zebra2

[beej]

Wonshu - cheers for that, that works for me. Dunno why it wasn't before, I swear I tried everything, including that config, which is the most visually obvious. But I obviously didn't!

EDIT: No, there's definitely odd behaviour with the bussing. I had two lines, the first set to main, the second the bus 1. Stick a reverb on bus and turn up the return. Cool I can hear reverb on osc 2.

Then I add a delay and it craps out. Now I set both lines to main, leave the reverb on bus 1 with no sends, and I can still hear reverb even though I shouldn't. And using a delay instead of reverb really confuses it. This was why the conventional routing wasn't working for me before.

I'll investigate it a little bit and try and boil it down to reproducible steps...

[beej]

Ok, to try and recreate some of the weird beahviour, can anyone try out the following:

- Load Zebra, and start with the default Z2 patch
- Insert OSC 1 at top of line 1
- Insert OSC 2 at top of line 2
- Tune OSC2 up two octaves, to make hearing easier
- Remove MODFX from FX grid 1
- Insert rev at top of FX 1 grid line 1
* we hear reverb on the mains with both oscillators, cool

- Move rev 1 to top of FX grid line 2
* no reverb
- Turn up Return 1
* we hear reverb even though we shouldn't (the rev is on bus 1 and no audio is sent to bus 1 yet)
- Switch line 2 with OSC 2 to bus 1.
* OSC2 disappears, and with wet osc 1, though we should only hear dry OSC 1 and wet OSC 2

- Change rev to delay (still on FX line 2)
* Sounds correct - dry osc 1, wet osc 2 (turn up the mix parameter in the delay so we can hear it)

- Move delay to FX line 1 - we should hear wet osc 1 only
* instead we hear wet osc 2, and osc 1 has gone

If you can reproduce this, you can see that the behaviour is strange. Either it's buggy at the moment, or I'm failing to understand the routings correctly.

[luCiPHer]

you fail to understand the routings correctly

the fx grid is modular in the same way the upper grid is, and in your example the rev1 module still receives input from fx gridline 1, rightclick on the rev1 module, change the input to 2, and everything works like want it to.

not a bug, a feature, zebra is modular

[Urs]

Hi beej,

Hmmm... please ctrl-click/right-click the reverb... does it say "same" or does it say "input 1"?

There's some stuff in the Grid Control that's problematic: The FX Grid doesn't draw lines to the top of the matrix. Thus, if a module is connected to another channel than it sits on, this isn't reflected in the graphics if it's the top most effect. (Apart from the bug that some lines won't be drawn which freaks me out anyway)

Maybe this is it?

If not, please send me the patch!

Cheers,

Urs

[Urs]

Ah... luCi, you beat me to it!

Nevertheless, this has to be considered a drawing bug!

Cheers,

Urs

[luCiPHer]

yes, lines to the top of the grid would certainly make things like this less enigmatic

[beej]

you fail to understand the routings correctly

I'm trying!
But that's why I was posting here for some advice, because it wasn't 'clicking' for me.

the fx grid is modular in the same way the upper grid is, and in your example the rev1 module still receives input from fx gridline 1, rightclick on the rev1 module, change the input to 2, and everything works like want it to.

not a bug, a feature, zebra is modular

Cool - lemme digest the replies and have another play...

[beej]

yes, lines to the top of the grid would certainly make things like this less enigmatic

So would a manual...

[Urs]

yes, lines to the top of the grid would certainly make things like this less enigmatic

So would a manual...

Not finsihed (no pics, some paragraphs missing):

http://www.u-he.com/zebra/manual



Cheers,

Urs

[beej]

I'm already learning stuff!

It's nice to get some description of various filter modes and waveform FX etc. Good stuff, thanks for doing this...

[beej]

Hmmm... please ctrl-click/right-click the reverb... does it say "same" or does it say "input 1"?

Ok, I understand - the reverb module was still set to "Input 1", wherever I moved it.

My conceptual understanding is still foggy though. Inputs 1 to 3 correspond to the three FX grid vertical lines, in the same way as the synthesis grid. Fine.

But those three lines - what do they represent?
Is it:
Main = FX Input 1
Bus1 = FX Input 2
Bus 2 = FX Input 3

In that case, the sends 1 and 2 therefore must control sends from the master buss to busses 1 and 2 respectively. Ok, I think I've got it now.

I do feel the lack of labelling and different terminology has been confusing. if the lines were labelled "Main, Bus 1 and Bus 2" I would have got it straight away. Or even if the Main buss was shaded/coloured different to the two FX busses. As it is, the routing is not obvious from the interface, and there was nothing to suggest that "Input 1 = Main Buss" in the popups etc.

Yes, I know i should RTfM, but there wasn't one and it's the only thing that has been non-intuitive without prior knowledge.

Phew! It's finally clicked!

[wonshu]

[beej]

Got there in the end!

[Urs]

But those three lines - what do they represent?
Is it:
Main = FX Input 1
Bus1 = FX Input 2
Bus 2 = FX Input 3

Yes!

You're right though... I should find a way to name them "main", "bus1" and "bus2" in the popup menu...

Cheers,

Urs

[blitze]

Love the preview and I think of all the VST's I've demoed recently to add to my collection this would be it but I have a little concern (this is a general comment with current crop of VST's) some of the demo banks like the set from Biolabs are very CPU intensive and with my paltry setup leads to clipping. I'm running the preview through Tracktion 2 on Windows XP with 1gig of ram and a Dual AMD Athlon MP 2000+ rig. Will the final release be a little CPU friendly (and given this is only for a few patches, most were fine)?

Other than that it's an awesome instrument which would compliment my small VST collection (Vanguard, Albino 2, Absynth).