Jump to content

Noel Borthwick

Staff
  • Content Count

    1,166
  • Joined

  • Last visited

  • Days Won

    24

Noel Borthwick last won the day on November 23 2019

Noel Borthwick had the most liked content!

Community Reputation

1,183 Excellent

About Noel Borthwick

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I assure you it will be worth the wait
  2. 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.
  3. @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.
  4. 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.
  5. 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.
  6. @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.
  7. 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.
  8. A fix for this is now available in the hotfix we just released.
  9. 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.
  10. @65 amps please post CbB questions to a different thread. If you have missing plugins from a very old project you may have to insert the plugins from scratch if you don't have the same plugins that existed at that time. Vendors often change the plugin ID's with newer versions so they will show up as missing.
  11. @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.
  12. I posted an update for this issue here.
  13. 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.
×
×
  • Create New...