brundlefly

- 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.

All clips are effectively just representations of underlying stored MIDI events. When lanes are showing, the clip in the main/parent track at the top is a composite representation of all the events in all the take lane clips merged together. Deleting from either a take lane or the composite clip deletes the underlying stored event that both are representing. Your desciption of the problem suggests the CbB spontaneously created lanes on opening a project that did not previously have lanes. This can happen with a very old project that was created before lanes superceded layers; CbB will convert the layers to lanes and expand them automatically for all tracks. But if the project originated any time after lanes were introduced (SONAR X3...?) then I'm sure they were already there when you last saved the project and you just weren't aware of it because the weren't showing and editing a multi-lane track without lanes showing is just like editing a track with everything merged to one clip. The circumstance under which SONAR/CbB/Sonar will create new lanes for MIDI tracks has evolved over time, and may have some dependency on the setting of Non-Destructive MIDI Editing in preferences. At one time, I thought it was intended that same-lane overlaps would not be allowed by either recording or editing, but editing seems mostly to allow this now for MIDI, so automatically created lanes are usually a product of recording. Without knowing the full history of the project it's hard to know exactly how you got where you are now, but I would guess it happend gradually over time as opposed to suddenly manifesting in the latest release. In any case, so long as you aren't actually seeing duplicate clips in lanes, Bounce to Clip(s) can be used to consolidate everything as mentioned.

Musically, the last transient of the clip you posted is at 3:01; i.e. the clip is effectively 9 beats long, and wouldn't sound right as a loop unless you repeat it every three measures. Using that last transient as a reference, and trimming the dead air before the first transient, the clip averages 117.58bpm, but the timing of the transient at 2:01 is a little late. Here's a clip that's been Audiosnapped and bounced to have a consistent tempo, and extended to fill out the 3rd measure. If you import it into a 117.58bpm project (I suppose I could have rounded it to 117.6), loop the three measures, and listen to it with the playback metronome enabled, you'll hear what I'm describing. EDIT: On re-listening, it at actually sounds pretty natural if treated as 10/4 time, i.e. looped every ten beats, but I doubt that's what was intended. ;^) 117.58bpm - 3 measures.wav

Check the Playback Timing Master. Sounds like something got mixed up with Audio mode/driver selection. If all else fails try Reset Configuration to Defaults. CbB will back up your AUD.INI and replace it with a default. If it works, you can compare them to see what's different and selectively restore customizations.

Nothing new under the sun. All the options were discussed here... a decade ago : http://forum.cakewalk.com/Quickly-transposing-midi-notes-up-or-down-an-octave-m2837805.aspx

I lot of users have requested the option to have new/looped takes merged into an existing clip. It's not necessary for my workflow, and I generally want to keep everything separate, but I totally understand and support having the option to merge in real time. But rather than having another record mode like "Overdub", I would suggest they just add a toggle box to 'Merge Clips" under the Take Behavior section of Record Options. Persistence of the "confidence recording" indication while loop-recording MIDI also makes a lot of sense. As it stands, it's really only an indication that events are being received, and can actually be deceiving; if the port of channel of the incoming notes is not matching the input setting of the track, you'll see the notes appear while recording but they won't actually be recorded. I've formally reported this problem to the Bakers more than once over the years.

I would try some things before reaching that conclusion: First, export just the Master bus and see if that succeeds. If not, try exporting all the sub-buses individually and see if one in particular hangs. If so, try exporting/freezing tracks that feed that bus to narrow it further. If exporting all the individual buses succeeds, try disabling/removing suspect plugins from the Master bus.

I'm not aware of any updates to TTS-1 since it was was ported to x64 and can't imagine that Roland would have fixed/upgraded anything since the Bandlab acquisition. But only someone with an un-updated installation of CbB with TTS-1 still intact could tell you for certain.

Funny, I read exactly the opposite. Why bother to say "currently or "at this time" if you have no plans to do something else in the future? The removal of "Early Access" is just an indication that it's considered stable and fully functional and ready for wide public release without reservations.

A bit of an exaggeration. Mercury was the original color scheme of SONAR X1 when the Skylight interface debuted in 2010. Pro Audio 4.0 of 1996... now that's a retina-burner. ;^)

Which theme? I don't see a significant difference between CbB and Sonar with the Mercury Classic theme.

FWIW, I always keep old versions around so I can tell whether something that's not currently working/appearing as expected is a regression.

Per the website it's Cakewalk Sonar: https://www.cakewalk.com/sonar Since the mixed case "Sonar" distinguishes it from 'old' SONAR and Cakewalk is back to being a subsidiary company of Bandlab rather than a product of Bandlab, I'm lobbying to just call it Sonar on the forum.

Welcome to the forum. FWIW, I mentioned this in an earlier post but without any particular emphasis or detail since the OP was so broad-ranging. To be precise, it's Process > Find/Change (previously Edit > Interpolate). You make a good point that CAL (technically deprecated long ago but still working at this time) can also be used after the fact to address some limitations in what can be done in real time, but the OP seemed to be mostly asking about what's possible within the main program and in real time in the way of MIDI routing/filtering/transformation so CAL didn't come up. The third-party CAL programming guide and even editors can still be downloaded from various sources. The best/safest/most current of these is always changing so I'll leave it to future prospectors to find it for themselves.

As I recall, providing some level of theme editing has been mentioned as a long-term goal by one of the Bakers, but I be hard-pressed to find the reference. Notwithstanding the reponse that Stephen got, if enough users express concern about specific contrast/legibility deficiencies, I think it still has a chance of improving in some areas. That said, my vision is not the greatest but I'm getting along pretty well with Sonar even on my 15" laptop that shipped with scaling set at 200% and which I've reduced to 160% to be consistent with the scaling of Sonar on my larger desktop monitors where the fine dialog font is not really a problem.