Zebra 2.3 Released!

[aMUSEd]

I hope I'm not going to have to do too much to make my KORE template for Zebra 2 compatible with the new version. What are the main new modules/functions added?

Actually I was going to ask about this. I first tried your template with the 2.3 beta, and I noticed that most of the kore knobs didn't control the right parameters in zebra. They'd control something other than what was named. I suppose the reason is because of the new modules. I might make my own anyways though.

That's what I was worried about - been holding off from trying the beta till the feature set was stable. Might be a lot of work to fix if everything has moved

Thinking about it, if you're right that so much has moved, wouldn't this also affect people who have projects in other hosts with automation set up for Zebra?

[Urs]

That's what I was worried about - been holding off from trying the beta till the feature set was stable. Might be a lot of work to fix if everything has moved

Thinking about it, if you're right that so much has moved, wouldn't this also affect people who have projects in other hosts with automation set up for Zebra?

Yes, possibly. Hence I guess I should enforce the customized parameter list, and by default customize it back to the order of Z2.2.

Lemme think about it.

[bagginz]

Urs,
when I use Zebra (latest beta) in Cubase4 it monopolises the focus of the (qwerty) keyboard.

I have to click back on Cubase4 to return the focus to Cubase and get my keypad acting as a transport again.

It doesn't happpen with the other VST synth plugs in the same session.

Is this by design? If not, any chance of fixing this? It's a little annoying having the sequencer transport controls disabled and having to grab the mouse and click around before they come back.

Cheers,
bagginz

Also, is there an alternative way of setting the cc numbers for the xy control, say by typing into a dialogue box?

Don't get me wrong, I love the convenience of midi learn, but trying to get Zebra to learn for example the xy pad on my Novation controller is a nightmare, because it sends out several midi CCs at once.

Sure, theoretically I can delve deep inside the bowels of the Novation and turn off the other 3 controllers leaving one, set midi learn then repeat with the next, then turn them all on again, but I'd rather just type in 71 and 73 in a box

[CJDJ]

Hi i'ts not a nightmare if you read the Manual of your Novation Controller 8)
On the XY Pad every triangle represents a different control. You only have to tap once not scratch. There is a good picture in the XioSynth Manual on Page 52. It's the same in every Novation controller.

_________________
Y1

X1 X2

Y2
_________________
I had the same problem first.

[bagginz]

Hi i'ts not a nightmare if you read the Manual of your Novation Controller
On the XY Pad every triangle represents a different control. You only have to tap once not scratch. There is a good picture in the XioSynth Manual on Page 52. It's the same in every Novation controller.

_________________
Y1

X1 X2

Y2
_________________
I had the same problem first.

Hello CJDJ,
thanks for the reply.

Yes, I am aware of a similar diagram in the Novation Remote SL manual, I was just looking at it an hour ago.

Now, bear in mind that I am definitely not talking about assigning the Novation's XY pad CCs to different parameters in the standard Zebra synth interface, that's easy enough. Tap and you're done.

I am talking specifically about the XY assign page. i.e assigning the Novation's pad to Zebra's XY pad on the performance page. It's a different story completely.

Try it, and let me know how you get on...

Cheers,
bagginz

[fgimian]

Urs,
when I use Zebra (latest beta) in Cubase4 it monopolises the focus of the (qwerty) keyboard.

I have to click back on Cubase4 to return the focus to Cubase and get my keypad acting as a transport again.

It doesn't happpen with the other VST synth plugs in the same session.

Is this by design? If not, any chance of fixing this? It's a little annoying having the sequencer transport controls disabled and having to grab the mouse and click around before they come back.

+1 yep I had reported this with 2.2 as well

This was the only additional bug I could find when playing with it yesterday.

I really wish this could also be fixed in a future maintenance update or similar.

Cheers
Fots

[Urs]

Sigh, we still have a problem or two. I had to fix a major glitch when used in MacOS X 10.3.9. Now I'm looking into the parameter automation thing.

I can't remove the greed for key strokes just yet though, as in I can't remove nor replace nor add features at this time.

Urs

P.S.: I'm having an ambivalent day - got to bed at 5am Berlin time, after California announced its vote. Hence I'm somewhat wasted today.

[viudu]

"Ambivalent day": Yes, it's strange how the U.S. has moved forward and back at the same time. What to take for an ambivalent day? Ambien!

[mabian]

Urs, I got deeper in the Arpeggiator problem and found an interesting thing.

The problem arises only when the "swing" option - the one with the flashing red square - is enabled; even in the preset about which I gave you the link, disabling the swing makes the problem vanish.

So, probably, the swing option prevents the arpeggiator from correct restart when starting transport.

Hope this info is useful for you.

- Mario

[bagginz]

I can't remove the greed for key strokes just yet though, as in I can't remove nor replace nor add features at this time.

O.k Urs fair enough, you're not omnipotent.

But I do have to say, having worked with several instances of this version of Zebra for a week or so, this bug is a major pain to work with in the context of writing a tune. (as opposed to creating patches)

Just so you know...

regards,
bagginz

[aMUSEd]

That's what I was worried about - been holding off from trying the beta till the feature set was stable. Might be a lot of work to fix if everything has moved

Thinking about it, if you're right that so much has moved, wouldn't this also affect people who have projects in other hosts with automation set up for Zebra?

Yes, possibly. Hence I guess I should enforce the customized parameter list, and by default customize it back to the order of Z2.2.

Lemme think about it.

Yes please do - if this sort of stuff is going to change with updates it's going to make it very hard to work with some projects and especially with KORE (or other software that relies on controller templates)

[tetsuneko]

HOLY MOLY BATMAN! I didn't notice the 2.3 release candidate until now :p

ProTools support.. can't wait to test this, jeez!

*six thumbz up*

[Urs]

Yo, we still have some small issues... mostly stuff that has always been there, or side effects form new stuff... gimme another couple of days for the final final

[Urs]

We're homing in on the final final!

Blood and tears went into the customizable parameter list and it seeems that I got it right this time. Hence the parameters seen by the host can now be ordered so that the ones from new modules (Sideband filters mostly) can be stuffed to the end of the list. This has the magnificent advantage that no Kore templates must be edited

#---

I also have headaches because of the Zebra2.data folder. I think I'll do things differently now. If any of Zebra2.data and C:\Program Files\u-he\ are present, both will be taken. If only one is present, just the one is taken. This will provide for the least screw-up-ability.

#---

Mr. Z needs a 64-bit version of Zebra2 and who am I to resist. Anyone with 64-bit Windows, keep an eye on the forum.

Later,

Urs

[Kyran]

I've got 64bit linux, does that count