Zebra 3 Beta Bug Reports

[PieBerger]

Not sure if it's a bug/design choice/WIP, but when adding a new mod slot within a source tab e.g. MSEG1, it loads a blank module, could/should this be context aware and load up with the appropriate source?

We've been thinking about it. Currently, it loads a generic mod slot, same as if you create a new mod slot on the mod matrix tab.
One problem we haven't solved yet: If we can make it so that it loads with the MSEG as source on the MSEG tab, what should it load as the source when creating a new mod slot on the Osc tab?

So a Work in Progress then I can see the conundrum you are facing, if Constant is reinstated as a mod source, perhaps it would be a good default assignment for the Osc tab?

[joradn]

Apologies if this is already known. In this example, 4in4 1 is going to the comb, but there is no visual routing displayed. Ignore 4in4 2, the same behaviour happens without it.

[Urs]

Apologies if this is already known. In this example, 4in4 1 is going to the comb, but there is no visual routing displayed. Ignore 4in4 2, the same behaviour happens without it.

Woah... ok! That would be a bug indeed...

[Andreya_Autumn]

This patch uses 4in1 scan mode with an LFO, and I'm hearing some zippering. Maybe something to look into?

[tasmaniandevil]

This patch uses 4in1 scan mode with an LFO, and I'm hearing some zippering. Maybe something to look into?

Thanks, we'll look into it.

[jnchristp]

I don't get the EQ-module at the moment...

Firstly: The initial graphics are way off. Switching to Resonator and back to Spectral Pan resets the display. I think that's a known issue.

But more important we should be able to turn a band on and off by double-clicking on it, like in Zebra2. That way a band keeps it's band-type while being turned off. At the moment I need to change a band to off, loosing the type. Using the mousewheel on an EQ-dot should increase/decrease the Q-factor. Maybe right clicking should give us the option to change the type, but that's not essential as there's an option above the graph.

[NAD]

I can't seem to get any modulator to trigger the Panic button in the Delay module. Interestingly, it is available as a drag-n-drop target but doesn't show up in the matrix target right-click menu, so I'm thinking maybe it's not meant to be a modulation target at all. I would like it to be though.

[Urs]

Hahaha, no, it certainly isn't meant to be a target...

[NAD]

Hahaha, no, it certainly isn't meant to be a target...

Oh

[Urs]

Hahaha, no, it certainly isn't meant to be a target...

Oh

If, then we could make it a trigger target... but that doesn't work through the ModMatrix, it only works as its own thing.

I'll keep that in mind.

[NAD]

That makes sense.

[gassle]

- Global Voice count doesn't seem to change, unless I switch it to Mono and back to Poly, then it updates. (at least with some initial patches I created). Seems to work ok after I do this switch once in a patch.

[Urs]

- Global Voice count doesn't seem to change, unless I switch it to Mono and back to Poly, then it updates. (at least with some initial patches I created). Seems to work ok after I do this switch once in a patch.

Voices are usually cycled through all 16, with few exceptions. The global voice setting just sets the maximum number of voices that are heard at the same time. If this number is exceeded, then voices are "discharged", i.e. quickly faded out, to bring it back to the desired maximum. So for a brief time, the number of voices can go higher.

[NAD]

OK so I think this could definitely be a real bug:
- Apply LFO1 to anything just so it's active, then view it in the scope
- Set the trigger to "Sync" (should be default)
- Set the waveform to "Rand Glide" ("Rand Hold" seems to have the same problem)
- Play some notes and look at the scope
= It appears that the LFO moves to a random value at the start of every note, contrary to what I'd expect from the Sync trigger mode. In fact, this happens with all trigger modes, whereas I would think there should be at least one that doesn't do that.

[machinesworking]

Report bugs here! Or send them to support at u-he dot com

But please check if the bug has already been known or reported:

[*] All the Gremlins we didn't catch yet[/list]

Hey I do not think this is necessarily a bug but it is significantly different than ZebraHZ /2.
When addressing the host automation parameters in Digital Performer 11, and with smart hardware like the new 2.0 version of Kontrol mk3, the automation presents nothing of use for the first 8-16 slots.

Inside DP11 I can see the 1000 slots in Zebra3! , but trying to find the most obvious choices (besides Output), is impossible. Are there plans to order the automation as presented so that the Control A to D at least show up in the first 8 slots? Zebra 2 had it's 8 XY slots in the first 16 host automation parameters presented to DAWs and the Kontrol mk3. This is how it should be, the user assigned automation macros in a preset are quickly addressable by controllers that read host automation, and in all DAWs as the first things in the list.

Count me in as someone who has wondered for 20+ years why this hasn't been a # 1 concern among developers? I assume it's much harder than I imagine to assign the automation presented?

Also count me as someone who thinks we should have at least 8 Control (Macro) slots. Almost every controller presents 8 knobs.