msmcleod

@TVR PRODUCTIONS - please send the minidump file after it crashes to @Jonathan Sasor. This should tell us exactly where the issue is happening.

I didn't consider this - I always put it down to engineers that swapped from tape to ADAT, still kept on boosting the high frequencies (presumably out of habit) to compensate for the HF loss due to the tape's noise reduction, and ending up with a really harsh & bright mix. I do agree with Azslow to an extent though. Many tracks in isolation don't have a particularly wide dynamic range, so they could probably get away with a much lower bit depth. However when it comes to mixing those tracks, you really need to mix at a higher bit depth, otherwise you'll lose detail very quickly.

Audio Export processes the audio through plugins as fast as possible, but there are however a handful of plugins that don't support this. The only way around this is to turn on "Render in Real-time" when you export: :

@Heinz Hupfer - can you confirm whether this slow behaviour new to this release, or was it slow in 2022.02 too?

Yes, this would work - and you can easily create markers from arranger sections in the timeline by selecting all, right clicking on the timeline and choosing "Create Markers from Sections" from the context menu.

The best way to do it: 1. In the original project, save the track as a track template 2. In the new project, insert the track template you created in step 1. 3. Copy the track in the old project 4. Focus the track in the new project, and paste

The main causes of this are: - Using a driver mode other than ASIO or WASAPI Exclusive - Having your ASIO buffer size set too high

CTRL+A selects everything, so it's likely including something that is starting at time zero. CTRL + Click only selects the clips you click, and nothing else.

I think you're mixing up the cable type ( coaxial ) with the most common type of coaxial cable which has BNC connectors. Coax cables with BNC connectors are typically used for digital clock signals, 10-Base-T networks, and analog video. Both the Lexicon and octa-capture have RCA S/PDIF connectors, which REQUIRE coaxial cables with RCA connectors to operate properly.

The export presets are stored here: Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\Presets\{FD3918AE-AF3D-414B-8701-C9A02623E875} Just export this registry key from within regedit.

Looking at your event list, you've got 3 audio clips starting at time zero, one on each track. These are most likely what are stopping you from moving the other clips. It may be you've got Cakewalk set to hide muted clips. Make sure these two options are checked so you can see them. If this still doesn't do it, switch to the advanced workspace.

I'd avoid using converters if possible. I've almost never got them to work properly due to clocking issues - sometimes the converter wants to be the clock master, other times not, and not all of them support all of the sample rates/bit depths. For SPDIF, just connect it directly. You will need to designate one device as the clock master and one as a slave though.

All of the Mackie compatible controllers are great for transport / fader control, but not really suited to custom control of plugins. The monogram CC should work perfectly with ACT Learn however. You just need to add the "ACT MIDI Controller" under Control Surfaces in preferences, setting the MIDI IN to be your monogram's MIDI input ( don't bother setting the MIDI output ). Once you've done that, you're ready to assign knobs/sliders to VST parameters. Once parameters have been learned for a VST, they'll be remembered globally - so the next time you insert that plugin, the controller will automatically work for that plugin while the plugin's UI is in focus. A quick example of how to set it up for plugins is shown at 1min in on this video: A more in-depth explanation can be found in this video:

This can be configured in the Mackie Control Surface Dialog. Set the master fader to control Bus #1 rather than Master #1. This will mean it controls the first bus ( i.e. Cakewalk's Master bus) rather than the first output fader: IIRC, the Oxygen Pro has two Mackie DAW Modes. One is a high resolution version, the other a standard resolution. Try using the standard one.

CTRL / SHIFT / ALT are modifier keys, and are not considered keys in their own right. The ctrl / shift / alt labels themselves aren't for clicking, and turn bold when you hold those keys. In other words, to search for CTRL + M, bring up the key search and press both CTRL + M. CTRL + M is a factory binding, which shows up differently to a custom binding. You can tell it's assigned, because it's in bold: A user assigned key is displayed differently to make it more obvious:

The Oxygen Pro itself needs to be in Cubase DAW mode, and AFAIK you should be using the second Pro 61 MIDI ports - i.e. MIDIIN2 (Oxygen 61 MKV) / MIDIOUT2 (Oxygen 61 MKV). The primary ports are used for the keyboard itself. You can't use ACT at the same time as the Mackie Control, as the Mackie Control integration takes full control over the MIDI ports. We'll look into why the Cubase mode isn't being recalled. [EDIT] - found the cause of this... it's been fixed for the main release.

You can also use the Arranger Inspector for navigation, which is my preferred method. Clicking on a section within the Arranger Inspector will set the now time to the beginning of that section, so both the tracks view and PRV will scroll to it.

While Cakewalk isn't running, rename ctrlsurface.dat within %APPDATA%\Cakewalk\Cakewalk Core to ctrlsurface.dat.bak Then start Cakewalk. Cakewalk will now have no control surfaces defined, so you can add the Mackie Control one for your Pro 61. Once you've switched it over to Cubase mode within the Mackie Control surface dialog, remember to save it as a preset. To switch back, quit cakewalk, delete ctrlsurface.dat and rename ctrlsurface.dat.bak back to ctrlsurface.dat - when you restart Cakewalk, it will be using AZ Controller again with your original settings.

Clips are always given unique names when they are recorded. Some people like them to be uniquely identified, other's may not. It's easy to change them all at once though: 1. Select all the clips on the track ( clicking the track number is the quickest way to do this ) 2. Open the clip inspector - the one with the waveform icon. 3. Type the new name ( or copy / paste it from the track name ) into the clip name property - this will change the name of all the selected clips.

If you've got "Select Track Envelopes with Clips" checked, and there's a track envelope earlier in the time line, this can stop you moving things to the left, because the track envelope can't be moved to a negative time. Unchecking it, or deselecting it in the Selection module should allow you to move the clip (but obviously without the envelope). You can find this either in the Track View Options menu, or in the selection module in large mode: As far as moving lanes into tracks, the bounce method you've described is one option, as long as you're happy with it all being one clip afterwards. Another method is to select all the clips on a lane by clicking to the left take lane number ( T1, T2 etc ), then holding down SHIFT while dragging it on to a new track. Holding down SHIFT ensures the clip won't move left/right while you drag the mouse up/down. You'll need to do this a lane at a time, otherwise all of the lanes will simply end up as new lanes on a new single track.

This will be fixed for the 2022.06 general release.

The issue is down to a missing string definition in the English resource file. The feature was working at the time it was implemented and tested, but it looks like a subsequent code merge went wrong at some point (merging resource files can be occasionally problematic). This has now been fixed, and will be available in the main public release. In the meantime, the entry is available in all other languages, so as a workaround you can switch to another language and make your binding there, e.g. for French:

That's the intention. Obviously without testing each individual device, we can't be 100% sure it will work, as anything other than a true MCU is simply emulating one. Testing was done with a real MCU, a Yamaha 01X in Cubase/Nuendo mode, and a Korg nanoKONTROL 2 in Cubase mode. Unfortunately we don't have an SLL UF8 to test with, but hopefully someone with an SSL UF8 can try this out and report back.

Finally got around to finishing off watching season 2 of Star Trek Picard, and in the last episode noticed Rafi was using a KORG nanoKONTROL 2 to hack into the drones... ... with a strategically placed bit of aluminium covering the KORG logo & name.

Unless you're up to date with all of the latest the Windows 7 updates, you may have issues using the in-app refresh activation. Downloading BandLab Assistant and using that to update activation is still an option on Windows 7.