Noel Borthwick

The drop out occurs since its a runaway buffer allocation loop. The engine allocates buffers typically from a preallocated pool but when there are special requirements it will allocate memory when needed (within limits). In this case it never stopped allocating so the engine forces a dropout and releases all memory buffers as a failsafe recovery. The spike you see is likely the deallocation. This is mainly a failsafe situation and doesn't happen normally. Somehow in this circuit its not properly recycling buffers which may be the root issue here. These issues can be tricky to fix so it might take awhile to diagnose.

Yes as I expected its a buffer overflow condition. So it will keep allocating buffers until it hits a limit and forces a stop by triggering the protection fuse. We'll look into it and try and fix it.

@JL thanks for the report. We'll investigate.

Don't bother, I managed to work around this bug in older Arturia plugins. They go silent if we forward parameters to them when loading despite the plugin requesting the forwarding! I had to hack our code just for Arturia to avoid this.

If you had tons of 32 bit plugins this is expected. There are optimizations to cache the inventory preventing too many registry accesses.

@marled I cannot repro your clip selection issue. Can you post a short video or upload a small project that exhibits this? Is this with the smart tool or another tool?

The aux track defaulting to a hardware out is completely normal. It can't assign to the default bus since it would create a feedback loop. I tried recording the aux track for 10 minutes with both input echo off and on and could not get any dropout. Do you have plugins with delay in your project? It will be easier if you list steps from the start to reproduce this or supply supply a simple project where this happens. The logic is very dependent on the routing of a project so its important to know exactly how its set up. Based on the symptoms my theory is some internal buffer is overflowing leading to the dropout as a result of the overflow fuse firing.

@gmpcan you send me a simple project that has the issue? We'll look into it. Delete all the unnecessary tracks and synths and just keep the tracks required to repro the problem.

@Jeremy Jensen I was mistaken. I had an experimental build with some other stuff that isn't compatible with Arturia synths. I am not seeing any issues with Piano -V in the early access build. Which version of the synth are you running exactly. I have Piano V2 from VCollection 7 Version 2.4.1 and this is working fine here. I saved a project from an earlier release and opened it up in 09 and it plays fine. If you are still seeing this please reply to this post or contact me with a link to a project file that has this issue and I can troubleshoot further with you.

There is no substitute for plugin vendors fixing their own code so you should contact them about these issues and send them a project to reproduce it. Whether its fast bounce or realtime bounce there is no issue of CPU load since a dropout cannot occur during bounce. All fast bounce does is run the export as fast as the syths can render bypassing the audio driver clock. Realtime bounce does the export by running the transport. Thats the only difference.

@Jeremy JensenThanks for your report. I was able to reproduce this. This is caused by bugs in Arturia program management that I have reported to them. I have worked around these issues for the other arturia plugins but apparently the workaround doesn't work for this specific synth. I'll look into it.

Are you sure that this is actually a new issue to this months release? As Mark said some synths don't render data properly during fast bounce. Have you tried unchecking fast bounce to see if the render is accurate yet?

Thanks for sending the project file. Are you referring to the small spikes at the point where you do the crossfades? The stretches are performed per clip when bouncing but the crossfades are rendered post stretch (after the stretch is applied) so it might be that the sample accuracy of the crossfade positions is not accurate. Jut a guess though. I havent investigated it. In your project I found that the clicks go away in the bounce if you have wider crossfades. Will investigate further, but this wont be in the 09 release since we are almost done here.

Hi huviolan, this wouldn't be related at all to this months release. There have been zero changes to video for a very long time. Media foundation doesn't support hardware full screen mode as far as I know. It has never worked.

Thanks for checking.

Yes this was fixed.

That actually happened to me. I left an older amp on some years ago in my basement. At 3am I was awakened by loud hum and had to go shut it off. No idea how it went into oscillation by itself randomly but it was pretty scary waking up to that Regarding the OP, Cakewalk itself it doesn't consume much when idle unless you have synths in the project. Then its always streaming audio and consuming some CPU. If you turn off the audio engine then its pretty idle. Its generally better to save and reopen once in awhile however to avoid memory leaks or other bugs from plugins building up.

Are you sure about this? Perhaps you changed your latency settings to make it lower - if so bounces would be slower. If anything startup is slightly faster in this release if you have lots of 32 bit plugins. How many plugins do you have installed?

Yes the final release will automatically update the early access build if you downloaded it so no worries there.

I understand that its difficult when you have sessions. However the main reason for early access is to find outliers like this problem which affect only a very small subset of people and testers don't find. If you didn't report its unlikely that it would be fixed before release anyway.

The System Realtime messages are used by CbB specifically for MTC sync. Incoming messages are used in order to respond to MIDI time code. We also send these messages when generating MTC. However Cakewalk never forwards (thru's) incoming system realtime messages. There has never been a need to do so because these are typically intended for use in an MTC scenario.

Hello @TedPiano would you be able to share a link to your project file? That would be the easiest way to troubleshoot it. Also give us some data on what audio interface you are using and the latency settings.

Localized versions are not provided for early access build, sorry. We're still working on it.

What problems? I've yet to see any reported issues with this release. Of course if you prefer to wait for the final release that's fine.

@TenfootDoes the new playlist option to not load the next project in the background solve your glitching problem?