Noel Borthwick

Many people used markers as a poor man's arranger. No need for that anymore

Yes this is because we updated our signing certificates. The lame thing is when you do that your have to build trust again so it will take a few hundred people to download and run before the warning goes away. Unfortunately this is out of our control.

Yes please try that. Also turn off the AV.

Those seeing no presets installed can you specify what version of Windows you are running and anything that may be relevant that could prevent registry access by the installer? such as AV software or restricted account permissions...

You are missing the presets. Something may have prevented the installer from installing them - maybe a permissions issue. Reboot your system and rerun the installer (you may have to first run the rollback). You should see a few hundred presets there if it properly installs.

@Carl P Clovis only thing that comes to mind is that somehow the installer failed to update the presets. Open the registry editor app and go to HKEY_CURRENT_USER\Software\Cakewalk Music Software\ActiveMovie\Presets Take a screenshot of what you see there. You should see more than a page of presets listed.

@Jean-Philippe ROGERCan you send a link to a zip of the project file. Its hard to know what you are running into without being able to see and reproduce it.

Put it on a share and send me a link.

Arranger is fully integrated with MIDI. What Mark mentioned has to do with certain generative VST instruments that have their own internal timeline (EzDrummer, etc) If you sequence something within the VST to play based on the original project timeline, of course the VST will playback using that timeline as a reference. So if you make an arrangement that splits up the original project into different sections the plugin will be unaware of this and will continue to play based on the original project timeline. You have two ways to handle this: Don't use the plugin's internal timeline to sequence things Freeze the plugin before rendering an arrangement Note that arrangement preview will always work since it hasn't committed the arrangement yet.

We just posted the 2020.04 early access release. Please post any comments or feedback directly in the linked thread. We're very excited to get this major update of Cakewalk out. We plan on releasing the final build next week which will include a few more tweaks.

I assure you it will be worth the wait

@HIBI this is fixed for next release.

Will look into it thanks for the heads up

Hi Folks, as mentioned in the prior release that model is considered "beta" since I still have to do more testing with it. The latency problem is due to a weird race condition leading to audio buffers being lost. I just havent had time to track it down yet but will get to it. For now don't use that model until further notice.

@Maxim Vasilyev the problem with track names displaying garbage has been fixed. As mentioned above its actually caused by the way the VST3 SDK reported this so technically could have been easily addressed from the plugin side (most other VST3 plugins handle it). However I have made a change to resolve it from our end. As far as VST2 goes there is no way for a host to report track names to the plugin via the standard VST protocol so this won't work with Relay in any host. You must use the VST3 version to get this functionality. Cakewalk has supported VST3 channel naming from the get go for many years now. With regard to track ordering in Neutron, this is a deficiency in the plugin since it it appears to be sorting the track names alphabetically and ignoring the host specified track order. There is a specific VST3 interface that can be used by the plugin to identify the order of tracks. If they use that the tracks will be sorted in the same way that they appear in the host. This is how it works with the Softube Console One. BTW the same track ordering problem can be observed in other VST3 hosts such as Reaper.

I've fixed this issue as well for the next release. It had to do with some peculiarities with how Relay requests the host to do resizing via VST3.

Oh well I managed to sort out the string garbage by fixing some code in the VST3 SDK . The SDK code was not copying over the null terminator for the string ? I'll submit my change to Steinberg as well since any app that uses that would be susceptible to the same problem.

@Matthew Sorrels I finally had a chance to look at this. The problem is not in the Cakewalk code. The channel names are provided by a standard VST3 interface called IAttributeList and provided via ChannelContext::IInfoListener. In this the string is properly null terminated but VST requires the user of the string to use the string size provided and properly null terminate their target. This is not being done by the Izotope plugin hence the garbage appears. I will pass on this information to Izotope.

I cant quite follow what the problem the user is having other than the fact that something doesn't work right with REAC. Since we no longer have a REAC system to test and it is no longer supported by Roland its going to be hard to troubleshoot. One suggestion is to turn on "StopEngineOnASIOPanelOpen" since some Roland devices don't like the audio engine running when the ASIO panel is opened.

A fix for this is now available in the hotfix we just released.

After several hours of troubleshooting and a tip from @Steve Katsikas I managed to reproduce the issue again. Its a bizarre preexisting problem that happens when you seek on the timeline to a late measure. In my testing the app would appear hang for about 5-10 seconds and then vanish silently. I was able to find the root cause and fix it last night. The engine was incorrectly responding to a seek on the timeline and computing a bogus delay compensation value. In Steve's case this could compute a delay of up to 3 hours ? This value would then be used to send a HUGE MIDI buffer the next time playback started causing an overflow and crash. While most users wouldn't necessarily see a crash (since its dependent on the amount of MIDI data) this issue results in way more MIDI data being processed when playback starts at a high measure number. I've sent Steve a build to verify the fix and if all is well we'll be releasing a hotfix with this and a few other issues soon. I'm happy that this issue is fixed since it could have been the cause of many unknown random crashes in the field over the years - the problem has been latent at least since 2006 Fortunately his project was reliably able to reproduce this and allow us to fix it. Thanks for working with us to repro the issue.

@Steve Katsikas its the strangest thing. I tried for 30 mins today to reproduce this issue and it is no longer happening. I went back to 2020.01 and even SONAR and the project plays fine at 48K and I even the your markers while playing extensively. Both myself and a colleague were able to reproduce it earlier but the issue seems to have gone away. Can you please retest this after updating windows since its not impossible that there was some external update that fixed itself. If you can still reproduce it please see if you can get a sequence of steps that makes it more likely to happen. @Bob4u I think your issue may be something else based on the crash. Please ensure that your VC redists are up to date by downloading and updating the latest 64 bit VC redist from microsoft.

I posted an update for this issue here.

Hi @Robert Bone @FJ Lamela and others who had this issue. Please try out this version of VST scanner. I've updated the logic so that it is more specific about the VST3 folder rather than just checking for VST3, It will now only look at the standard VST3 folders under Program files or Program Files (x86). Also it wont get tripped up by names like VST32. You will need to copy that file into C:\Program Files\Cakewalk\Shared Utilities and then scan again. Let me know if it fixes the issue.

@FJ Lamela Some questions: Are the 7 plugins removed when you scan from cakewalk the same plugins from c:/vst32/? Do any of those plug-ins reside within a folder that has the name VST3? Are the removed plugins VST2 plugins?