some small bugs:
* somehow Zebralette doesn't like to be muted by Bidule (like with most hosts you can select three modes in Bidule for every module/module group: "Processing", "Mute" and "Bypass". If one switches the group that contains the Zebralette instances to "Mute" and then back to "Processing" one get's gargleblasted clicks and blops only. The only cure is to open each Zebralette instance by hand and select an arbitrary preset. This isn't an issue with the full Zebra2 version, it only happens with Zebralette.
* Both Zebra2 as well as Zebralette don't allow to automate preset switching (tried it directly with Bidule and with EnergyXT - in both cases both synths only offer a "initialize" preset instead of the current preset list that is shown in the internal plugin browser.)
NothanUmber
muting zebralette
-
- KVRist
- 392 posts since 1 Jul, 2004
-
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Hmmm, not sure about the mutability of Zebralette... the code for Zebra2 and Zebralette is virtually identical, except Zebralette uses less modules...
Not automating the presets is a good thing here... these automated switches usually don't happen in the user thread but in a critical realtime thread. As Zebra has to mangle more than 10000 parameters (1000 something automatable and a shitload of not automatable ones) with each preset switch, it simply takes time... which in Zebra1.5 (where this was possible) led to drop outs and sometimes even to crashes... thus I have taken this functionality away for safety reasons...
Cheers,
Urs
Not automating the presets is a good thing here... these automated switches usually don't happen in the user thread but in a critical realtime thread. As Zebra has to mangle more than 10000 parameters (1000 something automatable and a shitload of not automatable ones) with each preset switch, it simply takes time... which in Zebra1.5 (where this was possible) led to drop outs and sometimes even to crashes... thus I have taken this functionality away for safety reasons...
Cheers,
Urs-
- KVRist
- Topic Starter
- 392 posts since 1 Jul, 2004
Oh, that's a pity 
(My plan was to build a neat controlling interface (with lot's of midi capabilities) that allows me to control and make meta presets for all of my synths and effects as a whole. For that preset automation of the single plugins is crucial. (Unfortunately encapsulating the Zebras in separate EnergyXT or Bidule subhost instances isn't a solution as none of the subhosts I know supports automatible presets atm... ). It's no problem if switching takes it's time as long as it's possible at all (Zebra will surely be able to switch to another preset before the sample oscillator (aka Kontakt2) has loaded it's new sample set ).
Would be really nice, if you could reenable that feature again at some point in the future (after the bug hunt is over of course).
Greetings,
NothanUmber
(My plan was to build a neat controlling interface (with lot's of midi capabilities) that allows me to control and make meta presets for all of my synths and effects as a whole. For that preset automation of the single plugins is crucial. (Unfortunately encapsulating the Zebras in separate EnergyXT or Bidule subhost instances isn't a solution as none of the subhosts I know supports automatible presets atm...
). It's no problem if switching takes it's time as long as it's possible at all (Zebra will surely be able to switch to another preset before the sample oscillator (aka Kontakt2) has loaded it's new sample set ).Would be really nice, if you could reenable that feature again at some point in the future (after the bug hunt is over of course).
Greetings,
NothanUmber
-
- KVRist
- Topic Starter
- 392 posts since 1 Jul, 2004
Have just tested again: The Zebralette mute problem with Bidule is absolutely reproducable (using the VST version of Zebralette under WinXP (32 bit version, SP2) with an Indigo I/O notebook audio card (ASIO-drivers) and Bidule 0.9203 (latest stable release)):
* Open a bidule instance (in standalone mode)
* insert a midi in module that is connected to a keyboard
* insert a asio duplex in/out device and connect a mixer to the output
* insert a zebralette instance
* connect the midi out of the midi module to the midi in of Zebralette and the Zebralette output to the input of the mixer
* open the Zebralette plugin (the default sawtooth preset will do fine)
* play some chords (working as expected)
* switch Zebralette to "Mute" (possible e.g. with the "Mode" Dropdown menu at the top of the plugin window)
* switch the mode back to "Processing"
* now all one can hear are some strange crackles
Don't know if that is Zebralette's or Bidule's fault but it doesn't happen with any other plugin I tried (not even Zebra2 - I'm using the Zebra and Zebralette beta versions from 2006-08-03)
NothanUmber
P.S.: Found the (probable) source of the problem: If one mutes the instrument the "Oscillator Tuning" parameter (the knob in the upper left) jumps to "-48". If one manually moves it back to it's old position everything works as expected again.
* Open a bidule instance (in standalone mode)
* insert a midi in module that is connected to a keyboard
* insert a asio duplex in/out device and connect a mixer to the output
* insert a zebralette instance
* connect the midi out of the midi module to the midi in of Zebralette and the Zebralette output to the input of the mixer
* open the Zebralette plugin (the default sawtooth preset will do fine)
* play some chords (working as expected)
* switch Zebralette to "Mute" (possible e.g. with the "Mode" Dropdown menu at the top of the plugin window)
* switch the mode back to "Processing"
* now all one can hear are some strange crackles
Don't know if that is Zebralette's or Bidule's fault but it doesn't happen with any other plugin I tried (not even Zebra2 - I'm using the Zebra and Zebralette beta versions from 2006-08-03)
NothanUmber
P.S.: Found the (probable) source of the problem: If one mutes the instrument the "Oscillator Tuning" parameter (the knob in the upper left) jumps to "-48". If one manually moves it back to it's old position everything works as expected again.
-
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Heard similar things about live 6... well, maybe different.NothanUmber wrote:P.S.: Found the (probable) source of the problem: If one mutes the instrument the "Oscillator Tuning" parameter (the knob in the upper left) jumps to "-48". If one manually moves it back to it's old position everything works as expected again.
The problem here is *certainly* a so-called "accidental MidiLearn". Right-click the tune knob twice and it will go away.
(I must find a better solution for that)
Later,
Urs-
- KVRist
- Topic Starter
- 392 posts since 1 Jul, 2004
Indeed, it was...Urs wrote: The problem here is *certainly* a so-called "accidental MidiLearn"
Perhaps add a dedicated "midi learn" toggle that has to be enabled in order to trigger midi learn. (One enables the toggle and then just moves the knob of choice a little and sends the desired midi event and the knob is coupled to that event type from there on. After that one disables the midi learn toggle again in order to prevent further "accidental midilearns").
Thanks again for help!
Greetings,
NothanUmber
-
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Hmmm, yeah...
I thought of opening a context menu for that on right-click, but a global MidiLearn toggle would probably do the trick as well... it would still just work with right-clicks...
... we'll see...
Urs
I thought of opening a context menu for that on right-click, but a global MidiLearn toggle would probably do the trick as well... it would still just work with right-clicks...
... we'll see...
Urs