msmcleod

I'm not sure if they do an XLR equivalent, but I'd definitely avoid getting a USB based Mic when running in Windows. The reasons... 1. You can only use one ASIO driver at once, so if you're using the Rode's ASIO interface, you can't use anything else within CbB ( this is a Steinberg/Windows restriction, not a Cakewalk one). 2. Even if you could aggregate the devices to allow both of them, there's no way to sync up the word clocks, so you'd have to fix any timing issues manually. 3. You're stuck with the pre-amp that's inside the mic. I'm not saying that the Rode pre-amp is bad, but you've got no other choice but to use it. 4. You've no idea how long the USB drivers will work with the OS. An XLR mic will last decades and will never just stop working because you've upgraded to a newer OS.

CTRL + TAB will do nothing when it's actually docked. If it's undocked, is the PRV actually visible? It might be that it's minimized and isn't obvious you've CTRL + TAB'd to it.

Obviously having a senior moment here!!

CTRL + TAB is the Windows standard for switching between different application windows. ALT + TAB is the standard for switching between windows within the same application. Edit: ALT + TAB is the Windows standard for switching between different application windows. CTRL + TAB is the standard for switching between windows within the same application.

Pressing F6 twice will toggle between Select and the previous tool you used, whatever that may have been. F5 (smart tool) and F7 ( move tool) do the same. F8 (edit), F9 (draw), F10 (erase) have several different modes, so pressing them will simply rotate through the modes they offer. Nothing has changed here in a long time, SONAR Platinum behaves the same.

Electric guitars are unbalanced - a TRS cable might work, but it won't do anything as the tip and ring will be shorted at the guitar end.

First, set up the Arturia Keylab so that its configured for MCU mode using Cubase - follow the first step under the Cubase section on this page: https://support.arturia.com/hc/en-us/articles/4405748362002-KeyLab-MkII-Tips-Tricks In the Mackie Control surface dialog in Cakewalk set the Protocol to "Mackie Control Universal (Cubase Mode)"

My thoughts on balanced vs unbalanced... An unbalanced signal is basically your signal + ground. A balanced signal also includes the phase inverted signal. The idea is that any interference (i.e. noise) that affects the cable will affect both the balanced and unbalanced signal equally. So when you combine the signals, the real signal will cancel out leaving only the added noise. If you then phase-invert that noise, then combine it with the original signal, it will phase-cancel the noise leaving you with only the clean signal. With a mic level signal going through a long cable this can be extremely useful, as a mic signal is relatively low and the noise level may be relatively significant in comparison... it'll also be amplified when the pre-amp amplifies it to line level. So removing the noise before it amplifies it means you get a clean signal. With a line level signal however, any introduced noise in the cable will be fairly low in comparison (unless you've got some real issues with RF / electrical interference in your room). Also the shorter the cable, the less chance any interference will get the opportunity to interfere with your signal. With an amplified signal (e.g. speaker cables), the noise level is so low in comparison, you'd never notice it. So in general, always use balanced cables for mic level signals. For line level signals, it's not really a big deal, especially if your cables are short (i.e. 6' or less). Personally, I use some balanced line cables in my pre-amp rack simply because the connections were there, there's so much gear close together, and it wasn't much more effort/expense to use them. There are plenty of places where I don't have a balanced input for line signals though, and I've never found this to be an issue.

There are several versions of the standard Pre 73 - Mk I, Mk II & Mk III - I've got the Mk I, and a modded mk II ( I replaced the transformers with genuine Carnhills ) From the looks of it, that's a Mk II. Everything from Mk II and above can be modded easily to be replaced with Carnhill transformers. The Pre 73 DLX already has Carnhill transformers. The bottom of the range is the Pre 73 JR, which is a 1U 1/4 rack module with just the Mic & Line inputs, and a gain pot... you could fit 8 of them in a 2U rack space ( assuming you mounted the power supplies on the rear ). There's also the Pre-73 Premier and Pre-73 DLX Premier, both which have genuine Carnhill transformers. They're also the same colour as the old Neve's, with Neve style knobs. I wouldn't assume the Carnhill transformers are necessarily superior to the stock transformers in the other Pre 73's - using Carnhill's just makes it sound closer to a real Neve 1073. When comparing the Pre 73 to my other preamps, it was by far the best sounding, although my Scarlett 18i20 was VERY close. Where the Pre 73 really shines is when you drive it slightly too hard... then the magic saturation kicks in.

It's worth mentioning that, the Xtra styles ( as opposed to the XPro styles): don't have any new RealTracks, but use combinations of existing RealTracks for the new styles. require you to have at least the UltraPack to use, presumably because only the UltraPack has the required RealTracks. The XPro styles contain their own new RealTracks and can be used with any version of BIAB 2022.

You may also want to check out the Golden Age Pre 73 - it's $30 more, but is a Neve 1073 clone. I use two of them myself, and I'm very pleased with them.

Both these microphones are very good. The SM7B will work well with your Klark Teknik CT 1. It really depends on whether they suit your voice or not.

@RexRed - the CloudLifter and Klark Teknik MIC BOOSTER CT 1 are designed for boosting the signal of low output dynamic microphones, most commonly the Shure SM7B. Normally dynamic microphones don't use +48V phantom power. What these devices do is use the phantom power to boost the signal before you plug it into a mic pre-amp. This saves you having to put the mic-pre on full gain ( which raises the pre-amps noise floor ). I doubt it'll work in your situation as: 1. It'll steal the +48V phantom power needed by your condenser mic 2. The level it boosts by is fairly small compared to what a preamp does get it to line level 3. You may have impedance matching problems

The sound quality difference for the preamps doesn't surprise me to be honest. The converters in the Behringer gear are absolutely fine, but the preamps themselves sound really harsh to my ears. RME on the other hand, have top of the range pre-amps. @RexRed - As long as you're recording line-level signals, the Behringer should sound fine. So if you've got any other mic-pre's you can use in the meantime, just to get it up to line level, I'd give them a try.

@scook is correct - your system files are not in sync, either due to an incomplete Windows Update, or due to some other application/plugin installing older system files. Follow the instructions in this post here: The first step is what @scook suggested, but there are additional steps afterwards you should take to ensure your Windows installation is in sync.

I got it working by: 1. Running CbB as administrator inserting the synth, then closing CbB - note that I only ran it as administrator this one time. 2. Adjusting the registry permissions for HKEY_LOCAL_MACHINE\Software\rgc:audio software , giving Full Control to all of the users - i.e., you need to click on each user one by one and give them Full Control. 3. Run CbB as a normal user and insert the synth.

This error is usually caused by your system files being out of sync, either by an Windows update that was only partially successful, or maybe a recent plugin install forced an install of older components. The first thing to do is to install the VC++ redist pack here: Next, I'd recommend trying the following: hold down the Windows Key and press X (which brings up a menu) then press A. This will open Windows PowerShell. enter the following: sfc /scannow this will attempt to scan and repair the windows system files. This may take a while. If this doesn't work, try entering this: DISM /Online /Cleanup-Image /ScanHealth this will try to download and replace any corrupt windows files, and may take a few minutes. Afterwards, run sfc /scannow again.

^^ This. If you've any 3rd party anti-virus or firewall programs, disable them when downloading/installing Cakewalk.

First of all, make sure you're using the manufacturer's ASIO drivers ( and not ASIO4ALL ) Secondly, make sure your Record Timing Master is set to the correct audio device.

@torerk Is your MIDI driver mode set to UWP? Try opening Cakewalk with no project loaded, and setting the MIDI driver mode to MME.

The best way to find what a keyboard shortcut does, is by using the "Locate Key" button in the Keyboard Shortcuts page in preferences:

I'm not in the position to try this out ( house being rewired at the moment, so I'm on a minimal setup! ), but in theory you should be able to do this by creating an extra two MIDI tracks, so: 1. Create two MIDI tracks, one for each controller. 2. Set the input of each track to only match the MIDI port / channel that each controller is on. 3. Put the Velocity MFX on the track you want velocity fixed for 4. Set the output of both MIDI tracks to the Synth you want to route it to. 5. Enable MIDI echo on both MIDI tracks. Note that the MFX applies the changes in real-time, so any MIDI data recorded will have the original velocities recorded. You can apply the velocity changes to the recorded clips by: Selecting the track by clicking on the track's number From the main menu, Process->Apply Effect->MIDI Effects If you want the velocity effect to apply to further MIDI input, uncheck the "Delete Effects from rack" checkbox Click OK on the dialog

It should be in the Cakewalk subfolder in your Downloads folder.

Sounds like you may have a dirty USB connection, a bad USB cable, or pending USB hub failure if you use one. It could even be a power supply issue in the PC itself. I'd start by giving your USB ports / cables a clean. Electrical contact cleaner, or even WD40 should be fine for that.

First of all, check the VST scan paths in preferences on both machines. It's likely you've added paths ( e.g. C:\Program Files\VSTPlugins or C:\Program Files\Steinberg\VSTPlugins ) on your old machine, and not added them on the new one. Native Instruments (Kontakt) may have an additional path - it does on my machine. Secondly, check that all sample libraries are in the same location on both machines, otherwise your Kontakt instruments won't load properly when transferring between machines. I've used a symlink on all of my machines to my Kontakt libraries, so they're all looking at the same "fake" directory even though the libraries are stored in different actual folders.