sjoens

Easiest way I know: 1. Save project as a new one so old one is preserved. 2. Bounce clips in each track so there's only one clip per track. 3. Extend all tracks/clips to same length as longest track/clip. Do not bounce. 4. Set Now Time Marker to -0-. 5. Click on Transport BPM and change to desired value. You'll see audio clips extend past the end of the MIDI tracks when increasing BPM. 6. Slip-Shrink the Audio clips to line up with the MIDI clips. 7. Bounce the audio clips. Slip-Stretching/Shrinking MIDI clips is virtually harmless. Slip-Stretching/Shrinking Audio clips can range from harmless to disastrous, depending on how vast the BPM change is and how complex the audio is. I just changed an entire mix from 120 to 135 BPM without too much issue - audio was shrunk?... shrinked?... 88.89%, but I wouldn't recommend doing it for a polished master. If tempo change is significant it's probably best to re-record audio parts... or spend a lot of time in Melodyne.

Yes. But not likely anyone will notice or care.

Because that's how previous Sonar apps worked. Sonar X3 behaves as expected with new and old projects. But if I open an older project in CbB, it also behaves as expected. So creating projects in CbB must be affecting the Solo routine somehow?? In any case, CbB will probably be deprecated with a host of unresolved bugs - just like any program would where there isn't enough time to address them all. Incentive to upgrade.

Not sure what intended behavior is, but it seems like when Soloing a track the remaining tracks should look darker or diminished. For some reason MIDI tracks aren't responding to this action. Checked Sonar Platinum and all but one MIDI track dimmed when another track was soloed, so something changed.

I can't reproduce your issue. Snap has never worked 100% for me in Track View or PRV but it normally works as expected. When Global Snap is on and PRV Snap is off, notes can be moved more freely with less 'magnetic pull'. When both Snaps are on, notes are pulled to the set resolution. Are Global and PRV Snap set to the same resolution?

Everyone's different. Probably no easy solution. I do change track names to my liking but they still reflect the synth name, so when I use "Replace Synth" I have to change the names anyway. It's when I forget to and the old name is still there when I can get confused. It gets more tedious when multiple MIDI tracks are involved.

Yeah, to my thinking, Cakewalk should change the name to the new synth even if I had renamed it before the change. Cause the old name usually reflects the old synth. If I change the synth and fail to rename the track, then come back later to see the old name still there (10 yrs later), I may be confused.

I assume once you change the track name, somehow Cakewalk is prevented from renaming it when you replace the synth. I would prefer it still did, tho.

Replace Synth routine is supposed to rename default track names. 1. Menu > Insert > Soft Synth... Synth loads with each track named after the synth 2. Right click track number or synth icon 3. Select Replace Synth for All Tracks Using This Synth... 4. Select new synth New synth replaces old synth and renames tracks accordingly. Only this does not happen on my system consistently.

FWIW, Quick Grouping can work with Replace Synth... if Instrument Track Per Output is selected when initially inserting a synth. and BTW, there appears to be a bug with Replace Synth... where default track name does not always change to the new synth. edited for clarity

You can also left-click & hold the button for a dropdown menu which also contains Take Lane options. All buttons with a lower corner arrow do this. Because it may contain some good parts? Maybe? SOS is all I ever use.

WIN+ "+" followed by WIN+ESC to return... on Win 11. Here's hoping any older plugs included with the new Sonars will be GUI enhanced to fix the "fine print".

I did now , There were several areas to add and Allow. All good now.

D'oh! Maybe of note: In Chrome the legacy pages open in perpetual loading (spinning circle) and images are broken even after adding the site to Chrome's Allowed list. My guess is it's trying to load the pics but can't. Pics can be right-clicked and opened in new tab, tho.

Looks good here. However, the in app link takes you to the Introduction page. You have to click on "Cakewalk" to find the Index. Wondering how the help docs will be affected by the new Sonar releases?

@Terry Kelley & @Bruno de Souza Lino You are both saying the same thing. PC indicator is missing on the Track View strips. Perhaps this is because there's no way to access PC from the Track View. Adding a "PC" button next to the Phase button would work too.

Inspector and Flyout QuadCurve EQ have fixed scales of 0-18. They do not change. When Console View QuadCurve EQ grid is set to Options > Plot Resolution: Auto, it cycles thru 4 scales: 0-6 default 0-12 triggered by a Gain value of 6.7 0-18 triggered by a Gain value of 12.6 (should trigger @12.1?) and 0-24 triggered when 2 highly set Freq ranges overlap, typically one @12.8 and one @17.7. The last scenario will cause the Inspector and Flyout EQ graphs to go off screen. Theme Editor only includes the first 3 scales so if you repaint them, the 4th one won't match.

After the new Sonars are released this issue will be deprecated.

Just 'cause we don'ts whine don'ts mean we Very true... Because though Logic is very good, if you're on windows, Cakewalk (SONAR/Sonar) is better! Mac users whine. Windows users just suffers in silence. I'd have Logic if it was a Windows app. But I'm not buying a Mac just to have it.

After a closer comparison with MX9 I found there was no discernable difference in appearance at normal scale. But MX10 looks slightly better when scaled internally or by Windows. SVG files are often smaller than PNGs. In MX10, SVG files are interchangeable with PNGs or even RGB colors... so theme editing isn't a total loss.

For those worried about an all vector GUI, you can download Mixcraft 10 demo and check it out. It's GUI now uses all svg files and it DOES look better. My only issue ATM may be how difficult it is to create usable svg files. I can create them just fine but MX10 doesn't want to display any of the ones I've edited. It also seems there are variants in the svg format.

.

I wouldn't say "irrelevant" unless I can re-create a couple of nice themes I've worked long & hard to complete. Colors are nice but imagery is everything. I get not using images from a developer's viewpoint as scalable GUIs require multiple sets of images to implement sizing requirements. Editing multiple sets of the same images would be daunting. But I have more issues with plugin text than I do with the main GUI text.

We may not be talking about the same text then as I haven't changed anything on it. FWIW, only the images in the Resources folder are changeable - no value text.

I just want it to work... .