David Baay

With ‘Recycle’ enabled, you can hold Ctrl when clicking to open new plug-in windows.

… or the project or preferences. The vast majority of issues turn out to be due to one of those three or hardware.

Old = stable

Audio performance issues are not common/consistent enough to be attributed to the app.

Much better advice in my view.

Have to say I have never done a “clean” install on anything but a new PC and would never recommend it without hard evidence of “corruption”. That’s a total copout, and for an automated reply to suggest it is really egregious..

Yes, critical points.

Selecting the clip(s) to be transposed would be a prerequisite for any method. Event Inspector is a control bar module and always present in mine - nothing to open or close except possibly the control bar itself.

I actually checked that before posting and it didn't seem to be a problem with the Bounce Buffer at 20. But there could be an interraction between the two settings, and you're right to point out that some plugins may not play nice with 64-bit DPE.

That might be handy handy but I don't transpose often enough for it to be a big time-saver over entering '+2' in the Event Inspector's Pitch field.

@Cobus Prinsloo Looks like those tracks probably all have Prefader Sends to 'aux reverb'. If you don't have LinkPFSendMute=True set in Preferences > Configuration File (i.e LinkPFSendMute=1 in AUD.INI), those sends will remain active when another track is soloed. Depending on what's on that Aux, you could continue to hear those tracks more or less clearly when the one is soloed.

Regarding "Apply Workspace on Project Load", you may not want to enable that. Here's why: I've just recently started using Workspaces after many years of not feeling they were useful to me because too many of my projects have specific layouts that I don't want to have overridden by a generic Workspace. When I came to understand (thanks to @Starship Krupa) that you don't have to have a Workspace applied automatically, that was the key to making them work for me. With 'Apply...' disabled, you can decide after opening a project whether you want to apply your preferred Workspace by reselecting it from the picklist. If you want the project to take on the layout permanently, just resave it, and it will open with that layout next time even when the Workspace is not applied. Then, if you do some project-specific tweaking of the layout later and re-save it, it will re-load with those tweaks preserved next time. For new projects, just save a project template that has that Workspace applied.

The demo bounces fine for me. Bouncing/freezing just that track with no FX enabled fails? What patch, and approximately how long is the region? Try: 1. Disabling FX if any. 2. Raising the Bounce Buffer Size to 20ms in the bounce/export dialog.

Interesting. I never tried it. Any other P5 features we should ask the Bakers to bring to Sonar?

Tried it with a project migrated as described, and I'm still getting just a MIDI file in the specified directory.

Hmmm... Not seing that here. It may be related to the fact that the audio is referenced from another location because of the way your migrated the project files. I'd have to try that specifically. Is that box unchecked before changing the file type grays it out?

Out of curiosity, I did a quick search of the forum regarding cross-fading of arranger tracks and found this: Auto Crossfades is applied to Section Split/Arrangement Commit Section operations now respect the Auto Crossfade enable in the Track view. Section Split and Commit Arrangement operations will now have crossfades applied when enabled. EDIT: I played around with this and found it has limited flexibility because the max auto crossfade is 25ms; it's really only suitable for removing pops and clicks. It needs a dedicated crossfade setting that's capable of a much longer transition which should be doable since it works offline on Commit Arrangment (or Insert Committed Arrangement which is what I used to test it).

It's simply the converse of your "systems should not force Humans to waste Life/Times simply for their- self-centered view points." Development resources are finite; the development or enhancement of any particular feature has an opportunity cost for other features that may be more broadly useful to more users. And individual users are as likely to make self-centered feature requests as companies are to make self-centered choices about which ones to implement.

Sounds like you're saving as MIDI to a project folder already created by previously saving as the default Type "Normal". You just need to make sure you're changing the file type in the Save As (or Save a Copy) dialog to MIDI, and navigate out of the project folder.

Definitely not a common experience. You should submit an affected project to the Bakers.

I'm curious what this means, exactly. For me, the initial migration of a project from CbB to Sonar's scalable UI requires adjusting the position of some pane splitters and changing timeline zoom level to make the layout of a given project look exactly the same, but it's far from 'a jumbled mess', and doesn't change with 'every update'. That's expressly not recommended as was implied earlier in this thread. Maybe you mis-interpreted that statement...?

Keep in mind this applies to the lives and time of developers and companies ('corporations are people, too', you know) as well as users. It may not be worth the time to develop a feature that does not have broad applicability/usefulness especially if it requires drastically re-architecting the underlying logic, posing the risk or introducing new defects or breaking backward compatibility. That said, I imagine that some basic implementation of cross-fading arranger sections could be very helpful to those who use it. I'd be interested to see a simple example project showing how this works Right offhand, I don't see how it solves the problem of not having overlapping audio to cross-fade without moving segments in a way that affects their timing.

RPN/NRPN messages are part of the MIDI 1.0 standard and thus originally designed to control hardware synths. Some soft synths will have particular parameters that respond to RPN/NRPN messages (usually things that have traditionally used them like Pitch Wheel messages), but the vast majority will use the 'normalized float" values that run from 0 to 1.0 (100%). Internally these are 64-bit floating-point values offering waaaay more resolution than the thousandths of a percent that the Sonar UI presents, but that resolution is about 6 times what an RPN/NRPN running from 0 to 16535 would offer. As pointed out, you can enter those small increments in the automation node properties dialog. Many Sonar parameters can be fine-tuned by holding Shift while dragging; unfortunately this does not seem to be implemented for moving automation nodes. This would ba good candidate for a feature request, possibly including the abillity to scale the automation display range so you could easily see what an envelope is doing when it's only varying from, say, 0 to 1%. Finally, I'll just mention that the extremely small values you're having to use for Reverb level could probably be mitigated by lowering/shortening the Decay and raising the Damping.

I resemble that comment. ;^)

Yes, I don't know offhand what's typical for other DAWs, but Sonar does have a zoom-out limit. It's in M:B:T, so if your recording is independnet of the project tempo, you can get more absolute time by lowering the tempo. FOr example, the M:B:T limit on my laptop with the Inspector, Browser and Tracks pane closed to maximize the Clips pane, I can see about 2880 measures. At 125bpm, that's about 90 minutes, but at half that tempo, it's 3 hours. At the minimum tempo of 8bpm, it's 24 hours.