chris.r

This. The famous M. Jackson's Thriller sound. For $1500 I wish they shipped it with the hardware .

On my system I only have a dialog box saying "Failed to execute script WavesLocalServer" during scan the first time I run Cakewalk after updating Waves Central, but then it's all working ok and the dialog box never comes back, weird. In Task Manager I can see two WavesLocalServer processes loaded during the first scan.

That's what I would expect as well, thanks for sharing your thoughts Larry. So I'll be skipping the update in accordance with the saying "don't fix it if it's not broken"

Out of curiosity, what would be the benefit from updating waves central? Does it make any influence on how the waves plugins work, or it's just about the waves central alone and I can just skip it until I'll need to install/uninstall some of the plugins? Thx

Select your MIDI clips, then menu Process > Length, by 50% make sure to check Durations if some of the drums are note-length dependent, like for example a reverse cymbal on some drum machines EDIT: Emmm... to halve the tempo of these clips, choose 200% instead of 50 (guess I need another coffee by now)

I'm right now working on a project with Modo Drums, except the useless preset up/down buttons no issues here as well.

I slightly prefer Pianoteq over Lounge Lizard, when playing with live band and doing some recordings, it did mix very well with the rest. I only had Lounge Lizard 3.4 and Lounge Lizard Cakewalk but the bark was always just a bit too artificial to me, maybe that's got changed in v4 full version...?

I didn't notice any problems with the EQ but I have always had same problem, you describe, with AVA Deesser. Recently I reported it to Harrison and got a reply that they have probably nailed the issue, but I have no idea when they will release the update and how to check for it.

Yes, the Event List would be much more effective if it allowed us to do bulk edits, filter single CC# and I could have much more ideas for it. For what you're asking, Nigel's suggestion would be the quickest. I would also advice getting familiar with Find/Change process (formerly known as Interpolate) where you can do much more than this in just one swoop.

and maybe some estimate of the CPU usage for the plugins/synths so we could get the first suggestion from our DAW what plugins to freeze first, not that it's crucial but could be handy... sorry for off topic

Ah yes, I remember that organ comparison now. He did an extraordinary injustice to the Blue3's leslie effect ?. Overall I find doing such videos a highly noble idea especially that he did care to put the sound in a context of music but I know Blue3 just too good not to notice that there was something going far far off with setting the leslie. In my opinion Blue3's leslie effect is one of the most natural sounding leslie captured sound, note I mention 'captured' like listening to a recording, not like staying next to the real cabinet (L'otary anyone? ), of the bunch only IK's leslie can rival Blue3 for natural, captured leslie sound, imo.

support@cakewalk.com

Yes, that's what I see. I checked again and found out that for some recent testing reasons I had Vertical Grid Lines set to 'In front of clips' which I typically have set to off. If I turn the grid lines off then I can see bevels more clearly. But I still have an impression like I'm missing some sort of a trail around a grooved clips, a kind of a dashed line. But I'm no more sure. Are you using custom skin?

I can see rounded corners here but the change is so small now, almost unnoticeable! It used to be much more distinctive in the past.

Almost 5 sites reading to just get two or three substantive responses, oh well Regarding legato CAL script not working anymore I didn't check yet but I'd say it would be sad if it got broken. When I was using it, I remember that I had to do some reasonable preparation on the clips itself first in order to make it work properly, like cutting or replacing the first note at some specific time. Overall I think the best thing we can do about it is asking developers to put a new "LEGATO" command in the Process menu - as many times as we can! That's one of biggest missing core features in Cakewalk's MIDI department. The 'sndfile.dll' bug is a Waves bug and have had accidentaly occured at this time, and as I see it had been already explained. Glad to see Noel already logged the quick group bug, that's great news. ? Regarding time stretching problems, I don't try to say that Audiosnap is entirely bug free but I kind of agree with Jonathan Sasor saying that in your case it's more of an user error rather than a bug. Besides you need to remember that Audiosnap will in almost 100% situations work with regard to transient markers that you've enabled, so that shouldn't be overlooked as well. And a question, correct me if I'm wrong but isn't a Groove Clip rendered with Elastique Pro (or Radius, if you prefer - I prefer Radius Mix over Elastique Pro 6 days in a week) when we bounce to clips/tracks? Maybe that's just the one step you're missing to get the quality - bounce your stretched clips once you've done. Lastly the cut/paste bug. Indeed there is a tiny bug in the way Cakewalk is handling selection when you cut. Just watched your video again - observe the selection on the Time Ruler changing the moment you hit Cut - there is your bag so the workaround would be always to select clips with only lasso (right mouse click+drag over clips) and this way have no empty area before clips discarded from selection after you hit Cut. And I think, but I could be wrong, that perhaps the right person to ask for dealing with this last bug would be @msmcleod...?? IIRC he did correct similar bug a year or two ago that I reported (Cakewalk didn't remember selection after Ctrl+Z, it was), so there's a hope. BTW as we're on it, I also don't like how Cakewalk looses tracks selected when we try to change time selection manually in the Time Ruler i.e. I have a few clips selected across a few tracks, when I drag any of the selection markers with the mouse, Cakewalk will change to only one track selected, only the focused one, discarding all the other tracks. But maybe that's for a purpose, idk.

I remember reading that someone called an audio driver a background process and that way justifying prioritizing background processes. My Ploytec ASIO driver has it's own setting for how much I want to prioritize it so I should have nothing to loose changing back to apps.

Glad nobody told me over the years or else it could have stopped working for me. And I think I got it from some well regarded source like SOS etc, back then.

So far only Reason reported an error after finding the whole AAS collection in my main vst folder (Program Files\Cakewalk\Vstplugins) and then the exactly same bunch of plugins in a subfolder (Program Files\Cakewalk\Vstplugins\Applied Acoustics Systems). What would be the reason for doing that? Before I was doing last update I first uninstalled everything AAS and then installed just to the subfolder, according to what the installer suggested (did carefuly notice the path that was displayed). It did install to both, the main folder and the subfolder then, plus everywhere else around the area here as we already know.

Thanks. Glad you've got away with the jab. I'll download the project also, to see it here on my side. Curious what's going on. Cheers

BTW i dig some more just to see something and indeed, if I set a sysEx reset at the beginning of a midi file, Cakewalk will automatically shift all events by an arbitrary amount of ticks, including the Program Change from 1:1:000, so that should work ok. The thing about it that terrifies me though, is that such an imposed intelligence, where Cakewalk is implying a common standard and shifting midi events back and forth at it's will, in any non-standard scenarios like for example when using less-known hardware synths that use their own proprietary set of MIDI rules, can lead to a shot in the foot. *I am in no full control of where exactly my non-standardized midi events are going to take place in the resulting midi file.* But I realize that's already too much of digression from the topic so sorry about it. I just wanted to vocalize that concern since I was already at it.

So what is the general consensus in XXI century, are we still supposed to set the priority to background processes? I was doing it since 90-ties and never looked back. That was always one of just few tweaks first done in each next Windows build for me.

Ok found out another way, luckily there's the Sekaiju! With it, I can see the duplicate Program Change events though both are set correctly to Vibraphone or whatever I set in there, so that seem normal since I was working in a *.cwp file first and then saved as midi file. The only quirk I've noticed is that in the track header, if I choose MIDI Channel = None and save as a midi file, the whole PC event don't appear in the midi file at all (it may be intentional though), there will be only the second one, that was there a bit later in the event list at exactly same position where I have put it. And if I choose any MIDI Channel in the header, the PC event will appear in midi file but always exactly at position 1:1:000. Hmm, not sure how is that suppose to work with GS/XG modules that used to receive sysEx reset at the beginning. So for the moment I only could check if exporting a midi file is working same way that you see. To be able to check what is Cakewalk sending in realtime I would need to install MIDI-OX here, but I'll rather do it another day, cause I'm right now going through the ugly covid and my willing to live is low ATM. But I see Mark wants to see your project file so you're in good hands.?

That's my understanding as well. The ins files are only to help speed up with surfing through the preset names and banks (provided that someone did already the hard work and handed it to you). IIRC the only thing that could matter is that you can specify the right bank select method for your instrument in it. But bank/preset changes should work even with just the numbers in the Event List. Since Mark has confirmed that he can reproduce it in his post above, question is whether it is a bug or something is wrong with your settings? Unfortunately I can't fire up my old trusty Cakewalk Professional 3.0 in Windows 10 anymore (or don't know the secret way but any compatibility settings don't seem to work), so I can't just save a MIDI file and load in it to see what is going on with MIDI events, and that used to be my quickest way before if I had to check some weirdness in the Event List. Since Sonar times and later, some MIDI events are sucked out from the event list and get populated in the track headers whether you like it or not, not much I can do about it.

Until the upcoming interface revamp, maybe a small change in the project length can help offhand i.e. put a marker or controller event at the end and just nudge it forth and back by a beat between revisions.

Honestly, I have no more idea how to help any further It's been a while since I was last sending PC to external gear but it may be now good time to install MIDI-OX and see what's going on here on my setup simply because I may need sending soon again.