msmcleod

I find by far the easiest method is to type in part of the name into the browser, then drag it on to my track:

The main difference between the previous version of the MackieControl.dll and the latest one is the auto config, which is based on the order in which the control surfaces are added. So all you should need to do is add the control surfaces in the following order: Mackie Control - US2400 port 1 Mackie Control XT - US2400 port 2 Mackie Control XT - US2400 port 3 However pressing the reconfigure button will override the auto config - and any preset you've previously saved will also override this in any case. There's thread here that describes a similar issue you're having:

ALT + Z get's you back. I'm always forgetting it too!

Running the nanoKONTROL 2 in Mackie/SONAR mode will emulate the Mackie MCU, which is pretty much limited to how Korg have programmed it and also by the limitations of the MCU. I did add some enhancements back in the 2019.12 release to give access to the effects & synth racks, but it still basically behaves like an MCU does. The MCU was never meant to be a generic controller (the Mackie C4 was meant to be that, but never really took off). If you want generic control, run the nanoKONTROL 2 in CC mode and use either Cakewalk's Generic Surface Controller or AZ Controller.

Mike - I've been in this place too... and had similar thoughts only a few weeks ago, as I seem to be spending all my time writing code (which I do enjoy), and really not getting much music done. The thing that snapped me out of it was spending the day with my daughter recording a song - just a cover, but it got me actually using my gear again. So that would be my advice - just record a cover of something. During the process you'll no doubt find a use for a lot of the stuff you've acquired over the years.

AD2 is still my go to for drums, and like @Michael A.D. I also quite often use it with Jamstix.

All of your Sonar X1 effects should be available in Cakewalk. Check any of the VST paths you've got set up in X1 are also set up in Cakewalk.

CbB continues to work on WIndows 7 - we just don't officially support it any more, hence the warning when you install it. There's nothing new that has been added ( AFAIK ) that wont work on Windows 7, however this is likely to change at some point in the future.

@scook is correct - this is where it's stored. The values look like this for the various default modes: Universal: <string>com.celemony.analyzerParameterSet.polyphonicUnpitched</string> Percussive: <string>com.celemony.analyzerParameterSet.percussive</string> Melodic: <string>com.celemony.analyzerParameterSet.melodic</string> Polyphonic Sustain: <string>com.celemony.analyzerParameterSet.polyphonic</string> Polyphonic Decay: <string>com.celemony.analyzerParameterSet.polyphonicWithDistinctAttacks</string> I've found best results for Audio->MIDI are from Melodic (or Polyphonic Sustain if you have Editor or Studio). Be VERY careful when editing this file though. If you get one of them wrong, it'll crash Cakewalk.

A couple of things: 1. WASAPI Exclusive isn't supported by all sound devices. 2. In WASAPI Exclusive mode, Cakewalk takes exclusive control of the sound device... which means it won't share it with Windows. You've two choices: 1. Use WASAPI Shared; or 2. Continue to use WASAPI Exclusive, but check "Suspend Audio Engine When Cakewalk is not in Focus"

When I last spoke to Noel about this, he said it used whatever one Melodyne was set to... so I guess that would be the last one you set it to within Melodyne's UI. Now this has got me wondering... if you were using the trial, and it was previously set it to one of the polyphonic modes... that might explain it not working.

I bought one of these a long time ago... actually I traded in my YAS-32 sax for it (still regret that ) - but it's great for both saving/restoring patches & also playing sequences. It also worked great in the studio. I could sequence all my keys at home, "bounce" it to the data-disk then sync it up to the BRC in an ADAT system. Random access to anywhere in the song on the ADAT worked a treat. The only downside was manually entering tempo maps into the BRC. For live, I'd store each song as a combination of sysex/patch changes so that my whole rig was set up exactly how I wanted in around 2-3 secs.

A lot of VST's use NRPN's for their automation parameters. By default CbB expects this, but you can switch it off. Have you tried checking "Do not intercept NRPNs" in Omnisphere's plugin properties ?

@Gary Shore - did you install Melodyne via BandLab assistant? CbB uses ARA directly to perform the audio to MIDI conversion outside of the Melodyne interface, so while you can't use it as a Region FX or plugin when the trial is over, you should still be able to drag clips from an audio track to an empty MIDI track to do conversion from audio to MIDI. If this has stopped working, I'd advise uninstalling Melodyne and re-install it via BandLab assistant. As far as alternatives, I find MAutoPitch ( https://www.meldaproduction.com/MAutoPitch ) fantastic for just doing vocal tuning, and best of all it's free. Although you can't edit it in the same way as Melodyne, you can automate it in & out as necessary. When I've used this method, I'll usually "bounce to clip(s)" afterwards to make it permanent.

FYI - we found a similar crash with freeze, which has been fixed for the next release. It fixes this issue too.

Dragging the audio clip to a MIDI track *should* still work, even if your trial has ended.

Do you have any audio tracks that have no import source (i.e. it's set to "none") ? We've just fixed a freeze issue where this was causing an issue. Export/Bounce is a similar operation, so it could be related. Until the next release is available, make sure your all your audio tracks have an input source before exporting.

Running your mix through this into the Lurssen Mastering Console is a very nice combination.

From personal experience... Antares VST2 plugins work much better than the VST3 ones in CbB. UJAM virtual guitarist series work better with smaller ASIO buffer sizes if JBridged in CbB (as a 64 bit to 64 bit bridge - not a bridged 32bit plugin)

I tend not to change banks, but instead use a single Combo patch with the patches set already - that way it's just a single program change. The manual says this: Bank A (A00–A99) CTRL#0=0 CTRL#32=0 Bank G (G01–128) CTRL#0=56 CTRL#32=any number Drum Program (G129–136) CTRL#0=62 CTRL#32=any number Which would imply, (if the "Patch Browser" setting is set to normal): 0 = Bank A 7169 = Bank G 7937 = Drums It may be easier however, to just import the .ins file and use the patch browser itself. The Korg .ins file is located in C:\Cakewalk Content\Cakewalk Core\Instruments The .ins file actually lists the banks as follows: 0 = Bank A 768 = Bank A Preset B 1536 = Combi Bank A 2304 = Combi Bank Preset B 7169 = Bank G 7937 = Drums

Interestingly, the Audio/MIDI engine for Tracktion comes with the JUCE framework, which is free, up to the point where you're big enough to have to buy a developer license (which Behringer already are). But even then, it's peanuts compared to developing your own... and it's cross platform. IMO they'll use that to start with, and bolt on a bunch of hardware support for things like the Wing console. Either that, or they'll do another Ardour fork like Harrison Mixbus.

The MIDI spec allows for volume changes (CC 7) and expression (CC 11), but both of those affect everything on that channel not individual notes. So if you adjust volume for the snare, you'd be adjust the volume for everything else too. So although the short answer would be "no", it largely depends on the drum VST your using. There's a couple of routes you could take: 1. Split your drums out into separate channels/tracks: If each drum has its own track, you can adjust the volume (e.g. using automation) at various points when needed. You can route all of these tracks to their own bus so you've got overall control of drum volume using the bus fader. 2. Your drum VSTi may have some automation parameters allowing you to adjust the individual output level of each drum using an automation envelope. Note: Although I've mentioned using automation above, if you want to do everything in the PRV, most drum VSTi's can map automation to MIDI CC values, so you can use the CC lane in the PRV instead if you wish.

I did a post on this a while back with a video showing how to set it up: The key thing with using instrument IR's is to crank up the gain, otherwise it's really quiet.

This is almost always caused by a rogue plugin not closing down properly. Are you using any bit-bridged / jbridged 32 bit plugins? These are loaded in separate processes and can cause the symptoms you're describing if they're not behaving themselves.

Yes, that would be a good start to get the tempo map. FYI - you can actually export the remaining tracks really quickly by dragging and dropping to a folder in windows.... just make sure you keep the left button held down until it's finished the bounce: Also, if you're using this method to import into another DAW, consider setting this option in preferences: This will ensure that the start time of each bounced clip is maintained when importing into the other DAW.