sjoens

Double clicking a MIDI track clip header (top of clip) opens it.

Link to new request:

Update the Preferences > Audio Meters window to include all meter options. Current Options > Meter Options routine requires numerus trips into the menu to set and reset each meter.

Going thru Options > Meter Options has always worked for me. Rightclick changes won't stick beyond your current session. Even so , the current meter settings process is quite clunky. As for the # of repeated clicks on the menu tab to get everything in order, I requested - in The Bakery which is no longer in existence - a consolidated meter menu in Preferences so you could make all your clicks in one comprehensive window. As it is, you don't even know if the box you clicked was even selected as the window poofs off screen before visual confirmation can be made.

If it works for X3 and below that's good enough for me. Let me know if you need beta testers.

Great. More buttons to customize .... and what about EXE Colors?! I hate teasers! ….

Confirmed here.

https://www.bandlab.com/products/cakewalk/whats-new

Above pixel 56 your meter is fine, but in order to look right you need to change all colors below 56 to the same color. You're using a color gradient below this point causing the effect you see. From pixel 56 down, Cakewalk repeats the graphic until the audio signal reaches -6dB at which point it begins to display the upper part of the graphic. This is because the meter has only one graphic to accommodate 6 different dB ranges (12 to 90). If each range had it's own graphic, you could achieve the desired affect. The X series wasn't originally meant to be customized so it's a limitation we live with.

Do you realize the bottom half of the meter is its background (which can be totally transparent or empty if you want) and the top half is the meter? So when designing the meter itself, edit only the top half. Post your meter.png right here like a screen shot and I'll take a look.

And along with all this, I've had X1 and CbB invoke the BSOD 2 or 3 times in the last week for doing absolutely nothing but opening & closing Preferences.

It happens to me if I turn on my USB controller after CbB is already running.

CbB may not crash as much or for the same reasons as the X series did but it seems to be catching up for me. I have one system that runs everything I do so it's bound to have more mishaps than a CbB exclusive system running minimal resources. Without the latter, you'll never be able to completely isolate particular issues. In my case, X1 seems to be the most stable version presently and have gone back to using it more frequently. It works best with my new controller and even opens while IE11 is open, something CbB will not do. If I turn on the controller after CbB is running, CbB POOFS! off the screen as if it was never there. I can then reopen it without incident. It's also possible that having every X version installed could be affecting the issues.

Sure. Tho it's not implemented quite the way I wanted, it is there.

Although "Friendly names" would be quite tedious for me with 24 entries (8 inputs X 3 choices each), I like the idea.

Thanks for the education. I guess this "request" can be removed as it is technically already implemented, technically.

I use all versions of Sonar for various reasons and have found CbB to hiccup, fart, crash, and burn just as easily as the rest of the gang.

Insert Instrument = Combined MIDI/Instrument track (which I never use). Insert Synth = Choice of Instrument track or separate MIDI/Synth tracks, which I always use but have to use the File Menu to get it.

Yeah, mine are so infrequent they can't be reproduced. I always use sound on sound, never comping, so it shouldn't be happening.

Some rgc:audio sfz FYIs Version 2.0.0.1 SCAN OPEN LOAD SF2 files CbB 64bit yes yes no Sonar 32bit yes yes yes Version 2.0.0.0 (2004) CbB 64bit no no no Sonar 32bit yes yes no SFZ Standalone - yes yes

… right-click menu of Track View? Seems an oversight and would be so handy.

I've seen and reported similar behavior years ago. No one had an answer that I can remember. There's times when "the machine" just does what it wants to. For me, clips would overlap as expected but then after awhile, for no reason, just moving a clip over another one would cut it at the intersecting point. When this happens, it may be possible to simply drag the clipped end back over the other clip where it should be, but I never tried that.

True. I do all my editing in PRV and then wonder why all these "clips" are floating around in Track View. For me it's usually an annoyance to clean them up.

+1 for Bouncing. Highlight the entire track so all clips are selected, then right-click and choose Bounce to Clip(s). They will all become one clip so that you only have one full length clip and one righthand icon. There is usually no reason to have multiple MIDI clips floating around on a track unless you're comparing takes.

I use VSTSynthFont64 and it works. Maybe something's wrong with your set up? Yeah, I forgot it only works in 32 bit Sonar.