Category: Installation & Setups

How to use maschine or mikro to work as DAW controller in Cubase?

Last updated: 20201228

We use a combination of Remote device and Mackie Control here. Because it seems Mackie Control in Cubase, we can only use F1-F8 keys only, that’s about 8 buttons/functions. So we use Remote Devices (Generic Remote) for more functions.

 

 

Turn off maschine in ALL MIDI INPUT:

  1. Studio > Studio Setup…
  2. Midi Port Setup
  3. Windows midi in > Maschine Mikro 2 in > uncheck ‘In All Midi’

 

How to add a button using Remote Devices instead of Mackie Control.

20201230: This gives you MORE and UNLIMITED key mapping on Maschine than the limited 8 buttons using Mackie Control.

Studio > Studio Setup > Remote Devices

  1. Add a ‘Generic Remote’
  2. Under “Midi Input”, select “Maschine In”
  3. Click ‘Mute 1’ and hit ‘Add’ – this will create a new control at the bottom of the list
  4. Rename it to ‘Jeric – Return on Stop cc111’
  5. Set Midi Channel to 1
  6. Address to 111
  7. Max value 127
  8. At the bottom list, scroll down to the same Controller name in Step 3.
  9. Set Device to ‘Command’
  10. set channel Category to ‘Preferences’ (or “Process Plugin” if trying to use a plugin)
  11. set Value/action to ‘Transport – Return to Start Position on stop’

That’s it! You added a macro to TURN ON or TURN OFF ‘return to start position on Stop’ to CC111. Now in NICE, Pick the Note repeat button > Type: Control Change > Channel 1 > Number 111 > Mode Trigger

You can import from G:\music_projects\20200105_shian_love_song\MASCHINE_MIKRO_SETTINGS\cubase_generic_remote\20200113.xml

 

To change a key color hack:

Instead of choosing Type: MCU button, switch to Type: Note first, select color, then switch back to Type: MCU button!

 

How to add a Mackie Control? (to get maschine mikro working as a daw controller)

1. install maschine 2 software, so the MIDI device will show up in Cubase

2. In Native Instruments Controller Editor (NICE), create a new TEMPLATE > Factory Templates > Mackie Control.

https://www.native-instruments.com/forum/threads/maschine-cubase-transport-control-question.324601/ (seems to prefer checking “HOST TRANSPORT CONTROL”)

3. Cubase > studio devices > remote devices > add ‘Mackie Control’

4. Select ‘Maschine Mikro MK2 In’ and ‘Maschine Mikro MK2 Out’ respectively.

By now, your transport controls should be working.

5. Map extra commands you want: use this table:
https://www.native-instruments.com/forum/threads/mackie-control-mcu-parameter-id-codes-template.266581/

Cubase: for example, 54 = F1 , so set up what you want F1 to do in Cubase.
NI Controller Editor: Then map the YELLOW buttons on NI Controller Editor, to make that key send ‘F1’.

6. You can learn to create macros and other functions and map them further:

7. More ways to switch to MIDI input on your NI devices incase you need to know:
https://support.native-instruments.com/hc/en-us/articles/210264145-How-to-Switch-Your-Native-Instruments-Controller-to-MIDI-Mode

8. Unfortunately, there’s no way to IMPORT settings on this Cubase screen yet. So you will have to manually re-map functions on new Cubase installs/upgrades.

 

 

 

Saving and opening configuration in Native Instruments Controller Editor (NICE):

F:\PluginContents\MaschineMikroSettings\20190702_jeric_cubase.ncc

Cubase Mackie Control setup:

https://pasteboard.co/IuUjgT8.png

 

 

 

How I set up my Allen & Heath ZEDi 10fx for my DAW workstation without using USB?

Alright here’s the story, I have been working with my trusted Yamaha MG 10/2 for the past 15 years – and since 2 years ago, Channel 1 died. And just recently Channel 2 also died. Which meant I no longer have any INSERT I/O ports to use, for hack-sending my MIC INPUT to my AUDIO CARD.

Fast forward to today, I decided to go with a modern mixer, with new onboard effects, and great reviews – the Allen & Heath ZEDi 10FX (here on forth known as Z10).

Summary

Pros: The whole mixer is great looking, clean and very little NOISE signal.

Cons: MIC INPUT volume too low if you don’t want to use the GSPRE pre-amp gain too much, when sending MIC IN to your AUDIO CARD. Of course, if you don’t mind the GSPRE pre-amp colour, then MIC INPUT volume to your AUDIO CARD will be just fine.

Made in China

I was under the impression the whole machine would be made in the UK, but to my surprise, after I saw the Chinese text in the manuals, I decided to look for the “Made in.. ” words, and found that the device was “Made in China”..

I love China! And I’m not against Chinese goods, just that in a huge sense, all the audio devices I have grown up with, were made in Western countries – Germany, Finland, UK etc, and for a good reason – the whole pop music culture came from the West, therefore, they have a long history with sounds, sound engineering, waveforms, sonic theories etc – and therefore, when building audio devices, they know the important thing is that they SOUND good.

China and the Chinese attitude can do and build great functioning devices – and the keyword here is “functioning”. Not great sounding – simply because sounding good isn’t a materialistic function – it does not have weight.

So I give it a decade or two, perhaps then Made in China audio devices can be reliably sounding! Ok I digress.

Setup 1 – not ideal

  1. MICROPHONE XLR MIC IN to Channel M3 on Z10.
  2. 1/4inch cable insert into FX OUT on Z10.
  3. GSPRE M3 GAIN set to 40dB. (pre-amp)
  4. FX GAIN set to 0 on Channel M3.
  5. MIX GAIN set to 0 on Channel M3.
  6. Turn on 48V phantom power
  7. MAIN MIX volume set to 0 on Z10.
  8. PHONES volume set to 5 (center)

Pros for Setup 1:

  • This set up sounds good during playback.
  • MIC volume is also good on your headphones.
  • Both M3 GSPRE GAIN & MIX GAIN affects the MIC INPUT volume to your AUDIO CARD. The M3 GSPRE GAIN however has a larger range of gain control.

Cons for Setup 1:

  • MIC INPUT volume captured to AUDIO CARD is low, around -13.0dB.
  • FX OUT is post-mixer, so you can capture MIC INPUT ONLY if the MIX GAIN is more than 0.

 

Setup 2 – better & loudest (I will continue configure these till I perfect it for my sound)

  1. MICROPHONE XLR MIC IN to Channel M3 on Z10.
  2. 1/4inch cable insert into AUX OUT on Z10.
  3. GSPRE M3 GAIN set to 29dB. (pre-amp) (perfect loudest setting at 37dB)
  4. AUX GAIN set to 5.0 on Channel M3.
  5. MIX GAIN set to 5.0 on Channel M3. (perfect loudest setting at 0dB)
  6. AUX MASTER GAIN set to +5.0.
  7. Turn on 48V phantom power
  8. MAIN MIX volume set to 0 on Z10.
  9. PHONES volume set to 5 (center)

Pros for Setup 2:

  • MIC volume is good on earphones.
  • MIC INPUT recorded volume determined by M3 GSPRE GAIN only – so adjust this to control how much is sent to your AUDIO CARD.
  • AUX is pre-mixer, so you can capture MIC INPUT even if the MIX GAIN is muted.

Cons for Setup 2:

  • Recording volume is low at -23. (unless we use the perfect loudest setting in steps 3 and 5 above)
  • Only M3 GSPRE GAIN controls the MIC INPUT volume to your AUDIO CARD, but because GSPRE controls the COLOR added to your sound (very obvious when you hear it on your earphones), but some USERS might not mind or hear it. (I DO!)

 

Setup 3 – USB to PC just for compare (still softer than Setup 2)

  1. Connected USB to Computer and the Z10.
  2. ST3 to MIX gain set to 1st tick.
  3. Cubase set to send audio LEFT to Analogue 3, and RIGHT to Analogue 4.
    1. You need to install the ZEDi 10fx Audio drivers first!
  4. MICROPHONE XLR MIC IN to Channel M3 on Z10.
  5. GSPRE M3 GAIN set to 39dB. (pre-amp)
  6. AUX GAIN set to 0 on Channel M3.
  7. MIX GAIN set to 0 on Channel M3.
  8. AUX MASTER GAIN set to 0.
  9. Turn on 48V phantom power
  10. MAIN MIX volume set to 0 on Z10.
  11. PHONES volume set to 5 (center)

Pros for Setup 3:

  • MIC volume is good on earphones.
  • MIC INPUT recorded volume determined by M3 GSPRE GAIN only – so adjust this to control how much is sent to your AUDIO CARD.

Cons for Setup 3:

  • Recording volume is low at -23 or -18 depending on your M3 GSPRE GAIN.
  • Only M3 GSPRE GAIN controls the MIC INPUT volume to your COMPUTER, but because GSPRE controls the COLOR added to your sound (only to your earphones in this case, the recorded sound sounded the same as Setup 2), it might be a bad thing cranking this too loud.

Summary:

I choose SETUP 2 – since the AUX SEND and AUX MASTER allows me to control the MIC INPUT GAIN to my AUDIO CARD.

As you can see, I’ve chosen to use Setup 2, but it’s not perfect, simply because the recorded volume is still slightly soft  – at the right amount of GSPRE COLOR to my MIC INPUT. BUT, it’s still WAY louder than using the Z10 USB Setup 3 above.

As I described above, you can still send a louder MIC INPUT to your AUDIO CARD, by adjusting the M3 GSPRE GAIN higher – but this would add more GSPRE COLOR to your sound (especially obvious on your earphones), which may or may not be a good thing, depending on your SOUND SOURCE.

I loved the COLOR and VOLUME from my old Yamaha MG 10/2 , but unfortunately, it’s really NOISY (and it’s dead)! The Allen & Heath ZEDi 10FX sounds really clean compared to it – I’m still happy with my purchase – now my workflow involves post-volume-gain to my recorded MIC INPUT in my DAW.

How to tempo sync a wav sound sample file in Kontakt?

Last updated: 20210705

 

The idea is simple:

  1. Drag and map the sound (as seen here: http://apps.badjoerichards.com/apps/musichack/how-to-drag-and-drop-a-wav-sample-file-into-kontakt-in-the-new-cubase-9-or-10-onwards/)
  2. (not really have to) Make sure you enable ‘Edit All Groups’
  3. Change ‘Source’ from “DFD” to “time machine pro”
  4. Change the Speed to ‘Zone’ (by clicking on the % icon in 100%)
  5. Double click on the sound to go into Wave Editor mode to edit it
  6. Turn on GRID and Set the correct BPM for the sound file.
  7. Now it should tempo sync on playback of the soundwave.

 

Check out this video:

How to install Cubase perfectly and future proof it for upgrading or moving in the future?

To expand on this article.

System requirements:

Windows 10 64-bit

Note the 64-bit.

Do you know what I hate most? Re-installing Cubase and all its VSTs and plugins.

This article had to be done. I’m calling this process “future-proof“ing. You will hear me referencing it throughout the article.

My last installation and upgrade took me nearly 2-months to complete, and over a year to finally migrate to the new laptop workstation (Laptop A).

Then the worst happened.

Working on a brand new project on the new workstation, midway throughout, things just kept dropping – I could not edit tracks properly. It was probably a combination of a few things – Windows 10 64-bit, Cubase 8.5 and booting the full OS on a Lacie Thunderbolt 2TB SSD drive (Laptop A was a Macbook Pro Retina 2013 first gen)

With the project timeline already closing, I had to think of a plan, and started building my new music station that runs Cubase 9.5 on my 2016 desktop. (Desktop B)

I had wanted to let my new computer (Desktop B) install while I work on the old workstation (Laptop A) – but I have only 1 dongle – didn’t seem like I could install and test while I work. 

Now I have installed Windows 10 cleanly, (before installing Cubase 9.5, make sure to set up your HDD C properly as in section Harddisk Setup and Design) this would ensure certain folders work properly.

and also installed Cubase 9.5 to my Desktop B (without dongle) – separating my Cubase 9.5 program files from the main M.2 NVME SSD drive which my OS is running on, and installing them to a SATA EXPRESS 3 connected HGST 4TB HDD.

The idea is to have my CUBASE 9.5 program, all its plugins, samples etc from today forth, on a separate HGST 4TB HDD (HDD C).

This simple step would future-proof my installation and upgrade of HARDWARE (and software) – which I will explain later.

Without the dongle, my Cubase 9.5 on my Desktop B wouldn’t start.

Harddisk Setup and Design

We will address this beautiful harddisk as HDD C from here on. Our drive letter would be H:\.

Important folders were created when building the new Cubase 9.5 workstation on Desktop B.

  1. MusicWinProgramFiles
  2. MusicWinProgramUse
  3. PluginContents
  4. MusicProjects
  5. VST2_32bit_Plugins
  6. VST2_64bit_Plugins
  7. VST2_64bit_Plugins\jBridged
  8. VST3_32bit_Plugins
  9. VST3_64bit_Plugins

MusicWinProgramFiles – would behave like the Program Files folder which we use everytime a new program needs to be installed. So instead of installing things to the Windows Program Files folder (that is currently residing on my M.2 NVME SSD drive where the OS is installed and running on), we install it to the dedicated HDD C. Cubase 9.5 itself was installed here. Future upgrade installations will also be installed here.

MusicWinProgramUse – would behave like the My Documents folder which you will use to store files and documents that Programs installed to MusicWinProgramFiles will use, i.e. settings, images, etc.

MusicProjects – this is the root folder where all your future Cubase projects should be saved. Naming conventions I use is as follow: 20180812_songnamecurrently

PluginContents – this is where you can place your VST Instruments or plugins’ sample files or data packs. These files/packs are usually large files that are required for your VST plugins/instruments to work.

VST2_32bit_Plugins – behaves like the usual VSTPlugins folder that we usually install all plugins and VSTs to. This phantom folder moves around on every Cubase installation and Windows installation, and has been confusing me and most users for a decade. So, we create a DEDICATED and FIXED location for current and future installations. Point to note is, this folder is specifically for VST2, and 32bit plugins.

VST2_64bit_Plugins – similar to the above, except for 64bit, VST2 plugins.

VST2_64bit_Plugins\jBridged – see section on jBridge. (to write)

VST3_32bit_Plugins – this folder is what I call our MAGIC folder. Basically Cubase and all other plugins that uses VST3 will install files to the LOCKED folders (See: Key Common Folders to note) – which will be magically installed here instead. This is done by symlinking. Do this as soon as you can (like right now, see: Magic VST3 folders and symlink), before installing any VSTs or plugins. Check this and the folder below from time to time, and you see your Plugins automatically installed here.

VST3_64bit_Plugins – similar to the above, except for 64bit, VST3 plugins.

 

 

Backups and Backup disks

You should have a separate disk to backup everything, including the OS, your music projects, data files etc. This will be known as HDD Backup, drive letter, X:\.

  1. DiskBackups (On separate disk)

DiskBackups – here we will schedule and run automated Macrium Reflect disk backups of your current Windows and all its Program and Settings. This will help you in the event of unbootable Windows or lost files. You can disable Windows System Restore when using this.

 

Magic VST3 folders and symlink

Because VST3 folders are locked on Windows, that means you cannot install VST3 plugins anywhere else except in the Windows drive i.e. C:\Program Files\Common Files\VST3 (for 64bit plugins) , we have to devise a way to keep this behavior, but “magically” save and store files on our HDD C’s VST3 folders. (See: Harddisk Setup and Design)

This process works BEFORE or AFTER you already have any VST3 plugins installed on your computer. Therefore it “future-proof”s our workstation.

  1. Start by installing Link Shell Extension on your computer. Do install x64 prerequisites. (i.e. http://download.microsoft.com/download/8/B/4/8B42259F-5D70-43F4-AC2E-4B208FD8D66A/vcredist_x64.EXE)
  2. Copy any contents in C:\Program Files\Common Files\VST3 (for 64bit plugins) to H:\VST3_64bit_Plugins
  3. Right click on the H:\VST3_64bit_Plugins folder, and select “Pick Link Source” (this appears after you install the item in Step 1)
  4. Head to C:\Program Files\Common Files\, right click on an empty space in the browser window and select “Drop As > Symbolic Link”
  5. Delete the VST3 folder that you see here. Feeling safe that you already copied all contents to H:\VST3_64bit_Plugins.
  6. Rename the folder VST3_64bit_Plugins that you see here, to VST3.
  7. Now we repeat this for VST3 32bit Plugins. Copy any contents in C:\Program Files (x86)\Common Files\VST3 to H:\VST3_32bit_Plugins
  8. Right click on the H:\VST3_32bit_Plugins folder, and select “Pick Link Source”
  9. Head to C:\Program Files (x86)\Common Files\, right click on an empty space in the browser window and select “Drop As > Symbolic Link”
  10. Delete the VST3 folder that you see here. Feeling safe that you already copied all contents to H:\VST3_32bit_Plugins.
  11. Rename the folder VST3_32bit_Plugins that you see here, to VST3.

That’s it!

From here on forth, everything should work automagically. All your VST3 plugins that you install henceforth, will magically appear in HDD C.

 

Some reference:

https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

 

Key Common Folders to note

What about VST3 you may ask? Note that VST3 folders are locked to:

  • On Windows:
    • C:\Program Files\Common Files\VST3 (for 64bit plugins)
    • C:\Program Files (x86)\Common Files\VST3 (for 32bit plugins)

 

You can however, re-arrange plugins and create sub-folders in THAT folder to manage things if you like.

So a few key folders to take note if your future-proofing life:

  • C:\Program Files\Common Files\VST3
  • C:\Program Files (x86)\Common Files\VST3

 

Project migration and continuing on better computer (Desktop B)

So I first saved my project on Laptop A at its current state. I could have used Cubase 8.5 > File > Back up Project

But I have already created unique folders on my own, so this time, I simply copied the whole folder to my new Desktop B.

I started by removing dongle from Laptop A and inserting into Desktop B. Starting Cubase 9.5 gave me permissions error with the dongle. To fix that, I run the “eLicenser Control Center” with Administrative privileges (Right click desktop icon > Run as Administrator), then let it perform online maintenance.

My current project is using a few plugins which I must install to continue work, I was able to quickly get these scrolling and looking at the MixConsole on Cubase 8.5:

  1. Waves
  2. Autotune
  3. Supercharger GT

Testing Cubase 9.5 while installing different plugins, would require you run the Cubase 9.5 program, and when we run it the first time, we should set it up to “future-proof” it.

Waves plugin allows you to install all flavors of the VST plugins, i.e. VST2, VST3 and both in 32-bit and 64-bit versions, so in total, 4 of them. We can use this installation to test our setup.

 

Running and setting up Cubase 9.5 for the first time

Either you are opening your first music project or testing if your VST plugin was installed correctly, some settings here should be set when you see them.

When the first POPUP of news and projects opens up, select “Prompt for project location”, so you can always be sure where to save your new music projects.

Now everytime you create a new project, create a new folder in MusicProjects with the naming convention, 20180812_newsongname.

Windows 10 requires you to lock your sample rate and turn off Windows sounds. See:

Cubase prevent sample rate change when working Windows Sounds

and

How to fix WAV playback too fast or wrong in Cubase, and how to change Sample Rate in Windows 10 for Microbook?

 

VSTPlugins settings

Once Cubase 9.5 loads for the first time, select Studio > VST Plug-in Manager from the Top menu.

Click on the Wrench Icon (Setup) at the bottom left.

Click on the + add icon on the new section that pops up. Add both VST2_32bit_Plugins, VST2_64bit_Plugins folders that were created on your HDD C.

 

A few good referencing materials:

https://www.steinberg.net/forums/viewtopic.php?t=74462

https://steinberg.help/cubase_pro_artist/v9/en/cubase_nuendo/topics/project_handling/project_handling_backing_up_projects_t.html

 

Installing new programs and plugins

When installing new programs:

  1. Always install to MusicWinProgramFiles
  2. When choosing the folder to install, copy the full Folder’s name & path
    1. i.e. C:\Program Files\IK Multimedia\T-RackS 5
    2. Copy the “\IK Multimedia\T-RackS 5” part.
  3. Then click the Browse or Select button, to select the folder in Step 1.
  4. If the new path does not include the Folder Name or path, then append it manually.
    1. For example, if the new path ends up being HDD C:\MusicWinProgramFiles
    2. Change it to: HDD C:\MusicWinProgramFiles\IK Multimedia\T-RackS 5

When choosing VST folders:

  1. VST3 should be automatic, using the default folders like C:\Program Files\Common Files\VST3. If it allows you to edit or pick when installing, leave it as C:\Program Files\Common Files\VST3. (Remember we have already MAGIC SYMLINK it to our HDD C? See: Magic VST3 folders and symlink)
  2. If you are asked to select your VST2 folders, then select your VST2_32bit_Plugins or VST2_64bit_Plugins folders. Take note of the default folder that shows up during installation. Copy it and note it somewhere. (Step A)
    1. If you are unsure whether it is a 32 or 64 bit, the default folder that shows up can be a hint. i.e.
      1. If the default folder says C:\Program Files\VstPlugins , then it’s probably a 64-bit plugin.
      2. If it is C:\Program Files (86)\VstPlugins, then it’s probably a 32-bit.
    2. Worst case scenario, just pick the VST2_64bit_Plugins folder – then test if Cubase 9.5 sees it. If not, then copy/move it to VST2_32bit_Plugins
    3. If there is a folder name in Step A, you can copy and append it to the end, so your plugins are more organized. i.e. E:\VST2_64bit_Plugins\Audio Ease

 

Updates, upgrades and installation of Cubase

So the time will come again when you need to install a new version of Cubase, install it to MusicWinProgramFiles. 

When running the installation/upgrade, for my example of Cubase 10, when prompted for folder, replace “C:\Program Files\” with “H:\MusicWinProgramFiles\”.

Other Windows performance settings

See:

https://help.uaudio.com/hc/en-us/articles/214429386

https://help.uaudio.com/hc/en-us/articles/214428366-Windows-Setup-Required-Settings#WinTB