David Baay

A. To keep you from leaving for a product that's being actively developed. B. To keep the developers from leaving because they're bored to tears. Like Craig said, the developers aren't in it for the money; it's the intellectual challenge of innovating that keeps them around.

As mentioned in the other thread about this, Massive X has a 'View Size' scaling factor in the pick list next to the logo at the upper left, and Ozone 11 is continuously resizable by dragging the lower right corner.

Massive X has a 'View Size' scaling factor in the pick list next to the logo at the upper left, and Ozone 11 is continuously resizable by dragging the lower right corner.

Try un-checking 'Enable Plugin DPI Awareness' in the Settings drop-down of the CLA-NX UI (and maybe SSL E Channel as well). In general I'm finding that plugins with a scaleable UI behave better with this option disabled. And some plugin UIs (especially older ones) will render too small with it enabled.

No doubt some users really like and depend on the one-click delete for their workflow and any change at this point would need to be optional/customizable (as it should have been when they changed it previously).

Yes, I should have mentioned it. I sometimes find it difficult to accurately double-click a note when the PRV is zoomed out or the note is short so usually just lasso it and use the Event Inspector... after I undo the initially mistaken right-click erase.

I should have mentioned: the option is in the Settings pick list in the plugin title bar so pretty easy to switch it as needed and to know you're changing the right plugin.

I've found it doesn't work for everything, but it is odd that I'm getting a different result with the same plugin unless maybe it's a version issue. Are you loading the VST3?

Yowza! Frankly the way all this scaling stuff works under the hood is a bit of a mystery to me, but I suspect that high scaling factor has something to do with it. I'm at only 160%. But I'd be surprised if the UI doesn't change size at all when you disable DPI Awareness...?

What monitor resolution and Windows scaling?

That would be the "Obfuscation Team", an indispensible part of any good marketing department. I suggest you submit your inquiry to them directly: http://bandlab.com/inquiries/roundfile

+1 Right-click used to open properties. I still inadvertently delete notes ? At one time you could customize tools, but not currently. The best you can do is get in the habit of using the Event Inspector.

I tried it with FM8, specifically, and it worked as expected here; the UI becomes the same size as in CbB. Possibly it's a limitation of demo mode that you can't change it.

Preferences > Display > Show Tooltips

- Disable 'Plugin DPI Awareness' in Plugin Properties for affected plugins. - I have deteriorating eyesight as well but I get along pretty well with the PRV in the Mercury Classic scheme. The keys are black and white - are you referring to the shading of the sharps the runs across the notes area? I could wish for darker/bolder gridlines, but they're usable for my purposes. It's not missing from Sonar but the hotspot has narrowed a bit; you have to hover over the lower half.

+1 Jurassic Cakewalk had this feature and I used it with some regularity.

Cool. Glad to help. I love a good mystery. ;^)

I see about -82dB at the output. FX Bypass kills it. I looked at a few tracks and found instances of Sonitus Compressor and Reverb. I didn't try removing them, and I didn't check all tracks, but that's where I'd start. EDIT - Looking further, I found Prochannel active on all tracks and buses with Tube Saturator enabled. I think that's the source. You can kill them all with Quick Grouping.

I understand that, but this thread is not really about that (or at least the OP wasn't); it's about the net cost either way. And conserving energy can help pay that cost either way.

Share a copy of the CWP file?

I'm beginning to wonder how many users could pay for their subscriptions just by completely shutting down their DAWs and studio hardware every night. I generally do, but I know a lot of people leave stuff running 24x7x52, often with Windows in high-power mode with all power management disabled and the audio engine idling with a project open. Add external interfaces, controllers and monitoring hardware, and I guarantee you're burning significantly more than $15 a month while not using it.

Almost certainly due to FX in the bin or in Prochannel. Does it go away when you enable FX Bypass in the Mix Module? If not 3rd-party FX it might be due to having Console Emulator Drive/Trim controls maxed or something like that. At one time, the PC Tape Emulator was found to be producing low level noise with no input to it, but that was fixed.

Indeed it shouldn't. But it will duplicate the lane structure of the source track if you choose to include Events. I don't use Duplicate a lot, but have not seen it create superflous lanes. I would guess there was something unusual about the state of the source track that caused it in the one case you saw.

Copy-Pasting from track to track can create new lanes if the tracks have differing numbers of lanes to start with or lanes have been added/removed over time such that each track's internal lane indexing differs. I have seen and reported some anomalies around this in the past. In particular, re-using an old project or creating a template from a project that's had a lot of editing done in it can be problematic if you don't delete all the empty lanes first. Copy-Pasting between tracks that have never had more than one take in them is generally pretty predictable in my experience.

But apparently you did because your Octave Up script is character-for-character identical to the one scook posted (which I expect he created from scratch), including the commented description. Sorry, but I consider it bad form not to have attributed the source.