micv

I inserted an audio FX to a clip, but the FX has no effect on the clip. The plug-in UI is fine but audio was not 'effected'. This is with the latest CW version. The plug-in works fine if inserted to the track. Wonder if there is a new default that has to be switched. thx

That does it. Interestingly if I shift-solo on a track the track solo icon/button is the 'exclusive solo' but behaves like normal mode. Not sure what that icon mean on a track.

If there's already solo track(s), I want to be able to hit solo on a track and only that track is solo'ed. Currently to solo each track I have to un-solo and solo. Thought there's got to be a way.

Is there any 'un-planned' (since it works so well this release ?) for off-line update? You can download and install the software, but only need to get online for authorization? My studio has barely a blip of a signal, probably just enough for auth. Always have to disconnect and take the computer to a location with signal for hotspot.

I personally haven't ran into the issues mentioned in this video, since Sonar to X to Plat to now CbB. So they look like system dependent. Way back, I did have issue which a few plug-ins not retaining setting when using 32-bit through bit-bridge in 64-bit app.

Isn't in Setting vst has the option to hide vst2 if there's like vst3? However even if you set this, Fabfilter still show both vst2, vst3

I'm about to do an update. Is this crash an isolated issue to a few and is it stable so far to most? Not sure how to roll back if there's issue so thought I ask first.

I have old projects with midi drums programmed/mapped loosely to GM, I want to use my current vst drums (BFD3) which has its own mapping. What I have to do is manual move each note to the new note. I have worked out the exact note for note translation, but wonder if there is a script or better way to do this.

It's clear to me that Lens and Screenset each has its own place: Lens=customize your layout/menu/... Screenset=windows position/layout Now I still believe that if you make Screenset global (saved screenset can be called up within any project) and working correctly (retain position and size), we would have the best of both worlds. No need to decide Lens vs Screenset.

After playing with all perceivable combination of things, I think that not able to retain the multi-dock's size is a bug. There are a couple work-around however. If the bakers ever re-visit this Lens-Screen functions, it would be good to make screen set global, or put it under Lens. Have a simple 'save Screen' function instead of this 'copy to screenset ..."

@Noel If you read this how about a simple change so alt-2, ... alt-n, (changing view) triggers double-click (full screen) of the docked tab instead of currently (seems like) single-click (half screen). Or better yet, single-click opens full screen. This issue only occurs when going from Track view to anything in the dock bar.

In English version there's no 'Dock on'. I think it's called 'Ease of access center', there's an option to turn off auto snap when moving a window to the edges. I did this and it didn't make a different in CbB. To me the various windows options are for managing multiple Windows. The issue here is within that 'workspace' within CbB.

Double click works, it opens full screen. I've been using a lot of keyboard shortcut (as much as I can remember, which is not much these days!). Guess I need to use the mouse click instead of alt-2, alt-3, ...

@Heinz, I can certainly "Rock-on" ? but how do you deactivate "Dock on"?

did those many times, Screenset locks has no affect. After resizing I can flip any view in the dock bar fine, but when go to Track view and the go to other view it's reverted back to half screen. When it decides to work, it will work fine until I save, exit. The next time I open the project will be half screen again. btw the project is now always open in a windowed box (not maximized).

Lens and Screen set always confused me. I do understand the concept but I think that there are a few quirks. For example I simply want to do the below and have never been able to do it consistently: For a single screen, I just want to use the keyboard short-cut [alt-something] to flip between the screen. I want the console, midi, ... to line up where the track view is thus not I can still use the control bar, in my case I set at the top. It's either docked or open but half screen with the track view, or maximized but cover the control bar. So I float the dock and drag sizing the screen to where I want but when I switch screen, it almost always reverted back to dock or half-screen. Then sometimes it sticks. Would Lens or Screen (or both) helps me do the above? Or perhaps a new option of 'fit to window' to allow the above.

yes. The first time I encountered this it wouldn't sync no matter what. But on the next day once I got it to sync once, I can only reproduced it in a couple times out of twenty or so. So I'm just sticking to selecting the track method and call it a day. Exactly. For example if your asio buffer setting is 128 samples, you would add 128 to the ext insert pinged value of 708 samples (=836 samples). This is the actual latency of your setup. And you now notice that the asio reported doesn't matched (lower/under reported) by 4 samples (836-832). Put 4 in the manual offset, for a perfect sync. Now anything around a few samples off would be considered as sync, and you wouldn't be able to notice. However if in this case if you use 256 for buffer, you will be off by 260 sample which will be quite noticeable.

It's in the tab 'Tracks' on the menu line with MIDI and Region FX

After a few days really digging and searched on the old Sonar forum into this 'hardware latency compensation' topic I think I got a pretty good understanding of how it's supposed to work. Let me share: There are two area to compensate for HW latency, 1) is the Asio driver Manual Offset, and 2) external insert. I was confused about the two compensation areas above but now I know that they are not related and should be used for completely different scenario: 1. Record Latency Adjustment (Asio driver): This is needed so any new recorded track will line-up with existing vst or audio tracks. 'Use Asio reported latency' is your hardware reported value. If you don't check this, your recording will be way off. Even if you have this checked, your recording will still be a little off depends on the HW. The issue here is most HW have hidden or unreported value. You must use do a 'loop back ping' to your HW to get the actual latency. You can use a tool like CEntrance, or CbB's Ext Insert ping (more later). Subtract the Asio reported from the actual pinged value. It should be a positive value (under compensated). Put this value in the 'Manual Offset'. This is a static value for any buffer settings so just need to set it once for a HW. 2. External Insert: settings in the Record Latency Adjustment will have no impact. (the CbB's bakers can verify but this is what I observed and t makes sense for overall compensation to follow EXT Insert if you use it). 'Ping' to get the actual HW latency. However the issue is the pinged value returns by Ext Insert is one buffer less than the actual latency. Not sure if it's intended or a bug? The good thing is regardless of the reported value, CbB compensates correctly. For my scenario, I want to bounce to track. There is a consistency issue when 'bounce to track'. If I just select the clips in the track and bounce to track it will be in sync most of the time but not always, (bug?). What seems consistent to me is select the whole track (click on the track number) and do a bounce to track.

Thought I have this figured out before but I still don't understand. I send a track out through external insert to route to hardware devices (compressor, EQ, etc.). Using external insert ping to get the latency, checked use asio reported latency (under preference). Hit bounce to track (real-time). The bounced track is behind the original track (delay) by about 38 samples. Using positive value offset in the external insert has no effect. Using negative value for offset delays the signal further. Manual offset in the Asio has no impact. How to get the bounced signal to line up with the original signal? Any guidance is appreciated.

I'm currently re-do a bunch of my Sonar 8.5 (32-bit) projects with CbB since I now have better plug-ins. CbB will open the old Sonar 8.5 files just fine. All the takes will mapped nicely into the Take Lanes, all automation, envelopes mapped. I haven't ran into any issue. The only caution is the 32-bits plug-ins, a few may not work with bit- bridge. Not an issue for me since the reason for me is to use the newer 64-bit plugs that I now have. Now looking back at that old Sonar 8.5 GUI, I'm glad we have CbB ?

I did a few controlled testing and it's working as it should. Only newly added or rename .dll file got scan, the existing plugs stay intact. Thanks for all the help.

or you can use keyboard shortcut like ctr-shift-A, or '5' to clear. Why have 'project' as an option at all?

I just noticed the Export Module and trying to use it. With "project" checked I would expect the whole project to be exported, in the past I have to do a 'select all'. However if a section on the timeline is selected it will only export that section. Should that be "selection" if you want a section and project should be all regardless? The issue is often time I don't notice that a section is selected. To use this new feature I now have do to a 'un-select all' first. To me there's nothing to be gained here if that's the design. Am I missing something? thx

I have it on manual scan, and upon adding new plugs I hit the "Scan vst plug-ins" button. Yes it does show re-scanning existing plugs Now knowing how it should work, I will run some test and observe it carefully. I have too many plugs so I didn't observe exactly if all was re-scan or a few folders.