abacab

And the fact is that most of them were lining up for DAWs with names like Ableton Live, Logic, FL Studio, Reason, Reaper, Studio One, Bitwig, Cubase, etc.

Sorry, but I will stand by the statement "A lot of competition in a saturated market", and belief that it was not misused in this context. I don't like it either, but the reality is that Cakewalk wouldn't have failed in the market under Gibson if the opposite were true. If it were a money making machine, don't you think there would have been eager buyers lining up, rather than shutdown plans for a 30 year old company?

That's my Plan "Z", as in if the Windows zombie apocalypse ever happens to us. I already have Tracktion Waveform working on Windows (it's PC, Mac, & Linux cross-platform), and I believe Bitwig has a Linux version, and Reaper has a Linux beta. So not a showstopper, except for most of my 500 plugins probably wouldn't work that great in Linux. The Tracktion synths and FX would probably be good to go.

There are a couple of ways to easily get the MIDI routed to the instrument of choice. An instrument track is a combined MIDI and audio track, that appears as a single track if inserted as a "simple instrument track". The instrument track supports MIDI, and provides audio output for the instrument. The MIDI input for this track, as well as any MIDI clips on it, are automatically routed to the instrument on this track. You can also place your MIDI clip data directly onto a plain MIDI track and select any instrument track from the output section of the MIDI track. My basic workflow for opening up a MIDI file and assigning instruments would simply be (for an example using 4 MIDI tracks): 1. Create a MIDI file with the 4 tracks elsewhere, and save/export as a type 1. 2. Open the MIDI file in Cakewalk. It should open up the file with 4 MIDI tracks (don't forget to save this project as a .cwp file now, as .mid files cannot retain Cakewalk settings). (a) If you have not set a default MIDI output port in Cakewalk preferences [MIDI devices > Outputs], it will automatically insert an instance of the GM synth TTS-1 with the 4 MIDI tracks routed to TTS-1. (b) if you already have a default MIDI output port assigned [MIDI devices > Outputs], your 4 MIDI tracks will be routed to the default MIDI output. 3. If you are using 2(a), then proceed with using TTS-1 and setting up the GM sounds to correspond with the MIDI channels you want to use. If using 2(b), you will need to insert your own instrument tracks as explained in step 4 below. 4. To keep this example simple, it will focus on 4 additional separate instrument tracks (although using a multi-timbral instrument like TTS-1, or Kontakt, you could accomplish this by using one simple instrument track using MIDI ch 1-4). (a) Insert 4 new simple instrument tracks with your choice of instrument, one for each MIDI track that you have brought into the Cakewalk project. Your MIDI data will still be on the 4 MIDI tracks that you opened in step 2. (b) Go to the output selector in each MIDI track, and route it to the respective instrument track that you want to play the MIDI data. No need to copy the MIDI data over to the instrument track. Set up each instrument with the desired sound, and you will be good to go. Note: for this example, if you are using simple instrument tracks in addition to the MIDI tracks that you opened, you will end up with 8 tracks total (4 MIDI + 4 Instrument). It's a matter of personal preference in how you manage and use tracks, but you can use track folders to tidy things up a bit.

Agree that Cakewalk has probably struggled with the for-profit model, even as a great program. A lot of competition in a saturated market, ever smaller slices of the pie. But as a free lure to bring folks into the Meng dynasty, who knows? New game in town!

Get it here: https://www.bandlab.com/products/cakewalk

May be using some type of modulation on the pitch, causing it to dip. Might be envelope or LFO, but just guessing.

Cakewalk's future looks as good as any. On the plus side is that Cakewalk doesn't have to keep increasing sales revenue every quarter to stay alive, and that's a good thing! They even had a big presence at NAMM 2019! I doubt that failure has been considered as an option for Cakewalk, as they are still in ramping up mode. So it would be silly for them to publicly discuss exit plans. As if there is even any obligation for them to do so.

Good to know scook! There are always many ways to do something in Cakewalk!

The limitation here is that a MIDI track can only send data to one destination. You might need to copy a MIDI clip to another track if you also wanted to send that data to a second instrument.

If you insert the new instrument as a simple instrument track, you can go back to any MIDI track and set its output selector to the new instrument. In the case of multi-timbral instruments such as Kontakt, you can also assign the MIDI channel that you want that MIDI track to send to.

Udemy also has some excellent music courses. Music theory, composition, and a even few DAW specific courses for Ableton, Studio One, etc. I discovered them after getting lured into a few computer classes over there. "Hey buddy, the first one is free!"

Now that figures! A once in a lifetime sale on u-he synths! And after I blew all of my leftover holiday cash on a SampleTank 4 upgrade!

I've always been a big fan of Yes, unfortunately never saw them live. This was a well deserved achievement! I have seen Rush live a couple of times, and could imagine no other bassist filling in for Chris!

Hector, you are clearly trolling this thread. Nuff said!

All of your old products & downloads are still available in your old account at Cakewalk.com, and the ownership of all Cakewalk software and plugins was transferred to BandLab. BandLab owns and controls those old servers now. You can still install and activate all of your old stuff. It's not going away. Just not being developed anymore. Meng announced that the new Cakewalk (the DAW) would always be free. There have been no plans announced yet as far as re-releasing any Cakewalk instruments or plugins. So nobody has that information yet. They suggested we sign up at BandLab using the same email address we registered with at Cakewalk, so when/if the time comes, we may get credit for owning a previous product, and get upgrade pricing. An example that comes to mind would be if you owned the original Rapture Pro, and they released a new version of that. But no official word on anything in the plugins or addons department yet. To get the new version of Cakewalk, you need to register at BandLab.com, download and install the new BandLab assistant, and the Cakewalk DAW download will be available with that. https://www.bandlab.com/products/cakewalk A lot of the former Sonar premium add-ons have been removed from the new Cakewalk, but if you have Sonar fully installed before installing Cakewalk, you can use all of your old plugins with Cakewalk. You can install and use both products side by side.

What impresses me most about SynthMaster is its synthesis capabilities. It isn't intended to be a replica or emulation of any particular synth, but in the hands of a capable synthesist it can sound like anything, or be competent with basically any genre of music. Nori Ubukata's banks really show off the power of this synth. Nori has worked as a sound designer for Yamaha (DX-7 and others), Korg, and Arturia. Interview – Sound Designer Extraordinaire, Nori Ubukata http://soundbytesmag.net/noriubukatainterview/

I would try disabling ALL effects temporarily to see what affect they might be having on CPU (Keyboard shortcut "e").

I noticed that recently, too. Probably just an overlooked feature that the moderators haven't figured out yet. Still has the fresh paint smell around here. Give 'em time!

It's all about trying to play those nylon strings like an electric.

Not obvious. LatencyMon measures DPC (Deferred Procedure Call) latency, and a few other things. Really more of a CPU and hardware driver interaction thing, and nothing directly related to audio processing. But it can impact real-time audio if the DPC queue is backed up and the CPU cannot refill the audio buffer in time. Boom, dropout time! https://en.wikipedia.org/wiki/Deferred_Procedure_Call Audio buffer size and audio latency is something entirely different from DPC latency. Audio buffer size is a function of how often your CPU has to service the real-time audio buffer before a dropout occurs. If your buffer is set low, the CPU has to visit much more often to keep things flowing. That makes it more susceptible to dropouts if any drivers on the system tie up the CPU. That can happen, and isn't always the audio driver at fault. Audio latency is calculated based on the latency of the round trip of the audio signal, and is directly affected by the buffer size.

That's exactly what I did! That's an additional 70GB and 2000 more instruments than I have now in ST3. And I can just fit that without buying a new hard drive. I actually think I would have been happy with just the base ST4 software upgrade, and no new instruments. I will import my ST3 stuff, Syntronik, and Miroslav 2 CE and enjoy the new workflow! But with all those discounts I jumped for the regular version.

Bump up your audio buffer size (increase latency) when mixing and see if that helps. If your CPU is not maxing out when you get dropouts, your audio buffer is probably too small. You could also try freezing several tracks at a time to test for any specific track/plugin combinations contributing to the issue.

I think you can send and receive sysex with MIDI-OX, but I have never used it for that. When I started with Cakewalk over 20 years ago, I was migrating my MIDI setup from an Alesis MMT-8 hardware 8 track MIDI sequencer. Acquired my first MIDI synth back in '85. Once I got Cakewalk working, I eventually had a couple of keyboard synths, a couple of synth rack modules, and a drum machine all connected up to a multi-port MIDI interface. Using sysex and getting a grip on managing my patches was a huge job back then. So was cable management! When I moved a few years ago, all that hardware ended up in storage. It wasn't really a conscious decision to move into the box, it just sort of happened. My new space is a corner of a room, where instead I used to have an entire spare bedroom dedicated to my studio. I kind of like the idea of saving my projects now and all current soft synth parameters and patches get saved with the project. Look Mom, no MIDI, LOL! No editor/librarians either. I have a copy of MIDI Quest Sound Quest gathering dust on a shelf. It's been a while since I had to depend on sysex. But I totally understand the need if you're still running a hardware studio. So I still have Cakewalk for when I ever get the desire to drag a MIDI rack unit out of the closet.

I'm going to guess that Q49 is using a class compliant USB MIDI driver that isn't multi-client. I have a different Alesis keyboard, but there is a custom Alesis multi-client driver available for it at the Alesis website. I don't see a driver download available for the Q49, so by default it must be using the class compliant driver in Windows. In that case, if something else on your PC has grabbed your MIDI driver first, you can get that memory error in Cakewalk because the USB MIDI class compliant driver cannot be shared by two applications on the PC at the same time. Try rebooting your PC, and then don't start any other programs, not even a web browser. Then start Cakewalk and try to assign the keyboard in Cakewalk preferences. That might work. But if you still get the memory error, you will have to do some digging. Check in the Windows Task Manager on the "Startup" tab to see the list of programs that autostart when Windows boots. You might find a clue in there if you are not starting any other programs manually. http://forum.cakewalk.com/FindPost/3596618