• SONAR
  • [ANSWERED] Sonar X3 Producer VST3 Bug (p.2)
2013/10/09 07:03:41
Disrezoloution
Mystic38
hmm..
 
ok..it looks like when I said "it works fine".. I actually meant " I can see that there is a VST3 and I can insert the VST and the editor window opens"..
 
With preferences set to have all 5 of the s70xs ports active for both input and output, I get a recurring error that says " the host ports are not properly set"
 
so, while I can open the editor window, I cannot communicate either setups, changes or play midi data to the device",
 
I will take another look later today wheni have more time but perhaps I suggest you change the title to reflect "X3 VST3 bug" or similar to get some attention?
 
 regards,
 


Changed the title.
2013/10/09 07:59:04
Noel Borthwick [Cakewalk]
Hmm, it would be interesting to know what that error message means and what the plugin is expecting from the host. I'll contact Steinberg and ask for more info on this. Its possible that it requires some extended support from the host beyond VST3 or is using some VST3 feature that we don't support yet. I'll see what I can find.
2013/10/09 08:17:22
Noel Borthwick [Cakewalk]
I replied in the other thread - we'll follow up and see what we can find.
2013/10/09 08:25:41
Mystic38
Thank you very much Noel!
2013/10/09 11:17:24
Noel Borthwick [Cakewalk]
I got a pretty quick answer from Steinberg on this. 
"The reason this fails is because this is because the Editor makes use of some private interfaces to look up MIDI and audio ports"
 
So this is not a SONAR VST3 issue per-se. If Yamaha exposes the private interfaces in the future we can consider implementing them - as long as its not a huge undertaking :)
 
2013/10/10 08:49:20
Mystic38
It may be that they are referring to the 5 USB ports (ports, not channels) that are associated with the s70xs/motif?..
 
port #1 is keyboard
port #2 is remote control surface (allows s70xs to control Sonar transport)
port #3 is midi thru from s70xs
port #4 is reserved for VST3 editor
port #5 is remote editor (allows s70xs/ to control vsti)
 
So, There are two USB midi ports required to be connected ports for the VST editor to operate. s70xs port #1 and s70xs port #4.
 
In the VST editor setup screen: 
 
a) Port #4 seems to be connected correctly : for both Port 4 MIDI IN and Port 4 MIDI OUT it is possible to see via a drop down list ALL the USB midi ports connected to Sonar... so s70xs-4 is selected for each. (this selection was done by me on first launch)
b) Port #1 MIDI In is blank (this is correct I believe) and Port #1 MIDI Out is "not assigned" . This, I believe is an issue as there is no list of available ports to select from...
 
I have launched a thread in Motifator and Phil Clendeninn "BadMister" is very keen to assist in getting this working.
 
link http://www.motifator.com/index.php/forum/viewthread/469746/
thx
2013/10/10 09:55:42
Noel Borthwick [Cakewalk]
If I understood correctly they have a custom interface to request ports from the DAW. It wouldn't make sense to use the ports directly from the plugin since they could be in use.
We do the same kind of thing in our external insert so its a well defined issue.
2013/10/10 11:35:06
Mystic38
Noel Borthwick [Cakewalk]
If I understood correctly they have a custom interface to request ports from the DAW. It wouldn't make sense to use the ports directly from the plugin since they could be in use.
We do the same kind of thing in our external insert so its a well defined issue.


What you heard from Steinberg was a confusing statement to Phil Clendeninn - "BadMister" ,who is the predominant Yamaha Motif expert at @ motifator..
I would wonder that if this was a "custom" protocol, then it would not be likely that in the setup of the Editor, port 4 has available in the dropdown menu all of Sonar's USB midi ports?..so the Editor clearly can see the USB ports.
 
Port 1 is for Keyboard data. The input is hardwired to the VST editor input so is left blank, the output should be selectable from the same list of USB midi ports available to that shown in port 4....
 
just a thought.... is there any likelihood that there is an issue because this is an external VST (ie going over USB to hardware) rather than a VSTi where output routing is internal ?..
 
thanks again, Ian
2013/10/10 20:49:59
Noel Borthwick [Cakewalk]
Well the steinberg message clearly indicated that they had a custom API so I assume this is fact.
A vst plugin can't open ports directly without conflicting with the host using the same ports so there would have to be some kind of handshake. An instrument editor is completely different from a normal VSTi.
2013/10/11 09:01:00
Mystic38
I have asked Phil Clendeninn to request clarification from Steinberg regarding the ports issue, and as he has been a good customer advocate for some years hopefully he can encourage some dialog on the topic to help get this going. I will add that some quick web research shows that the statement may well indeed be correct, with FL Studio and Studio One users also posting similar issues.
 
Here is the nutshell of the roadblock issue, two images of the VST editor setup window.. one (for Port 4) correctly showing all usb midi ports and one (for port 1) showing no access to Sonar's USB midi ports
 

 
and here for port 1
 

 
I have already offered to buy a copy of X3 for Phil if that will help get this moving and if it gets to that point, I would also cheerfully drive to your site in Boston with my S70xs to help with testing if necessary.. 
 
thanks again, Ian
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account