Noel Borthwick

Best to contact celemony to help troubleshoot it

Thanks to David at Lynx for the fast turn around on this!

It's best to post a video of what you are doing since there may be some confusion with how you are describing the issue. Which channels are getting muted? when you record on a track it's normal for previous audio on the same track to get muted. Other tracks should be unaffected by recording.

It's could be possibly related to the asio driver not responding after the system wakes up. Is the UI also frozen or does it only appear frozen when playback is started?

I have the Zoom U-44 here and it works fine with record and input monitor. If you see meters then it is receiving a signal inside Cakewalk. Try recording a track and see if it records audio. Then play back the recorded audio track and ensure that its assigned to Driver Out 1.

Thanks @rv729 based on the symptoms it really looks like a driver conflict with MMCSS. Lets see what response we get from Lynx.

@VyacheslavPlease zip the file and send a link to the dump so we can look at it.

Upsampling runs the plugin at 2x the current sample rate in Cakewalk. The result really depends on how the plugin is coded but there are cases where upsampling changes the sound because it gets rid of aliasing artifacts introduced by the plugin DSP at lower sample rates. It works both ways - sometimes the "artifacts" may sound better to you since the sound designer may have tailored the presets at 44.1K. So use your ears and enable upsampling where it improves the sound to you. This feature came about when @Craig Anderton was playing around with amp sims and found that they sounded very different at different sample rates. So we built this feature to allow users to easily run plugins at higher sample rates without unnecessarily running the entire project at high rates.

Anything is possible But today there is no way to select which effects are bypassed when you use the global bypass button.

I meant it could be some external software component affecting system timing. Especially since you say that rolling back to the last release did not solve your issue. Try keeping task manager open first and then reproduce the hang. You should be able to then right click the cakewalk task and choose "save dump file".

You can use mix scenes to swap in different sets of effects on tracks. That's one way to do this.

If you prefer the basic workspace you can make a custom workspace with just the features you use including the video view.

Even if you use melodyne as a track effect it utilizes data from the track. I restoring a scene simply restores the melodyne effect state. If the track data has changed since then it will be out of sync.

@Vyacheslav @glen dale If you can reproduce a hang please send the dump based on the instructions above. Maybe some timing changed on your systems that is exposing a previously unknown issue. Do you have plug-in load balancing enabled by any chance in preferences | Audio | Playback and recording?

No as explained, Melodyne is not a track based plugin, rather it is region (clip) based. Mix recall presets do not save the state of clip based plugins only track/bus effects. If you got a crash while changing scenes please send me a link to the dump file so we can investigate the cause.

Its not a bug - that's how floating windows work. It would be far worse if minimized floating windows continued to be visible since they would obscure areas of the app. This behavior has existed in every version of Cakewalk. You can either double click on a synth icon to make it visible again or use CTRL-TAB to tab back to a floating synth window and make it visible again. If you don't want to use floating windows you can also turn it off in the system menu by selecting disable floating. It would be nice if floating windows also appeared in the Windows menu in Cakewalk. We may add that sometime.

Mix scenes are saved externally in the per project mix scenes folder. However if you add new scenes you should resave the project since the list of scenes is stored in the project file. Please note that mix scenes will not save melodyne region effects. Only track and bus effects and synth settings can be stored in mix scenes, no clip based effects...

Phew thanks for clarifying Re TTS1, its really sheer coincidence that you are seeing it work "better". Known crash bugs are like playing russian roulette - sometimes you get lucky and sometimes the trigger will get you! There is nothing special in CbB other than it has more code than older versions and as a result a greater likelihood of tts1 corrupting something more important. I can assure you that we had several reports of it crashing old versions of SONAR as well. If you have a simple project that can reliably crash CbB with TTS1 there is a remote chance that I could work around whatever damage its doing so let me know. TTS1 code was written by Roland developers and Roland themselves abandoned it many years ago. (The original devs from Roland who did it are long gone) We have a very old version of the code - however even if we had the current code it would be impossible to fix since it was machine generated from their synths and is next to impossible for a human to understand let alone fix! We're considering an alternative a replacement for TTS1 for the future, but if you really want to get something now, Roland has a SoundCanvas VST plugin that you can buy. I've have not tried it myself.

And Merry Christmas to all our hard working users too Its not Christmas just yet here so still chasing down some gremlins here!

@JohnT6794 and Чело Век which release of CbB are you running? This message was posted back in May and many things have changed since then. Please run this release that we plan to publicly release soon and report back. Also when did you first notice this specific issue? Have you directly compared the settings you have in SONAR to CbB? If so please contact me and we can troubleshoot it further with you. If you can reproduce a difference there is likely a simple explanation. Most drivers will have a hard time using a 32 sample buffer and do it by using internal buffering. In all my tests I see better performance at low latency in Cbb than SONAR. However perhaps the issue you are having isn't performance related. @Terry Kelley I'm not aware of several things that work in SONAR but not in CbB. More the converse situation - we've fixed hundreds of issues that preexisted in SONAR. Can you be more specific?

Grouping applies to widget fader movements not automation envelopes. i.e automation is independent of any widget grouping set up.

Clip envelopes are completely non destructive and can be used to change clip gain or other per clip plugin properties with clip based plugins. The usage of VCA's as demonstrated, can be done using control groups, and using absolute, relative or custom grouping of parameters. VCA's can be convenient but grouping will do a large segment of what they do for most people.

When in the effects bin you aren't using it as an ara plugin since it's not a region based effect anymore.

Hi @treesha yes you must apply it to all clips since in it is a region effect and not a track based effect. Here is a video from Celemony's site that shows the process. Though its made using Studio One its a similar process in Cakewalk. Select the clip and press CTRL-M to turn it into a region effect clip for editing in Melodyne. As the video states if you intend to use Melodyne for comping its best to start using it early in the comp process so convert the entire take lane clip into a melodyne clips and then start using the comp tool or smart tool to isolate sections. It will automatically create sub regions for editing in Melodyne.

@Rajeev Vijan as discussed contact us when you are available and support can try and walk you through some steps. The fact that you aren't getting any error messages and the problem occurs even in the last 09 release seems to indicate that there may be something else going on. The first steps you should take is to eliminate a routing issue. Try recording in a blank project and see if you get meter activity. Then playback and look for meter activity on hardware mains in the console view. Also check the lynx console.