msmcleod

It's basically a 64 note polyphonic Sound Canvas. It's a 1U rack, with limited display ( IIRC it was just a 2 or 3 digit LED display ). AFAIK, it's the equivalent of a Roland SC88 in a 1U rack. The SC88 has a much better display. As far as sound... it sounds exactly like the TTS-1 ! IMO something like the Yamaha MU100R blows it away ( and that's an old bit of gear too ).

The TTS-1 uses the Roland SoundCanvas sound set, which is the same as the M-GS64, and all of the sound canvas range. The MT-32 has a completely different sound set, as it's an LA v2 synth and not a ROMpler (yes, I know it has PCM samples in it, but they're so short IMO they don't really count - they're really just short attack samples, with the bulk of the sound coming from the synth engine). The TTS1 is GS/GM compatible, as are all the Sound Canvas range. The MT-32 is not GM/GS compatible (although with some clever sysex you can get close to the GM mapping). Although the M-GS64 has an MT-32 mode, all this really does is remap the program change values of its existing sounds to match as closely as a can, the sounds in the MT-32.

Mine is just under 8". I can manage an octave comfortably. An octave plus one, although doable is uncomfortable and I can't do it with any reasonable velocity. Fine for organ sounds, not so much for piano. I use a Korg microKEY 61 in my office, which has mini piano style keys - it's a breeze to get an octave plus three on that. IIRC when I did classical piano ( so long ago, it's hard to recall!) I used to quickly arpeggiate larger intervals I couldn't stretch to, and using the sustain pedal to sustain the first note. Takes a bit of practice, but it can be done.

When a region FX is active, the region FX has total ownership over the clip. If Cakewalk messed with it in any way, it's likely to crash the plugin. When a clip is frozen, the region fx is temporary disabled, but it still owns the original clip. What you're seeing/playing in the track is a temporary frozen clip. When you move a section in this scenario, one of two things could happen: 1. The frozen clip is moved, but the original clip stays where it is: That isn't what you want, because as soon as you unfreeze, the clip is in the wrong place. 2. Both the frozen clip and the original clip are moved: The region fx isn't aware that the original clip is moved as it's meant to have total ownership of it... it'll probably crash. As neither of these are feasible options, clips with active region fx are excluded from arranger operations.

A single instance of Kontakt is more efficient with memory / CPU... that is if you enable multi-processor support within Kontakt. That being said, a single instance per track of Kontakt can be more convenient if you want to freeze individual parts. Having one instance of Kontakt basically means you're freezing all of the tracks feeding that instance, or none. Also, some systems may have issues with enabling multiprocessor support in Kontakt - although I've had zero issues with CbB personally (all are Intel CPUs). If you do see issues, then separate instances is definitely the way to go, as CbB will distribute the VSTi's across the CPU cores.

1. As others have said, make sure you're inserting tempos, not altering the first one. It's far easier to see what is going on by using the tempo track / tempo inspector. When using the tempo track, make sure you add a node at the existing tempo at the place you want the tempo change. Then add a new node and drag it to the new tempo. This will ensure your tempos before the tempo change aren't affected, e.g. : 2. MIDI data will always follow the current tempo. You can set the start time of the clip to absolute, but changing the tempo will always change the tempo of any MIDI clips. In practice, this shouldn't be an issue unless you've got different MIDI clips playing at the same time which need a different tempo. The only way around this is to render your MIDI as audio, and move the audio to the place where you're changing tempo. The way I'd probably do this, is to have an area after the video where I have my MIDI data. I'd then edit the MIDI as I see fit without affecting the rest of the project. Once I'm happy with it, I'd freeze it, copy the audio to the place it's meant to go in time to a separate audio track, Note that I'd only do this for the exceptions - i.e. MIDI based sound fx or small motifs. The main parts should always be following the project tempo at that point. Alternatively, you could have small motifs at different tempos in a separate project, and have both projects open at the same time. You could then render the audio in your motif project, and copy them as audio to the main project where your video resides.

If you can grab a dump file, please sent it along with your project to @Jonathan Sasor - we can look into the cause of the crash.

What if I have one synth instance with 16 outputs, connected to 16 audio tracks & 16 MIDI tracks? A track name/number would make no sense at all in this case.

@Mark MoreThan-Shaw - just noticed that the clip is frozen in your screenshot... this isn't the same as rendering the region FX. All this does is create a temporary copy of the rendered region FX, but the region fx itself is still actually active. Did you actually render the region fx before freezing?

That is strange... I just tried the following: 1. Create two audio tracks with a clip on them 2. Added an arranger section covering the extent of both clips 3. Created a Melodyne Region FX on the 1st clip. 4. Attempted to move the section.... only the 2nd clip gets moved ( expected ) 5. Undo the move 6. Render the Region FX on the 1st clip 7. Move the section - both clips get moved as expected So for some reason, in your case, either Cakewalk thinks the region is still active, or there's something else in play. Can you zip up your project folder and PM it to me? I'll need to see it in action with the debugger attached. [Edit] - you could also try bounce to clip(s) on that clip to see if this helps

This is intentional - while a region fx is active the audio "owned" by the region fx plugin.

If you want everything saved, i.e. name, selected buses etc, all you need to do is add it as an export task.

Maybe you hit nudge by accident?

We'll have something that addresses this in the next release.

We'll do something about this in the next release.

Me too... I had two... and only just managed to get my 3rd one from eBay after waiting about 3 years for one to turn up!

There's no PC in Sonar 8.5, and the OP is using Sonar 8.5 because of better compatibility with JAWS.

My PC was freezing twice a week - I spent AGES trying to work it out. The thing was, I've got a quad-boot: 2 x Win10, 1 x Win 7 64 bit, and 1 x Win 7 32bit. It would freeze in all four of them, and once it froze while doing a disk backup ( when it was running Linux booted from a CD ). On a hunch, I increased the CPU voltage in the BIOS very slightly... freeze problem solved. It's been around a month now with no issue. This was a complete computer freeze though, not just CbB. I've not seen CbB lock up in a long long time. I run a pretty clean machine though, and make sure no AV or cloud sync programs are looking at anything CbB might be.

Can you post a video of what is happening? Without seeing explicit steps and seeing what state the various options are in, it's hard to give any suggestions. ScreenToGif is useful for this.

I'm sure I've said this before, but the major three stumbling blocks for using Linux as an audio platform are: Lack of professional Audio Driver support Lack of native plugin support Lack of supported DAWs ( Reaper / MixBus being the main exceptions ) FWIW - I love Linux as a platform... just not as a DAW platform.

You absolutely have to switch to high performance mode to get any decent performance in audio applications. Software synths & effects are almost 100% reliant on CPU power.

Some of NI's instruments completely break the rules of MIDI, e.g. using CC#1 as a volume control is madness. CC#1 is defined as modulation, not volume... and CC#1's default value is zero. It's in the MIDI spec. So the question is, should Cakewalk start ignoring the MIDI spec just because NI does? There's probably some extra work we could do to be a bit more selective about which controllers get zero'd, but that's just a workaround. Given that NI have already made the decision to break the spec, the best thing to do is manually add a CC#1 to the beginning of your MIDI clips in the event list.

Personally I'd always go with a manufacturer that has experience in making quality mic pre-amps. Both Focusrite & Presonus have a history of making studio consoles (Focusrite with analog consoles / Presonus with digital consoles), so they have a wealth of experience designing quality mic pre's. Focusrite was founded by Rupert Neve, and is currently owned by the original founder of Soundcraft. I still use Focusrite in my office, and about 50% of the time in my studio ( the other 50% of the time, I use my RME which has only ADAT inputs... but is quite often "fed" by the output of my Focusrite Scarlett 18i20 when I'm not using other hardware pre's).

If all I'm doing is mixing, then using the onboard sound device in one of the WASAPI modes works fine for me on my laptop. I just plug my headphones directly into the laptop. Whether to use WASAPI Exclusive or WASAPI Shared is down to a number of factors: WASAPI Exclusive Low latency Cakewalk will completely take over the audio device, so you can't have other apps using audio. Checking "Suspend Audio Engine When Cakewalk Is Not in Focus" in Preferences->Audio->Playback and Recording can be used to mitigate this to an extent... but it can be annoying if you accidentally switch to some other application, and Cakewalk stops playing, so I tend to not have this option checked. Cakewalk normally has full control over sample rate/bit depth, assuming the onboard device fully supports exclusive mode. Not all on-board devices support this mode WASAPI Shared Higher latency Audio device is shared with all other applications You may need to manually change the sample rate/bit depth in Windows audio to match your Cakewalk project Supported by almost all on board audio devices

Alternatively, there is the "Toggle Track/Clip Gain in the Edit Filter" keyboard shortcut. This toggles between what the edit filter is currently set to, and Clip Gain Automation so you can quickly switch back and forth. I normally bind this to '\' as it's right next to SHIFT on a UK keyboard.