José David

Hi all, justed wanted to share a little episode I had with dropouts, although it's almost a joke it may help other people to avoid the same aggravation :-) All of a sudden I started to have a (11) code dropout message consistently and continuously. It was a long time, after trying a lot of different things such as suggested in this thread and in the Cakewalk manual, that I realised that I had the function active with a zero length loop segment (i.e. start point = end point). It was this that was causing the dropout, I think I must have pressed Shift-L inadvertently. As it happens, if you press SHIFT-L without any selection (as when you have just opened a projet) Cakewalk sets a loop segment with both beginning and ending at "now time" and activates loop mode.

Hi, thanks for the brilliant work, this is surely the result of a gigantic effort that you are sharing with the community. I'm trying to initiate myself in (rudimentary) orchestration and this seems like an excellent means to it. A basic question, though: in practice, how do you work with the different articulations of an instrument? Do you have do create separate instrument instances (or use different layers in the same instrument) and separate MIDI tracks (and different channels, if using a single VST instance) for the different articulations? thanks and regards josé

Hi folks, I've had Cr8 perfectly working before and now it didn't work, as for many of you. There's been a Cakewalk update since I had last used it, but of course I cannot know if that's something to do with it. After reading the previous posts I resorted to reinstalling the product again, using Waves Central and now it works. To be sure, I removed previously removed all WaveShell1-VST3 13.?_x64.vst3 files from the VST3 folder and, sure enough, the installation procedure recreated these files anew, one for each WAVES product I have on my system (I reinstalled them all). The file for CR8 is called "WaveShell1-VST3 13.4_x64.vst3" in my system (not sure if it's always the same, as the other products have seemingly random id numbers). regards and good luck to all josé EDIT: ups, not quite as described above. In fact, CR8 started to work, not because of the reinstallation, but because Cakewalk rescanned the old versions of the WaveShell1-VST3 13.?_x64.vst3 file. I had it renamed to ".vst3XXXX", apparently the scanner ignores the characters beyond the 3rd in the file extension and treated these files as valid VST3 dll's. I've then removed the old file from the folder altogether, and CR8 was no longer available inside Cakewalk. I've reinserted the old VST3 file and it's working again (I've deleted the VST3 file created today by the reinstallation and it's still working). It seems is that the renaming made Cakewalk see it as a new VST3 and scanned it. Strangely enough, I had done a full rescan with "rescan failed plugins" and that didn't work. No idea why the new .VST3 created by the new installation doesn't work and why the old one stopped working and now works again. But if you have the WaveShell1-VST3 13.?_x64.vst3 file in the VST3 folder and Cakewalk is not scanning it, try to rename it (I don't believe in magic, but I'm sure it exists 🙂

I was struggling with the same problem exactly (Musescore exported MIDI crashing Cakewalk when fed to sforzando). I had just installed the most recent version of sforzando (1.967) and also installed ARIA latest version (1.959, found here https://store.makemusic.com/Downloads/Default.aspx?id=665), installing only the VST3 plugin in both cases, naively thinking that that would get the best results and compatibility. Resorting to VST2 of sforzando did solve the problem. Thanks for all the tips of the previous contributors. BTW, I didn't try to use ARIA again after getting sforzando to work, as I find the sforzando interface more user friendly (for what I do), but I confirm that I could install use ARIA without any purchase or license (if only if it did not crash... :-)