Feature Brainstorming for Zebra.

[Urs]

I really need a WestGoingCamelsaurus and an EastGoingCamelsaurus for a complete set of EQ curves.

Well, but in Australia both of these would go north...

[billstei]

I really need a WestGoingCamelsaurus and an EastGoingCamelsaurus for a complete set of EQ curves.

Well, but in Australia both of these would go north...

No, you're thinking of the The Zax EQ curve is a wide bandpass or bandcut, depending on north or south goingness.

[billstei]

That EQ script got me thinking about a possible tool...

What if there were a program that would extract all the parameters of a specific module out of an existing h2p patch file, and then output a script that sets (only) those parameters. Say, for example, you have a preset that has an XMF module set up a certain way that you want to import into a new preset. You point the tool at the previous preset file, it extracts only the XMF module parameters, then writes a script that initializes just that XMF, and the resultant script file, as a "delta patch", is loaded into Zebra. A "Module Copy Paste" tool. And it would/could do multiple modules all in one go.

Uber sound designers, what say ye? Useful, or silly waste of time?

[amoeba]

What if there were...

i'd like that. i tend to start with modules by setting them to my own "zero". this would be a great way to load 'default' modules, and build libraries of each.

since they are just text files, the basics should be easy. knowing what patch is loaded, and injecting it into the current patch, AND having zebra/host pick it up... now there's the trick!

but don't let me discourage you... you don't seem to be the discouragable type anyway (and i mean that in a very good way)

[kajiotaku]

What if there were...

+1

[billstei]

I would probably do a proof-of-concept with a command line tool first. And I'm leaning a bit towards writing it in Python (even though it's an evil snake language, and Ruby is my true love). So, something like this:

organdonor.py -i MyTrustyOldPreset -m FMO1,EQ2,VCF1 -o MyFav3Modules

or this syntax defaulting to stdout, so that pipes work:

organdonor.py -i MyTrustyOldPreset -m FMO1,EQ2,VCF1

So in the example above the modules FMO1, EQ2, and VCF1 are extracted out of the preset called "MyTrustyOldPreset" and a new "delta patch" called "MyFav3Modules" is created, which is loaded into Zebra as/when needed.

Or another idea that I tend to like:

organdonor.py -i MyTrustyOldPreset -x FMO1 -o MyFMOxModule

that loads FMO1 settings into all/any active FMO's in Zebra at the time the script runs.

Anyway, these are just some brain farts. I really need to hear from Grand Master Poobah Sound Designer Howard, et al, before I go crazy building some infernal contraption.

[Howard]

I really need to hear from Grand Master Poobah Sound Designer Howard, et al...

Ask Al first - I'm a crap beta tester.

[billstei]

I really need to hear from Grand Master Poobah Sound Designer Howard, et al...

Ask Al first - I'm a crap beta tester.

As you wish, I am but your humble servant.

IF SOMEONE NAMED "AL" IS HERE, WHO CAN EVEN COME CLOSE TO HOWARD'S ABILITIES WITH ONE OSCILLATOR TIED BEHIND HIS BACK, PLEASE RAISE YOUR HAND.

[jupiter8]

I really need to hear from Grand Master Poobah Sound Designer Howard, et al...

Ask Al first - I'm a crap beta tester.

As you wish, I am but your humble servant.

IF SOMEONE NAMED "AL" IS HERE, WHO CAN EVEN COME CLOSE TO HOWARD'S ABILITIES WITH ONE OSCILLATOR TIED BEHIND HIS BACK, PLEASE RAISE YOUR HAND.

I can call you Betty and when you call me,you can all me Al.

[billstei]

I can call you Betty and when you call me,you can all me Al.

If I had known jupiter8 would come out of hiding by simply yelling nonsense I would have made a fool of myself sooner.

@Howard - Al is not answering his page, and since I don't need any beta-testers (I can summon them any time by just saying "Arise my beta testing minions and eat the flesh of many bugs"), what I'm really wondering is whether your workflow ever has you wishing you could copy-extract entire modules from pre-existing presets, and import them into a preset you are working on... ?

[Howard]

...what I'm really wondering is whether your workflow ever has you wishing you could copy-extract entire modules from pre-existing presets, and import them into a preset you are working on?

I think individual module templates (XMF, Comb, Arp, FMO) should be handled like the Osc and MSEG templates - so I guess that should be left up to Urs. BTW: Inserting complete FX patches (replacing whatever is in there) would also be a useful function.

[bmrzycki]

BTW: Inserting complete FX patches (replacing whatever is in there) would also be a useful function.

That would be very nice. There are some great FX chains out there.

Not only that but it'd make it a great start to Zebrify presets.

[billstei]

...what I'm really wondering is whether your workflow ever has you wishing you could copy-extract entire modules from pre-existing presets, and import them into a preset you are working on?

I think individual module templates (XMF, Comb, Arp, FMO) should be handled like the Osc and MSEG templates - so I guess that should be left up to Urs. BTW: Inserting complete FX patches (replacing whatever is in there) would also be a useful function.

I was thinking the same thing, that Urs would eventually have module templates, but if we assume that he is up to his neck in alligators (er, crocodiles) then it might be a long time before we have that available. I might be able to bang out a little program much sooner. The FX chain example is a good one, but unfortunately I don't think I can force a module unto the grid, or wire it, using scripting. Or can I? (Urs?).

[Urs]

Or can I? (Urs?).

Yes you can.

Code: Select all

#defaults=no
<?

Grid.clear();

Grid.setCell( 0, 5, Filter[ 2 ].id, 0, 0 );

?>

GridObject.setCell( channel, row, ModuleID, inputChannel, sideChainChannel );

Forgot to mention that anywhere

[billstei]

Or can I? (Urs?).

Yes you can.

Code: Select all

#defaults=no
<?

Grid.clear();

Grid.setCell( 0, 5, Filter[ 2 ].id, 0, 0 );

?>

GridObject.setCell( channel, row, ModuleID, inputChannel, sideChainChannel );

Forgot to mention that anywhere

Hmmm. Lots of new questions...

1) Is there a different keyword for the FX grid, or is it just a higher "row" argument?

2) Is there a difference between GridObject.setCell and Grid.setCell, or are these synonyms (aliases), or ... ?

3) Can I alter inputChannel or sideChainChannel specifically without calling ::setCell, something like:

XMF1.gridSet.sideChainChannel(channel);

4) I bet I can do this: Grid.removeCell( channel, row ); I should probably just put on my Super-Hacker cape for this one.