The UniWire VST BETA with 1.5 BETA works well in Live 4.1, allowing me to instantiate multiple instances of the VSTs, passing data back and forth from PC to Receptor through multiple channels.
However, I am only able to load one instance of the UniWire VST in Plogue Bidule. Upon loading the second instance, the communications pathway between PC and Receptor stops. If I unload both VST instances from Bidule, then re-load just one, the pathway opens again.
My PC is a Toshiba P30 laptop, WinXPHome SP2, 3.2GHz, 512MB. Plogue Bidule 0.9001 ( built : Dec 7 2005 )
You'll probably need me to gather more info on this, which I'm certainly willing to do, since Plogue Bidule is a very flexible host and I'd like to get UniWire working with it. I've also contacted Plogue about this.
UniWire VST BETA, 1.5 BETA with Plogue Bidule, problems
-
- KVRist
- 197 posts since 23 Jan, 2006 from Ontario, Canada
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
It looks like a synchronization problem between the instances. Most plug-ins have each instance work totally independently from each other, but since with UniWire all instances share one Ethernet cable and share one or more Receptors, they have to be synchronized with each other.
We will need to look at how Plogue Bidule works, maybe talk to the developer. Thanks for the report.
We will need to look at how Plogue Bidule works, maybe talk to the developer. Thanks for the report.
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
-
- KVRist
- Topic Starter
- 197 posts since 23 Jan, 2006 from Ontario, Canada
Thanks for looking into it. Bidule generally supports VSTs better than other hosts... except perhaps for this!
Perhaps a hint, the Bidule log file showed this:
UniWire Instrument wants vstTimeInfo, but no cando(receiveVstTimeInfo)
I'll try again tonight with the latest Bidule build (2006-01-05).
Perhaps a hint, the Bidule log file showed this:
UniWire Instrument wants vstTimeInfo, but no cando(receiveVstTimeInfo)
I'll try again tonight with the latest Bidule build (2006-01-05).
-
- KVRist
- Topic Starter
- 197 posts since 23 Jan, 2006 from Ontario, Canada
With Bidule build 2006-01-05, the behaviour was slightly different.
One instance (of UniWire FX) correctly provided the audio pipeline. Upon loading the second instance, the first kept going fine, but the second produced no sound. A third instance also was mute, while leaving the first still working. But a fourth instance caused the audio to change, sounding kind of like ring modulation, then it degraded and went silent.
To get audio back again, I had to unload all instances, cycle "Enable UniWire" on Receptor Setup, then re-load the VST into Bidule.
One instance (of UniWire FX) correctly provided the audio pipeline. Upon loading the second instance, the first kept going fine, but the second produced no sound. A third instance also was mute, while leaving the first still working. But a fourth instance caused the audio to change, sounding kind of like ring modulation, then it degraded and went silent.
To get audio back again, I had to unload all instances, cycle "Enable UniWire" on Receptor Setup, then re-load the VST into Bidule.