msmcleod

FYI - to stop MIDI Output being enabled on newly inserted synths: 1. Open Synth Rack View 2. Click on the "Insert Synth Options" dialog button 3. Ensure "Enable MIDI Output if Available" is unchecked, then click OK.

We're aware of this issue, and have fixed it for the next release. The workaround for the moment is to disable the Spectrum Analyser display in the Inspector / Console View before loading/saving ProChannel presets.

Another thing it could be is an archive file on your desktop that Windows explorer is unable to unzip. The Browser control within Cakewalk is basically an instance of Windows Explorer, and when it is first instantiated it points to the desktop. If there are any files there that Windows Explorer can't deal with, you may get a shell exception. One way of confirming this is to open Windows Explorer and go to your desktop - if Windows Explorer hangs or crashes, then that's your issue.

@Archerdrummer - does turning off the spectrum analyser in the console view help at all?

My hunch is that it's this setting here: When this is checked, all CC's are set to 0, apart from CC7 which is set to 101. Normally, having both "Zero Controllers When Play Stops" is fine as long as you've also got "MIDI Event Chase on Play" checked too... that way any CC changes are set to the correct value when you continue playback. CC7 events should be fine. CC7 automation will be problematic if you have jump events, as they literally mean "no automation" - so nothing will be chased. You could try unchecking "Zero Controllers..", but this will require you adding your own resets for any CC's / Pitch Bend at the beginning of each MIDI track. My recommendation: 1. Ensure you're setting CC7 to what you want at the beginning of the project. 2. Ensure "MIDI Event Chase on Play" is checked. 3. If you must use CC automation, avoid jump envelopes. 4. If possible, use audio volume automation instead.

The new Sonar supports articulations that apply negative delay in either ticks or ms (up to +/- 1000 ms or +/- 1000 ticks). Negative delay at the track level is in the works, but no ETA as yet.

Radius and Elastique use completely different algorithms to stretch the audio. There is no better algorithm between the two - one can be better for one type of audio, and the other the better for another. All stretching algorithms will create artefacts / distortion to some extent - again, the extent of these artefacts will depend on the audio and how much you're stretching.

This might work... 1. Open up RegEdit and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ASIO 2. Expand that node, find your Axe Fx ASIO device, and expand that. 3. Take note of the exact CLSID and description. 4. Take a backup copy of drivercompat.json in C:\ProgramData\Cakewalk\Sonar (or C:\ProgramData\Cakewalk\Cakewalk Core for CbB ) 5. Open drivercompat.json in notepad 6. Add an entry for the Axe Fx, using the CLSID (minus the curly braces) in step 3 as the uuid, and the description as the name. Be careful to ensure you get the syntax exactly right, then save the file. This will tell Sonar to ignore the Axe Fx as an ASIO device.

I wholeheartedly agree with all the replies here. What I would suggest is maybe getting someone else to mix one of your songs, just so you can compare to your own. There are bound to be plenty of up & coming mixing engineers who would be more than happy to do a mix far cheaper than you'd expect, just so they can get some experience / add to their portfolio. There was a youtube video not long ago, where the youtuber paid 5 mixers and 5 mastering engineers of different price scales to a mix / master. The best master came from some on fiver.com, and cost something like $20. A similar thing happened with the mix.

Do your microphones have switchable patterns? If you're used to using cardioid, you'll be used to getting a proximity effect which boosts bass frequencies giving a fuller sound. If you've switched it to something else, like omni or figure of 8, that could explain the difference in sound.

Both Sonar & CbB enumerate all audio interfaces on start up, so it can correctly show which ones are available. Depending on how the drivers are written for those interfaces, it could cause a temporary glitch in any existing audio being played.

Have you inadvertently turned on high pass (either on the mic or the pre-amp) ?

Unfortunately that's up to the VSTi vendor. In fact, it's not just VSTi's - some hardware synth modules ignore CC7 for volume. IIRC I've got one or two Korg modules that ignore CC7 unless they're in GM mode.

The folder where Cakewalk looks for templates is specified in Preferences: If you've changed this to another directory, either change it back or copy the templates from the original directory to your new one.

Make sure "Select Events with Sections" is checked within TV Options, or highlighted within the Selection module:

If the you're on the Audio tab then it's gain; if you're on the MIDI tab then it's velocity. The same thing goes for Pan & Volume fader - i.e. Audio Tab = Audio Pan/Volume, MIDI Tab = MIDI Pan / Volume.

Actually, for MIDI you probably want TTSSEQ.INI (in the same directory). Also check you haven't got a Control Surface using those MIDI ports.

IIRC on the real Mackie, Modifier 1 + Function 5 does the same as the space bar, where Modifier 1 is Note On 0x46 (70), and Function 5 is Note On 0x3A (58). The Faderport might use SHIFT for Modifier 1, and the "Master" button for F5... but you'll need to give it a try (or see what buttons give the same result using something like MIDIOX). For the play button, the Faderport is definitely sending the expected messages for their play button, but as you say, this isn't the same as the spacebar.

It's safer to just exclude your Cakewalk project / content / plugins directories in your AV rather than disable it altogether.

All you need to do is uncheck the metronome for both recording and playback. It will still be heard for the count-in. If you want the metronome completely silent, mute the metronome bus.

The latest version of MMcL Mackie Control can be found here: https://msmcleod.co.uk/cakewalk/MMcLMackieControlSetup.zip Apart from the COM class ID (so it's recognised as being separate from the stock Mackie Control DLL), it's identical to the one shipped with Cakewalk/Sonar. It's definitely up to date.

Your audio device set up seems fine, but without seeing your track / bus routing it's impossible to tell where the track is being routed to. Also, all of your tracks are plain MIDI tracks. MIDI itself makes no sound - it needs to be routed to a software synth or an external sound device via a MIDI interface.

The P0 is showing the Patch Change of program 0 at 1:02:375. As for the crash, you'll have to attach the MIDI file for us to investigate further. My guess would be the SysxBank's or the NRPN's... are you playing this on a softsynth? If that's the case, then you're as well deleting these events.

@Misha FWIW, when I read his post it didn't read to me like you were the person he was accusing of being dishonest, but rather the DAW vendor.