chris.r

Such CAL you're describing I've got built-in to my right hand<>mouse tandem, that is whenever I need to I simply do it by hand , much labor I agree. I too wish I had a tool like this, this is great idea.

Definitely please mention Cakewalk as well amongst other daws. I don't have Deep but I had some UI related issues in other Ujam instruments in Cakewalk and let them know. They did acknowledge they received my report but didn't fix anything as of yet just because of too small user base, they say (maybe using other words). One particular issue I have is when you want to change the project tempo in Cakewalk using the spinbox (is that a term?) - the tiny +/- buttons next to the tempo input box on the right. Once you place mouse between the '+' and '-' so the cursor turns into an up/down double arrow, it freezes a part of the Ujam's GUI, most likely the upper part where you have some buttons with hidden settings, like Micro Timing.

Just a heads up: "Note: This product does not run standalone. You must already own SONAR X1 Producer Expanded or higher to use this product." from the product page

IIRC you can scan plugins from the 2 locations and then change to a new location and scan plugins there, it will keep previous plugins.

That means that the loop is not Groove-Clip enabled. You need to right click on the clip first and choose 'Groove-Clip Looping'. Also it works best if the loop is just a few bars long. I can't tell how well it can work with a song length loop, may be fine if you manage to count the proper amount of beats. EDIT: probably clicking 'Loop' button in the LCV (to the left of the 'No Slice' drop-down) will work too

Set this drum loop to groove loop first (right click on the clip and choose Groove-Clip Looping) then open it in the Loop Construction view (right click View > Loop Construction) and set the correct amount of Beats there. Now you can simply slip-drag the clip edge (without Ctrl+L this time) to make it play in loop.

Shame they discontinued the VX series keyboards.

I recon doing the same in the Loop Construction view in Cake.

Someone having already his/her full version of AT5 and wants to swap the serial# for something else?

Lasso-select with right mouse button is not intuitive at all, I've got adapted to it with time (it's extra annoying in the prv) but then it always pays back when I lasso-select with right mouse button in Windows' File Explorer etc.

Aaaargh... even on my UVI account the changelog still says 3.0.17. No way to know what's got changed.

Preparing space for 12 pages of outstanding deals on my desktop tomorrow ?

+1 for this and I wish similar smoothing out/balancing/averaging the tempo changes (!) but that's another feature request, I suppose

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.