micv

My bad, I must have seen stuff! I tested it again and the soundcard always locked to the project rate which is 48k even when I do audible bounce.

When I export to 96k, my soundcard got changed to 96K. How is it possible that the project is running at 48k and the card at 96K?

I realize that if you are doing ITB, it probably doesn't buy you anything. However I routed my buses to external analog hardware and export the audio, thinking that it's like 'tracking' the final mix bus so let use the higher rate there.

Once you go SSD you won't go back! Net result is about 3.5 times faster overall. I use Samsung EVO

Any reason why you would or would not export mixdown to 96khz when all tracking and project is at 48Khz? I've always used 48K but now that computers are more powerful and sound-card can easily do 96khz. Can anyone actually hear a different?

Searching the old thread, it's a known old issue/feature, when you have External Insert you simply can't solo a bus.

When I solo a bus, there is no audio coming through, which technically makes sense but not useful in real use. Is there a setting that when you solo a bus, all the tracks that are routed to that bus is also solo'ed so you can hear what coming out of the bus?

After further testing, this condition happens when the audio driver/card is off or dropped from CbB. When the CbB is connected to the sound card then it's working fine. Would be good if CbB shows a notification like "FX Region disabled, no audio card" or something instead of going thru the erroneous rendering.

When create an FX Region, Vocal Sync or Melodyne, for a clip, the FX Region clip got extended (much longer in duration) and the audio got pushed to the right. Or in other words, silent audio padded to the beginning of the clip for some large random number of bar and the original audio is at the end of the clip. Anyone seeing this?

This is specific to 2019.12: As I mentioned earlier I have issue with Midi dropping out starting with 2019.11. The midi buffer default value in my config, for as long I as have used Cake, is 200msec. In 2019.12, since there was a changed in midi buffer recently I played with the setting and increased by 50msec (250, 300, 350, 400) for each test case. when the buffer set at 400msec, there's no drop out. fwiw apparently the new midi 'auto buffer' requires the buffer to be set much higher (twice?) and not automatic as stated. My question is then is there any negative impact if the buffer is set too high?

Since the beginning Sonar has a library of CAL scripts. Basically you can script or program for midi. For example I use the undup all the time to find if there's any duplicate midi note which is not visible since one note would be under the other, but the velocity or volume would jump.

Thanks for the info, didn't know that. As long as Bandlab supports CbB on Win7, I'm ok, so please support it for another couple years. MS regular updates are the culprits to many of my woes, and my workstation is only on the internet for CbB updates, so I don;t need all that securities updates mess. Typically I would buy a new system as upgrading an existing system has always been problematic and frustrating. Just the thought of having to upgrading all plug-ins, soundcard drivers, and spending weeks working through issues, yikes.

I have to say that up to 2019.9 CbB has been reliable despite its well know quirts and workaround. Since installed 2019.9 I continue to have work stoppage issues. The only change is that when force to update Bandlab Assistant, I think that it also installed an update Microsoft Visual C++ 2017. I'm on Window 7 pro. Last resort I will do a system restore. Couple of the new (recent) issues are: 1. Clip gain envelope does not consistently work. You can raise and lower, but it doesn't follow the nodes. Moving the clip to another lane would allow it to work once. toggle another clip (at the same timeline) would allow it to work sometimes. CbB has long standing issue with envelop not working if moving the clip to another lane. Now with the changes in lane, maybe the old issue is the underlying culprit. 2. Midi track drop-out in playback when there is an External Insert in the mix bus. I never have issue with Midi ever going back to Sonar8.5. Perhaps this is related to the new audio/asio driver change and somehow midi not tracking under some condition. Then there is situation where a clip can not be split no matter what but the undo history recorded that splits were done; If you bounce multiple clips into one, sometimes not all of the selected clips got bounced. Probably some conflicting rules in the codes. 2019.12 probably helps stabilize in some areas but the issue I been having still persist.

@Noel. If you have an External Insert, on a bus in my case, and Midi track, the midi playback would drop out intermittently. Reproduce by stop-start the project a few times and it will eventually occurred. Will occur in audio export also. This issue occurs in the previous release also (2019.11)

good question, don't know, I'm still trying to find a clue. Issue is observed on the project I created with the Sept 2019 release. Interestingly, I opened that same project in Sonar Platinum and everything works fine there.

A week has passed, I tried a bunch of things but the problem still persists. These are the strange behavior I noted: If there is no nodes on the envelope, and you raise or lower the gain envelope line it will work fine. When you have nodes, it will play correctly (the level) the very first time you play but if you stop and play the clip again, the level will not follow the nodes. If you move the clip to another lane, it will play fine the first time in that lane and again won't play correctly on subsequent play. I can re-produce the issue consistently. The level is render correctly if you bounce the clip however. Painfully this is my workaround at this time, bounce, play, undo, set gain, bounce, play, ..... until it's right. When bounce clip, now sometimes the clip name is blank. No one seeing this issue?

wonder if there's any cakewalk GUI changes recently.

I was editing in Takes Lane mode (all lanes opened). I hardly cut and paste in track mode as it will also select all the clips in that selected timeframe section. and yes, with no option that I can find, I have to make sure to paste into and empty lane (create one , select it, and paste into it). I don't recall it behavinh this way until the last couple updated.

an example: I cut and paste a clip in section 1 , into a section 2 to compare. But I have other clip in the take lane in section 2 already, variations of the same theme, that I muted. Cakewalk will paste the copy clip on top of (or override) the existing muted clip in that lane, even in "Blend' mode. The expected or desire behavior is if there is an existing clip, muted or not, don't override it in 'Blend' mode, put it on an open lane, or have the option to.

thanks, but exactly checking for what? the ... Blend, Replace, Slide Over?

Thanks for the help so far. I've been using the clip envelope for years without major issue. Not sure what's going on here. At this point I'm thinking it's the app. Just learned that W (with T) is for "touch" mode, that's the default so that's not the issue either. I uninstalled and installed the latest version. It working intermittently and behaves erratically. Disable the Global Read [R!] the clip with the envelope level jump to something like twice the level. If the clip has a section with the gain at max then the whole clip is played at max level (+6db). Think it's might be the graphics, I deleted all the pictures cache, still not working. Deleted the audio.ini too. In the past when the clip gain is not behaving, I can always comp and use the track's gain. This time neither is working.

I don't remember this behavior previously, but now when I past a clip, it's placed over a muted clip. Is there a setting so it would paste into an empty lane instead?

don't think so, it would have a + sign on the volume fader

I think so, the R is blue for all tracks.