Improvements!

[Mighty Pea]

I like tagging, even if it would only be semi-tagging by means of allowing one to search the description. To change a description though, am I right in thinking you need to save the preset again? The problem with this (as I found when saving presets to a Favourites folder) that you need retype the name of the patch's creator, and next time you want to save a patch of your own, that name will still be in the 'author'-section.

[Urs]

I like tagging, even if it would only be semi-tagging by means of allowing one to search the description. To change a description though, am I right in thinking you need to save the preset again? The problem with this (as I found when saving presets to a Favourites folder) that you need retype the name of the patch's creator, and next time you want to save a patch of your own, that name will still be in the 'author'-section.

Try it... the name of the patch creator stays unless you change it

However, the patch meta data is mostly a description of what's going on in the patch and how to use it (i.e. "use Modhweel to mangle filter"). The system wasn't so much put in place for Zebra or instruments in general but for effects such as MFM and Filterscape. Unlike synths, these fx highly depend on the source material hence preset descriptions have to explain what they're meant for. Otherwis people just run presets through a drum loop even though the presets were meant for vocals - and wonder why the fx sounds like shyte. Which is actually something that no meta tagging can replace.

Nevertheless, I think only few people are eager to comprehensively tag their patches. I think that most people just need an aid to separate the patches that are usable for them from the patches they don't like.

I also highly doubt that patches can be proeprly pre-tagged ("factory tags") apart from the really stereotypical ones. I also think that good patches can be tagged everything.

Urs

[blurk]

Nevertheless, I think only few people are eager to comprehensively tag their patches. I think that most people just need an aid to separate the patches that are usable for them from the patches they don't like.

Actually, that is a good summary of what I would use a tagging system for. I don't really want to go out to the host OS file system and reorganise the preset directory structure etc., and I don't really want to copy "favourite" presets because I prefer to keep patch set collections (e.g. Transmission, Old Skool) together. FWIW.

[Mighty Pea]

To be fair, what Blurk said also applies to me. As well as your assertion that descriptions (and tags, really) are more applicable to effects than a synth.

[bagginz]

Urs,
a few suggestions for improvements that spring to mind:

1, On the flanger module make zero on the <speed> parameter stop the LFO completely.

This way we could assign a mod wheel (or alternative mod source) to the <centre> parameter to use the flanger as a nice clangy stereo comb filter - which has a completely different character to the comb module.

Currently this isn't possible because the flanger lfo is always engaged.

Also this allows longer sweep times if we assign an available LFO. (btw the manual says flange lfo times go down to 0.001 hz, which doesn't appear to be the case.)

Also, more extreme settings for the flange module generally would be useful - longer flange/chorus delay times, slower native lfo sweep.

2, Delay Module: add bypass switches for each of the delays rather than current method of setting one side to a 4 sample minimum. On high feedback settings this can cause a skewed stereo image and also runaway feedback - of the unpleasant kind.

3, Another two modes for the shaper module. I propose:

a) Extreme distortion.

Warm and fuzzy territory is well covered by the current modes and filter saturation. I am talking raspy and snarling here. if you want an example, check out the surprisingly good new distortion plugin that comes with Cubase4 (not the amp sim.)

b) Sample reduction - Sonically speaking, Logic Audio's sample redux (bit crush plug) is one of the best implementations

Apart from expanding the sonic possibilities nicely, this will enable use of the onboard effects when creating that type of sound. Currently I have to bus out to a plugin, thereby losing the opportunity to use Zebra's nicely integrated effects.

4, The ability to save and recall individual Flange, Reverb and Delay settings in the same way as oscillator settings etc. would be really useful and a real time saver. I seem to spend a lot of time re-creating my favourite settings for these modules over and over.

5, Perhaps it's just me, but I really think that clicking on a module on the synth grid should jump Zebra directly into <synthesis> mode if one is in either; <performance> or <preset> mode.

Perhaps I am missing something, but why else would one click a module if one didn't want to edit something? This saves having to switch into edit mode, before being able to edit.

That'll do for now

Cheers,
bagginz

p.s.
big thanks for an excellent 2.3 update.

Love the new custom GUI sizing, unempty horse skin, compressor modes, new oscillator FX, osc reset switch ...

[Urs]

Here's a new build:

Zebra23MacInstall (VST & AU, RTAS Mac)

Zebra23Winstaller (normal installer for Windows)

Zebra23pre-installed (with Zebra2.data for Receptor, Everything In Vstplugins)

- restructures the parameter list, makes it compatible to existing automation and Kore templates
- unleashes space bar and other keys in Cubase/Win
- switching GUI schemes should be flawless now

Also, I hope those crashes described before are now gone... I can still not reproduce them...

Cheers,

Urs

[bagginz]

Here's a new build:

- unleashes space bar and other keys in Cubase/Win

Urs

Brilliant! You're a star.

Downloading now...

bagginz

[Urs]

Hope it works! It hasn't undergone extensive beta testing this time...

[bagginz]

Hope it works!

So do I

Not having the keyboard transport controls always available when working with a sequencer is a major PITA

But either way, I appreciate your effort in getting a potential fix out so quickly.

Cheers,
bagginz

[bagginz]

Urs,

The querty keyboard is back, so that seems to work fine so far... (WinXP + Cubase4.52)

Graphic distortions still appear (white vertical and horizontal lines when moving the GUI over and edge of the screen and back)

No other bugs spotted so far

Thanks for the fix

cheers,
bagginz

[hakey]

How about having some ability to morph between different versions of the same preset using an XY control? I know that that assigning the X or Y axis to modulate various parameters does in a way do this anyway, but my idea differs in how assigning the mod. amounts is achieved.

I envisage it working like this: a user makes would up a patch and 'save' that to one corner of an XY controller. they could then tweak that patch to their taste (without adding any modules, modulation routings etc) and save a new version to another corner and so on until they have a different set of settings in each corner. Different points within the XY square would correspond to morphs between the different settings for that patch. This way it would be possible to morph between radically different versions of the same patch involving many simultaneous parameter changes.

I would imagine it's quite a lot to ask for and I'm sure that there's reasons why it could be difficult to implement.

Whilst I'm thiking about it - someone else mentioned the ability to record and play back movements in the XY square (in the vector post) - some Reaktor ensembles have it and I think it could be fun in Zebra.

[phazed]

Don't know if this has been requested before, but I like to have some more fine-grained control when loading OSC presets. Namely I want to be able to load the waveform-related parameters only without overwriting the other settings like detune, mod settings, fx etc. Maybe a checkbox in the load dialog would do it.

[Urs]

Don't know if this has been requested before, but I like to have some more fine-grained control when loading OSC presets. Namely I want to be able to load the waveform-related parameters only without overwriting the other settings like detune, mod settings, fx etc. Maybe a checkbox in the load dialog would do it.

That's on the list!

[aMUSEd]

How about having some ability to morph between different versions of the same preset using an XY control? I know that that assigning the X or Y axis to modulate various parameters does in a way do this anyway, but my idea differs in how assigning the mod. amounts is achieved.

I envisage it working like this: a user makes would up a patch and 'save' that to one corner of an XY controller. they could then tweak that patch to their taste (without adding any modules, modulation routings etc) and save a new version to another corner and so on until they have a different set of settings in each corner. Different points within the XY square would correspond to morphs between the different settings for that patch. This way it would be possible to morph between radically different versions of the same patch involving many simultaneous parameter changes.

Theoretically it should be possible to do this in NI KORE 2 and I've tried several times to create presets that morph this way using Kore's 8 square XY system. In practice though it seems there's something about Zebra (also true of Filterscape VA I've noticed) that prevents it being able to morph in a smooth fashion even within one fixed structure. Everytime I try and morph the sound cuts out for a split second and morphing is jerky and unpredictable. Other people have reported this too. It doesn't seem to be a limitation of KORE as I can do this with most synths and effects so must be something to do with how Zebra deals with massive changes in several params at once.

[hakey]

Well, on further reflection I wonder if xy patch morphing is maybe a bit too gimmicky? In Reaktor you can morph between presets, but I it's not a feature that I really use a great deal.

On a slightly different subject the ability to 'undo' changes whilst editing patches would be useful. Several times I've created a patch and then tweaked it just a little too much and been unable to remember the changes I've made. Of course it is possible to save a patch at any point, but to do this one has to either overwrite the last version of a patch, or give successive patches new names thus filling up the patch folder with temporary patches, which one would have to delete by hand afterwards. If not the ability to undo each change infinitely, then perhaps a save to buffer button that stores a number of recall points for the present patch would be useful?