msmcleod

I'm not sure this is always possible for MIDI tracks, the reason being that they can be routed to a hardware MIDI output, a synth MIDI input, or a drum-map MIDI input. The MIDI output ID's always start with the hardware outs, followed by the soft-synths, then the drum-maps. The complication comes with drum-maps, as they could be routed to more than one synth. This would then involve traversing through the topology graph to see what is connected to what, which is a relatively slow process, and not something you'd want to do on a control surface polling cycle. I think the best that could be done, would be to return the synth rack index for a particular MIDI track only if it's directly connected to it. You should then be able to get the rest of the information using the existing API calls used when dealing with the synth rack. I guess the same could be done for audio tracks fed from the synth rack. BTW - I'm not sure what's happening with MIX_PARAM_INPUT_MAX for MIDI tracks, it looks like it always returns 17, and I'm not sure why!

Streamworks Audio's SWA Complete SONAR X2 is old, but covers 90%+ of what Cakewalk does: @abacab has kindly listed a description and links to each chapter in this post:

@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: :

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:

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.

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.

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.

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