Zebralette 3 Bug Reports
-
- KVRAF
- 2066 posts since 11 Aug, 2012 from omfr morf form romf frmo
Crash on Windows 10, Reaper 7.15, CLAP when exporting wavetable, and choosing "Show...". A Windows (file) explorer window opens correctly as the plugin crashed and takes the DAW down with it. Simply choosing "OK" does not cause a crash and continues as normal.
-
- KVRist
- 168 posts since 18 Mar, 2004
I get A LOT of crashes with Reaper so I run it as a dedicated process as to not take the whole DAW down, but even as a dedicated process that still happens more than I'd like.
This is related to separate process mode, but when I first load the plugin the UI is usually mangled with certain parts cut off. Closing and re-opening the plugin or switching to generic GUI mode and back fixes it. It happens with a few other plugins too, so might be something Cockos can fix.
Another issue is anytime I save a preset Reaper disappears and another program is given focus (as if I had used Alt+Tab.) If I use Win+D to minimize all other windows first this doesn't happen.
When the plugin is running in normal mode (shared process) and I save a preset there's a brief flash as if it minimized and returned to the Window so it seems like the "bug" is still there, but it doesn't really bug me.
Hopefully the next beta is more stable so running it sand-boxed isn't as necessary.
This is related to separate process mode, but when I first load the plugin the UI is usually mangled with certain parts cut off. Closing and re-opening the plugin or switching to generic GUI mode and back fixes it. It happens with a few other plugins too, so might be something Cockos can fix.
Another issue is anytime I save a preset Reaper disappears and another program is given focus (as if I had used Alt+Tab.) If I use Win+D to minimize all other windows first this doesn't happen.
When the plugin is running in normal mode (shared process) and I save a preset there's a brief flash as if it minimized and returned to the Window so it seems like the "bug" is still there, but it doesn't really bug me.
Hopefully the next beta is more stable so running it sand-boxed isn't as necessary.
-
- KVRian
- 784 posts since 29 Mar, 2016
in bitwig when using the typing keyboard, the plugin keeps losing focus and I have to click the bitwig track over and over to get a note playing again.
-
- KVRian
- 784 posts since 29 Mar, 2016
Hi when exporting the wave and trying it in Vital, why does it sound different after importing it? Shouldn't it sound the same?
-
- u-he
- 30180 posts since 8 Aug, 2002 from Berlin
The exported waveform is based on the raw shape of the edited waveform. The Zebralette 3 oscillator can interpret that shape as a spectrum instead, and that would not be present in the exported waveform.xtreme sounds wrote: Wed May 29, 2024 11:26 pm Hi when exporting the wave and trying it in Vital, why does it sound different after importing it? Shouldn't it sound the same?
-
- KVRer
- 2 posts since 15 Jun, 2024
I just started testing this and I think both the sound and the UI are excellent! I am using this with MTS/ESP, it's great that microtonal support is already there. However, I would like to report the following issue:
The transpose function does not work correctly on scales that aren't 12 notes per octave. Apparently the transpose value is applied to midi note number and not to pitch. When using a scale with more or less than 12 notes per octave, this completely throws off the intervals between the notes.
This is especially apparent because the INIT sound and many of the presets are transposed one octave down by default.
If you could make it so that your INIT sound and most of the presets would be on center pitch (no transpose), that would already make the synth a lot more microtonality-friendly. Ideally, I think transpose should be applied to tuning rather than midi note (so for instance a +7 transpose becomes a 700 cents increase in pitch).
By the way, this issue is not specific to Zebralette, it affects other u-he instruments as well. I use Hive 2 and it has the same behaviour (both through MTS-ESP and directly with tuning files). There it also affects the arpeggiator, which is apparently applied to midi notes rather than to pitch (meaning it is only useable with a 1 octave range if you don't use 12 notes per octave, which is understandable, but also quite a shame). It would be fantastic if you could improve the microtonal behaviour moving forward!
The transpose function does not work correctly on scales that aren't 12 notes per octave. Apparently the transpose value is applied to midi note number and not to pitch. When using a scale with more or less than 12 notes per octave, this completely throws off the intervals between the notes.
This is especially apparent because the INIT sound and many of the presets are transposed one octave down by default.
If you could make it so that your INIT sound and most of the presets would be on center pitch (no transpose), that would already make the synth a lot more microtonality-friendly. Ideally, I think transpose should be applied to tuning rather than midi note (so for instance a +7 transpose becomes a 700 cents increase in pitch).
By the way, this issue is not specific to Zebralette, it affects other u-he instruments as well. I use Hive 2 and it has the same behaviour (both through MTS-ESP and directly with tuning files). There it also affects the arpeggiator, which is apparently applied to midi notes rather than to pitch (meaning it is only useable with a 1 octave range if you don't use 12 notes per octave, which is understandable, but also quite a shame). It would be fantastic if you could improve the microtonal behaviour moving forward!
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- Topic Starter
- 2170 posts since 22 Mar, 2005 from a planet called u-he
Thanks, I'll create an improvement ticket in our bug-tracking system. But can't promise anything, as I don't know when we'll find the time to dive into the MTS-ESP stuff again.Arithmophone wrote: Sat Jun 15, 2024 9:05 am It would be fantastic if you could improve the microtonal behaviour moving forward!
Adjusting the behaviour of arps and sequencers might be especially tricky, as it would likely require significant changes to our MIDI logic and voice circuits (can of worms, lots of potential for things going wrong).
That QA guy from planet u-he.
-
- KVRer
- 2 posts since 15 Jun, 2024
Thanks! I understand completely that this is tricky, microtonal midi is a can of worms all by itself and it's great that you already support it as well as you do. I think these limitations (not being able to use transpose, only being able to use arp with 1 octave range) are quite acceptable, the main downside for me at the moment is that I can't play most of the presets without making some adjustments first, and hopefully this can be changed relatively easily. I noticed that many of the presets in Hive are transposed -12, and I'm guessing this is because many sound designers start from an init patch and never change the transpose. So when I saw that the init patch in Zebralette 3 was also transposed -12, I just had to raise this point.
What would also be a very cool feature and (hopefully) easy to implement, is if you could add a tag like "microtonal supported" to any presets that don't feature transpose, multi-octave arps or melodic sequences, so we could just filter out the ones that won't work microtonally out of the box.
Finally, for if and when you would like to address the MIDI behaviour, I think I should clarify my original post: the current transpose / arp behaviour is dependent on both the number of notes in the scale and the intervals between them. So there are actually three different 'microtonal scenarios':
1) When using an irregular 12-note scale (for example just intonation): you can still transpose up and down by full octaves without problem, but transposing by other values than 12 or 24 will throw off the intervals between the notes on your keyboard. The arp remains fully functional in this scenario.
2) When using an equal temperament with a different number of notes (for example 31 EDO): you can still transpose up and down by EDO steps, although you can't transpose by a full octave in EDO > 24. For example, a transposition of +19 will have thes same effect in 31 EDO as a transposition of +7 in standard tuning. This actually makes a lot of sense, though it would be very useful if the transpose range were larger to facilitate larger EDOs. The arp becomes limited to one octave in this scenario
3) When using an irregular non 12-note scale (for example the 43 tone Partch scale): transpose becomes unusable and the arp is limited to single octave range.
What would also be a very cool feature and (hopefully) easy to implement, is if you could add a tag like "microtonal supported" to any presets that don't feature transpose, multi-octave arps or melodic sequences, so we could just filter out the ones that won't work microtonally out of the box.
Finally, for if and when you would like to address the MIDI behaviour, I think I should clarify my original post: the current transpose / arp behaviour is dependent on both the number of notes in the scale and the intervals between them. So there are actually three different 'microtonal scenarios':
1) When using an irregular 12-note scale (for example just intonation): you can still transpose up and down by full octaves without problem, but transposing by other values than 12 or 24 will throw off the intervals between the notes on your keyboard. The arp remains fully functional in this scenario.
2) When using an equal temperament with a different number of notes (for example 31 EDO): you can still transpose up and down by EDO steps, although you can't transpose by a full octave in EDO > 24. For example, a transposition of +19 will have thes same effect in 31 EDO as a transposition of +7 in standard tuning. This actually makes a lot of sense, though it would be very useful if the transpose range were larger to facilitate larger EDOs. The arp becomes limited to one octave in this scenario
3) When using an irregular non 12-note scale (for example the 43 tone Partch scale): transpose becomes unusable and the arp is limited to single octave range.
-
- KVRer
- 3 posts since 13 May, 2013
When a curve is deleted in the MSEG or in the OSC editor, then the displayed curved is not updated:
You do not have the required permissions to view the files attached to this post.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- Topic Starter
- 2170 posts since 22 Mar, 2005 from a planet called u-he
-
- KVRer
- 3 posts since 23 Oct, 2019
Bug I found:
1. Start Init.
2. Select Additive.
3. Go to the second wave and PreListen. (the one which is a triangle wave by default.)
4. Turn PreListen off.
5. Now it sometimes randomly plays wave2 (at 100%) when playing, instead of wave1 (which is still morphed at a 100%).
Doesn't happen with wavetable. Stops happening once I go back to wave1 window, even if I then go back to wave2 window.
It then only starts happening again, once I start and stop PreListen and remain on the wave2 window.
Hope this helps.
1. Start Init.
2. Select Additive.
3. Go to the second wave and PreListen. (the one which is a triangle wave by default.)
4. Turn PreListen off.
5. Now it sometimes randomly plays wave2 (at 100%) when playing, instead of wave1 (which is still morphed at a 100%).
Doesn't happen with wavetable. Stops happening once I go back to wave1 window, even if I then go back to wave2 window.
It then only starts happening again, once I start and stop PreListen and remain on the wave2 window.
Hope this helps.
-
- KVRAF
- 4196 posts since 23 May, 2004 from Bad Vilbel, Germany
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- Topic Starter
- 2170 posts since 22 Mar, 2005 from a planet called u-he