Jump to content

[CLOSED] 2019.11 Hotfix Release Candidate (HFRC)


Noel Borthwick

Recommended Posts

1 hour ago, Matthew Sorrels said:

The UI paint problems with the VST3 version in Bandlab may still very well be iZotope's bug, can't really tell.  The track name garbage though is almost certainly Bandlab's bug, looks like they aren't null terminating the track name when they hand it to the plugin maybe.

The VST2 version of Relay in Cubase 10.5 doesn't even have the advanced drop down arrow.  Which I think is funny (since Cubase is the defacto VST platform).  But the VST3 one correctly resizes and repaints the UI, which Cakewalk doesn't seem to do right.  In Reaper and Ableton 10 both the VST2 and VST3 plugins work correctly and have all the options visible.

I'd say the odds of getting this fixed aren't that good.  Maybe someone from Bandlab will see this and can put it on the list.  I think they can get a demo version of the iZotope plugins that would be enough to test/debug this.

Thanks for the insights Matthew. For me that's all useful information. Hopefully it will get sorted out. I really like the iZotope Production Suite for mixing.

Bill

Link to comment
Share on other sites

Hello
When will the problem with track names in plugins be fixed when using iZotope Relay plugins?
In the photo Two options for using these plugins: VST2 and VST3.
In both cases, there are incorrect track names and their ordering.
The iZotope website says:
"The track naming feature in Neutron and Relay is specific to DAWs that support this functionality. DAW manufacturers have to intentionally make this functionality available for us to be able to use it."
I use Sonar Platinum version 2020.01.
Please correct this misunderstanding.

Relay Name VST2.jpg

Relay Name VST3.jpg

  • Thanks 1
Link to comment
Share on other sites

On 12/15/2019 at 11:06 PM, Noel Borthwick said:

@Matthew Sorrels we'll look into the string issue. Thanks for the report.

@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.

  • Like 3
  • Thanks 2
Link to comment
Share on other sites

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.

  • Like 4
  • Thanks 1
Link to comment
Share on other sites

10 hours ago, Bill Phillips said:

Another problem that @Maxim Vasilyev didn't mention is that the features in the Advanced tab are available in the VST2 version of relay but not available in the VST3 version.

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. 

  • Like 2
  • Thanks 2
Link to comment
Share on other sites

12 hours ago, Maxim Vasilyev said:

Hello
When will the problem with track names in plugins be fixed when using iZotope Relay plugins?
In the photo Two options for using these plugins: VST2 and VST3.
In both cases, there are incorrect track names and their ordering.
The iZotope website says:
"The track naming feature in Neutron and Relay is specific to DAWs that support this functionality. DAW manufacturers have to intentionally make this functionality available for us to be able to use it."
I use Sonar Platinum version 2020.01.
Please correct this misunderstanding.

@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. 

  • Like 4
  • Thanks 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...