The Zebra Scripting Thread

[rockin1]

it seems that Lua is better suited for what we do.

My vote is for Python! But I'd happily accept LUA too. Documented scripting in .h2p would be great.

Also Urs, I asked a question about volume scaling in spectroblend presets, if you could answer it for me I'd appreciate it:
http://www.kvraudio.com/forum/viewtopic ... 82#4669882

If we're voting I would vote for Ruby, but I think it will come down to Urs looking at what fits best for various reasons. Really, my preference is for whatever makes this happen in a fully documented and supported manner. I have many ideas...

[rockin1]

A couple more questions Urs...

What is the compressed binary data used for? I know not to touch it, but I'm mostly wondering about making patches from scratch with scripts. Is this data necessary? Can it just be copied from an existing preset? What should I be aware of in dealing with this section?

Also, would it be possible to have the preset reloaded if it changes on disk (or maybe an option to turn this on or off)? This would make working with scripts much easier...

[ojggaspar]

Hello,
Is there any way to lock a parameter via scripting and unlock it?

Code: Select all

Something like: 

Oscillator1.Tune = Lock; 

Oscillator1.Tune = Unlock;   

[Urs]

Not really I'm afraid. Only in a default preset I think.

[ojggaspar]

Ok!
And is there a way to address each individual step (or any steps at all), in the LFOs user waveform or the MMAP, through scripting ?

Something like:

Lfo1.Step.Value[1] = 18.0;

MMap1.Step.Value[1] = 99.0;

[Urs]

I don't think that was ever accomplished.

*sigh* sometimes I wished I had time to rewrite this. Because I wanted it to compile to byte code rather than interpret, it has become overly complicated. There was hope to use the engine for DSP, and the byte code was executed fast enough. Yet, that never materialised and today one would use LLVM. In the aftermath it would have been better to stick with an interpreter that's easy to maintain and great to work with.

[ojggaspar]

Well, can I ask (final question for now, I promise , will Zebra 3 have scripting capabilities similar or even better than Zebra 2 (and documented! ?

Thank you

[Urs]

I honestly don’t know yet.

[elnn]

Ok!
And is there a way to address each individual step (or any steps at all), in the LFOs user waveform or the MMAP, through scripting ?

Something like:

Lfo1.Step.Value[1] = 18.0;

MMap1.Step.Value[1] = 99.0;

I think this would be better off relegated to the host / a wrapper, rather than the plugin. Same interface for any device.
CLAP should address this, as I understand it?