msmcleod

Arranger sections are definitely not tied to any of the material - they're either tied to a specific MBT time by default, or specific sample time if the arranger track is set to absolute time. There's really no such thing as single track ripple editing... there's either Ripple Edit All or Ripple Edit Selection, so I'm assuming you're using Ripple Edit Selection for tracks. Ripple Edit Selection should have no effect on arranger sections - only Ripple Edit All all does. Moving an arranger section will move the events under it, but not the other way around... unless you've got Ripple Edit all on. From what you're saying though, maybe this isn't always the case. If you do see a case of arranger sections moving unexpectedly, please let me know the steps to reproduce, or alternatively post a video of it happening.

This message is in response to Windows telling Cakewalk this MIDI device has been removed. If it's coming up repeatedly, then it could indicate one of the following: A dirty USB connection ( clean your USB connections - I normally use contact cleaner, or WD40 ) A faulty USB cable ( try another cable ) An out of date driver for your device ( update the drivers if it has any ) A fault in the device itself... in which case it might need replacing

I don't think you'd want to add the MPKMini as a control surface. Control surfaces are primarily designed for controlling transport. Just enable its MIDI input within Preferences->MIDI->Devices.

We're not aware of any outstanding Arranger bugs - can you elaborate?

Sad news... https://www.theguardian.com/music/2022/may/19/vangelis-greek-composer-chariots-of-fire-blade-runner-dies

You could try checking "Always open all devices" within Preferences->Audio->Playback and Recording. On adding a track, Cakewalk enumerates all the devices for populating the input/output dropdowns in the track header. This is much quicker if the devices are already open and ready to go.

Sounds like you're running CbB as Administrator. Windows automatically disables drag/drop between applications running as non-admin and admin.

I got this, but the CPU usage is crazy high... (both in CbB and Studio One 5) anyone else seeing this?

From what I can tell, the clips or the content aren't actually moving, but what you're actually seeing is the clip being drawn slightly differently due to where the split points are. When you're zoomed out, the drawing of a clip is average of the waveform as it's trying to draw several sample values in a single pixel. The number of samples that are being averaged are changing as you are effectively changing the length of the clip by moving the split point. As you zoom in to the point where samples are more obvious, this effect is lessened to the point where it doesn't happen at all. But audibly, the clip is fine.

Yes, you can do that. Just insert a new synth, and change the output of the MIDI track to that synth.

Yes, you can do that however: 1. It requires knowledge of how MIDI tracks / soft synths are routed, and 2. Most new users just want the track to be an single instrument track, rather than separate MIDI / synth tracks. Having separate MIDI / synth tracks makes for a more complex project ( up to double the track count ), and can cause confusion for new users. For example, the gut instinct for adjusting the volume of, say a piano track, is to go to the track with all the piano MIDI data on it and changing the volume slider... except by doing this you're not changing the piano's synth's output volume, you're changing the MIDI volume ( CC #7) of that channel. Instead you have to go to the synth audio track to change the volume. And then there's which track to use for FX, or MIDI vs VST automation. So you have to be constantly aware of what you're adjusting and how things are routed. Simple Instrument / Per Output Instrument tracks take the complexity out of that. You've still got complete control via the Track Inspector Midi/Audio tabs, but by default it's easy to work with. The only limitation with using instrument tracks is the case where you've got several per-output instrument tracks fed to a single synth instance, and you need automation on the VST parameters. In this case, you're limited to putting the VST parameter automation on the first track. However, this can be usually worked around by mapping CC's to the parameters within the VST itself, then adding MIDI automation in each individual track. Alternatively, you can create an additional MIDI track solely for adding VST automation.

Yes - the shelf tool alters existing envelopes. If there's no node to the right of it, there's no envelope to modify at that point.

@Torbjörn Lundberg - there are a lot of different ways to do this, as detailed in this thread - but I admit the explanations are a bit daunting for new users. For new users, I'd recommend doing the following: 1. Create a new Kontakt instrument track for the track you want to change, then move that track so it's underneath the old MIDI track. 2. Select everything in the old MIDI track by clicking on the track number, then hold down SHIFT and drag the MIDI clip selection to your new Kontakt track (holding down SHIFT stops the MIDI clips moving left/right in time when you're dragging). 3. Delete the old MIDI track. I appreciate there'll be a bunch of users who think "Why, when you could just do X,Y, Z.....", but this method is simple and easy to understand for new users. There are definitely more efficient ways of doing this, especially if you're going to be changing all of your tracks to share a single Kontakt instance, but this should at least get you up and running.

The first time I did an install of any of the AIR stuff after Windows 10 21H1 came out, it put my machine into a BSOD loop on boot. Luckily I had a backup image from the day before, so I could restore it. IIRC what I did was... immediately after the AIR install ( and refusing any option to restart the machine ), I re-installed the latest VC++ redists, and also re-installed the latest iLok License Manager / drivers. This cured it.

@John Bradley - Thanks for the report. It may be in some instances the tracks are being moved in track creation order, rather than their original index order. We'll look into it.

Another way is to save it as a track template, and import it.

Do you have Ripple Edit enabled?

oh, interesting... they must have different CLSID's, or maybe installed in the Win32 subsystem.

32 bit DX plugins cannot run within a 64 bit DAW, and vice versa... and AFAIK you can't have a 32 bit DX plugin "installed" or more accurately, registered at the same time as the 64 bit one. So although you can have both on your hard disk, only one of them will be available as only one DX plugin can exist in the Windows registry with the same CLSID. You can however quite happily have 32 bit & 64 bit VST's installed at the same time, as long as they live in different locations on your hard disk. For the DX plugins, you could probably come up with a batch script that could swap between the 32 bit & 64 bit DX plugins before you ran SONAR or CbB, but you'd need to know exactly which plugins you'd need. For example, assuming you've installed SONAR 32 bit to "C:\Program Files (x86)", you could run the following to register the 32 bit version of TTS-1, and use it in SONAR 32 bit: regsvr32 "C:\Program Files (x86)\Cakewalk\Shared DXi\TTS-1\TTS-1.dll" Then run the following to register the 64 bit version before you run CbB: regsvr32 "C:\Program Files\Cakewalk\Shared DXi\TTS-1\TTS-1.dll" However, you'd need to: 1. Do this for each and every DX plugin, and 2. Know exactly what dependencies they need, in case you need to regsvr32 those as well. It's not for the faint hearted. There are three other solutions: 1. Run SONAR 32 bit on a different PC 2. Set your PC to be a dual 64 bit/32 bit boot and swap between them as needed ( FWIW, this is what I do ) 3. Run SONAR 32 bit in a virtual machine running a 32 bit OS... although with this solution, you'll be able to load/edit projects, but the VM might be too slow to record or playback larger projects.

It's also worth mentioning that Midi Export is now selection sensitive, so it'll only export what is selected. As mentioned above, the fool-proof way is to Save As -> Standard MIDI File.

Look forward to that one. @Craig Anderton BTW - I've been collecting your "Musicians Guide to Recording" series, but a few of them seem to be unavailable, particularly "How to Record and Mix Electric Bass" and "Desktop Mastering". Are these still in the pipeline?

Personally, I would avoid USB mics on Windows, the reasons being: 1. You can't use ASIO, as most USB mic's don't come with an output and Windows only allows one ASIO driver to be open at once. 2. You're stuck with the preamp built in to the mic, which may or may not be a good one... but it's never gonna be a Neve 1073. 3. You can't plug it into anything else but a computer. Additionally, if you're using it with other audio devices, there's no way of syncing the word clocks. So even using WASAPI Shared to record from multiple audio devices, they're all going to be misaligned and you'll have to deal with any phase issues by aligning the audio yourself afterwards. An XLR mic gives you way more options, and will be still be useable for decades - way past the point the drivers for your USB mic no longer work on your PC's OS. So unless you're ONLY doing pod-casts / voiceover work, I'd stay clear of them.

I managed to get one of those for a stupidly cheap price from Amazon a few years ago. It's surprisingly good as a guitar MIDI controller, although it does require its own playing technique. I've used it for recording finger style parts with the Ample Guitar M Lite.

When a Meloydne Region FX is active, Melodyne takes ownership of the clip which is why split is disabled. You need to render the Region FX first to relinquish control from Melodyne.

CC's 121 to 127 are Channel Mode messages: 121 - Reset All Controllers 122 - Local Control On/Off 123 - All Notes Off 124 - Omni Mode Off 125 - Omni Mode On 126 - Mono Mode On (Poly Mode Off) 127 - Poly Mode On (Mono Mode Off) For synths that support it, sending CC 126 with a non zero value turns that channel into a mono synth, which is handy for keyboard solos.