Noel Borthwick

The driver has disconnected from the system or you have a faulty USB connection causing it. This is not caused by the DAW.

If you can reproduce the crash please send the dump file. Regarding the fx chain, try dragging it to the track fx bin and then splitting it into it's components. It may reveal which plugin is going silent.

Does it happen if you try and load the same project again? If so please send me a link to the project file that causes it. That warning was put in to help diagnose cases where plugin settings might not be restored properly.

@Helene Kolpakova thanks for posting your use cases. This change was made to align the behavior with the way most modern DAW's work as well as to cater better to the "always playing" workflow. As you have already noticed most other DAW's do not stop in response to transport actions (other than stop itself). Prior to this change, there was no way to jump to the loop start dynamically without stopping playback, which IMO is a major omission. This can be important while mixing where you want to repeatedly audition a segment without stopping playback. Or even when playing or practicing a part before recording. Also the behavior was very inconsistent since some operations like "W" would stop playback but yet others like go to previous measure would not stop. Its inconsistencies like this that make the application not intuitive to new users, so sometimes we need to make hard decisions to change behaviors even though it may impact some users. In the future we plan on adding more accessible transport control operations as well so unifying the behavior was a first step in this direction. However I acknowledge the opposing workflow requirement to "seek with stop" in order to make an edit and then proceed post edit. So to accommodate this but in a more consistent way, we're considering adding a new preference. "Transport Seeking Stops Playback". When this is enabled any seek operation to change the transport position while playing (or hotkeys like W) will first stop playback before seeking to that position. I believe this should address your two cases "Case1: Often, I need to Stop at a particular moment that I want to edit." and "Case2: Equally often, I need to Stop to get back to the beginning, because the part I need to edit is around where I started" We will default to the new behavior but you will be able to turn on the stop behavior through the TV options menu. Sound OK?

Hi guys, I've fixed this now. It will be in a hotfix soon. There were some massive changes to time management this release and I missed the count in case when reporting time to plugins. It's not exactly related to starting playback. It's just the time reporting itself that was not accounting for the count in.

Thanks for the report. Indeed the time reporting with a metronome count in is not properly accounted for. I'll investigate it.

If you are going to be in New York Oct 15-18 please come see us @ AES! If you don't have a pass you can get a free pass from us here. Jesse Jost, Mike Balzarini, and myself along with Amon Wong from BandLab are at the show and we're showing CbB as well as BandLab. Here are some pix of the booth.

The only reason it happens is because you press W multiple times quickly Now that it doesn't stop playback it exposes the issue. You can repro in any version of Cakewalk by just seeking on the timeline faster than a second with your project.

@eli0s thanks for sending your files. I loaded up your project with the video and set up a loop and repeatedly pressed the W key to rewind but everything works as expected. There were no hangs at all. Do you have any synths in your original project or something else that could be causing a stall? If you could send the hang dump via wetransfer or google drive etc it might show where specifically its hanging. I suspect its some video codec on your system leading to the issue. Does it hang if you seek time by clicking on the transport? All the W key is doing is setting the transport position so the hang should occur there as well if there is an issue. Edit: I was able to reproduce it finally. I had to have the video running fullscreen before it happened for some reason. It appears to be a deadlock with the MF video engine. I'll investigate further and let you know but I don't believe this issue is actually new to 09, just exposed because of the seeking while playing. EDIT2: Confirmed. I can repro the same hang by rapidly pressing CTRL PgUp or PgDn to seek through the video while its playing. In fact that hang even happens in SONAR. Will investigate a potential fix EDIT3: I've fixed it for our hotfix This was an ancient issue that could cause a hang with some video's if seeking on the timeline quickly.

The aux track related drop out was fixed for the main release. That would have a error code 12 and not 1. If you are seeing a project specific dropout with aux tracks that is reproducible try and pare it down and send me the project file to look at.

Thanks for the follow-up @guitfnky. I've already implemented a workaround for a hotfix, but it would be best if they fix the issue in the plugin since Im just ignoring the error.

@eli0s if you can upload a version of the project and the video file we can take a look.

W during playback will first rewind to the last landmark from the current position. If "On Stop Rewind to Now Marker" is active then the last landmark is where playback started from so it will first rewind to that. If you do the same while transport is stopped the last landmark is potentially the loop start time (if looping is enabled) and then the project beginning. If you press W rapidly before the time starts advancing from the landmark it will jump to the previous landmark from there. However unless you are using video which takes longer to seek its likely you will never see that behavior when playing since seeking audio is very fast and time will start advancing. If you want to rewind to the beginning of the project during playback press the Go to Start button on the transport or press CTRL_HOME. Anyway I cannot reproduce any stability with the W key and video.

That's because that is the global audio folder. If you save projects with per project audio which has been the preferred mode for over 10 years this you wouldn't run into this. It then searches only the project audio folder.

@eli0s this is described in the notes below. The only change to the W behavior is NOT to stop playback since its not standard to stop playback when seeking. The same also applies to the transport RTZ operations. Its desirable to jump to the start of the loop or beginning of the project and continue playing in many cases.If you need to stop playback why not press the spacebar? Seeking on the transport doesn't stop playback so why should rewind operations do that. We tried W with a video file and did not see any hangs. Is it possible to upload the specific video you are using? Does it happen with any video file? Updated transport behaviors Go to Start and Go to End buttons now accurately seek to project beginning and end, and do not stop playback. The W (rewind) key always seeks backwards in time to the prior "landmarks". There are 3 landmarks: the original playback start time the loop start time the project start time (time 0, or 1:1:0)

There is probably a simpler reason for Code 0. I think its just that the dropout reason was not assigned someplace it should have been. I'll see if I can find it. Code 13 is your ASIO driver telling the host that something changed that requires a reload so we force a dropout. Perhaps the sample rate changed or another app did something to the driver that caused it. As long as it doesnt happen all the time its normal.

In general its no longer necessary to use Cakewalk Audio Finder and in fact its not optimized like Clean audio which now cleans in seconds. For per project audio there is no reason to use anything else to clean.

I meant in the code we catch the exception and ignore it. Its not a recommended procedure but its a failsafe. You can't prevent the crash yourself till you get the fix from us... Please report it to them - I will also file a bug report directly.

I was able to reproduce this. Its caused by a bug in the plugin which causes a crash when the process call is done while the plugin is not active. This is the proper VST3 specified way to synchronize state when a plugin is not running. The reason it didn't happen in earlier versions is because there is a new fix for the bug below. We're not going to bring back that more serious issue so I have worked around this crash by ignoring the crash and it appears to load OK. The plugin vendor really should address this properly in their code. --- Waves/Fab Filter are reverted to the plugin reset value ============================= recipe: 1. Set Cbb option "always stream audio through FX" to off 2. Insert FabFilter Q3 or Pro-G in an empty track 3. Open UI and change settings 4. Save project 5, Reopen 6. Tweak settings in plugin 7. Save 8. Reopen Expected: Plugin changes are saved. Actual: Intermittent cases from some users where the plugin values revert to default settings.

No Cake for you

I'm curious how often you get code 0 and what you did before that. As far as I see that shouldn't be happening normally but I may have missed a case setting the dropout reason.

Hello @eli0s I'm unable to reproduce this. Are you clicking the Go to Start button at the bottom of the transport? Could you please send a link to a dump file? Instructions here. By the way there is no need to double click that button. It will always jump to project start.

Thank you all for your feedback and participating in our early access preview! The final 09 release is now available. As mentioned in the Early Access Program Guidelines, we release only after we have finished our internal beta testing, so you are getting a close to final build. It's impossible for us to test every combination of plugins and environments, so we rely on our community to do these final "smoke tests" and provide feedback. Your feedback has been a huge help to us so so please continue participating. It helps everybody and leads to a stable release.

@guitfnky please take a look at this article.

I think it's unlikely to be new but I'll take a look. Please send a link to the crash dump file. Did you not try the early access build?