chris.r

That would be huge, though not enough for for some, me included. I'd wish for example, for every controller line, somewhere on the left, a folded list of all available controllers, where we could freely enable/disable each cc#, to show only those we'd want to work with on that line, and for that moment (for example we could get two lines with separate controller sets for Osc1 and Osc2 of a synth or two separate drawbar sets of upper/lower keyboard - to compare/edit with reference to each other and notes), AND enable/disable a chosen cc#(s) for overwrite-recording (similar to write-enable an envelope). That's just top of an iceberg what ideas could be added to the editing toolset, some of them, really basic, much missing. But like I said, I don't see midi editing anywhere on the top of requests for most of the userbase, unfortunately.

The piano roll section for editing controllers is fine if you're dealing with just 2-3 controllers, if you have to deal with 20-30 then it looses sense. I just opened one of my projects with only one instrument... the Hammond organ . And instantly remember the hassle when it comes to edit the controllers. If you're going to record the organ track properly there you can easily exceed 30 of them in one track, 2x9 drawbars for both manuals plus at least 2 for the pedals that's already 20, then there is expression pedal which in some cases is moooving constantly the whole track populating it with never-ending waves of cc#11 events. Plus some intermittent leslie switch movements, drive, volume, click, V/C, rocker switches and cabinet settings... many of them drawing at once in the prv! I mean, just working on the expression pedal alone in prv is a grind, not to mention if you'd want to overwrite just a single controller events line, for just a part of the song. There are no tools. I can't see how working on orchestral tracks would be much different, except there could be even more hassle in big projects.

From a few sources I did see that the AAS guys are no longer in love with Cakewalk, don't know the reasons. Better let them know the crash happens in all DAWs (I'm sure you did).

I feared twice already what the improved behaviour could mean... more places where the plugins are installed? On a serious side I can hardly see a benefit from updating for just improved installer behariour (have only Chroma.v2 and the sessions).

Agree, best way for a DAW is to get the least in the way when you're making music but then serving you a huuuge hand when editing especially when dealing with tedious tasks - the more tedious, the more we should lean on the DAW.

In your situation what I would do is select only the wheel events by using menu Edit>Select>By Filter or simply lasso selecting by hand in the PRV (wish there could be more editing tools re cc events in the prv) and drag them to another midi track that's being sent to the same instrument. Now I could re-record only the wheel using comping or punch-in methods. Typically, working on midi controllers is a bit more challenging. I too wish we could have more convenient ways when working with midi, especially the controllers, but then I realized that we're rather on the niche side compared to the whole user base with this, and have to arm ourselves in more hope and patience . I've heard often Logic being recommended as best DAW for orchestral work, this could well be the clue (plus the visual presentation of midi when zoomed out).

Presets are there, you have to pull them from VST3 drop down and navigate to the right folder on your disk, as scook says. Very inconvenient, we're basically left out without any preset manager for PA VST3 !

I almost read the video title: HOW TO FEAR COMPRESSION

Dang! Is that true? I was eyeballing at that controller recently... shame.

Beside the paths you mentioned, it's putting the whole collection in my 'C:\Program Files\Cakewalk\Vstplugins\' and then it adds the exactly same collection (doubles) in C:\Program Files\Cakewalk\Vstplugins\Applied Acoustics Systems\'. That way they are always scanned twice in one go, I have no idea how to stop it.

Do you know, by a chance, if the AAS plugins have any install paths written in the registry, and where? Maybe my issue with doubles in my Vstplugins folder comes from the installer writing the new path in the registry when I was changing it at some point, but not deleting the old one... it just occurred to me.

Thanks for the heads up @Matthew Sorrels! And good luck in solving your issues.

In terms of quality customer support I have to mention UJAM, excellent experience even if they didn't have a direct solution for my Cakewalk issue it's still very rewarding. And another vote against online-only authorization method here.

Brilliant! I just came back from hard work of cleaning my drives from AAS plugins spammed all over the place (and even twice in my main Vstplugins folder!) and need a shower now. If it's a some OSX maintenance update I simply don't wanna go back there to clean all that stuff again. Please keep us posted .

Well it's just too difficult for me to find the change log on their site, it seems ?

As we're on the freezing topic. I was always trying to avoid having to freeze. as often as possible, and the main reason for it always being that I feared of loosing the exact instruments/effects state after unfreezing. What are your insights about freezing, is the problem occurring often, or maybe, for some of you, never? How often you guys use that feature? I had some bad experience with Synthmaster not properly loading it's saved state where I had to re-load the project second time and everything was fine then. Hate to have my head always busy with checking if everything is playing correctly but that's how it is now in Cakewalk, always have been. I assume with freezing Synthmaster I'd experience similar issues now and then. Was wondering how are other plugins?

Missing those jrrshop codes...

I agree that slapping Tape Machine 24 on every track would be the best scenario but with it taxing CPU as much one would need to upgrade to the quantum-CPU to make it even start working. Maybe if IK allowed us putting an instance on each track but then mixing them all internally into a single instance in the background, that's a similar idea to what sknote's Strip is doing (plus it's adding some fancy crosstalk and whatnot), but in that form it's already not far from just using a bus.

I've got TapeEcho and the four Tape machines already so it looks like it's just one plugin for the price of one for me, hmm... ?

Just had to delete some of the NI/EastWest/Sampletank/etc. libraries from my tiny overcrowded drive to make room for this one!

now waiting for that BOOM...

can share my code if you want it

^^ yes, this!!

To follow up, I just had a Cakewalk crash when trying to load Waves EchoSphere. Upon the next Cakewalk launch vst scanner told me I have one (1) plugin less than I had before crash. The EchoSphere is still there and working fine. Go figure out. ?

@scook brilliant.. that was it! thanks