The Zebra Scripting Thread

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

billstei wrote:Simple Question #3724 - Global.Parameter[1203] is the Bypass On/Off for the Effects grid. What is the class name that it properly belongs to? My wrong guesses: Core.Bypass, VoiceMix.Bypass, VoiceCircuit.Bypass, Master.Bypass .
:shock: :shock: :shock:

Must be VoiceCircuit...

Nevermind. Bypass parameters are the on/off switches that you have in Filterscape/FilterscapeVA. They are pretty useless in Zebra because this is meanwhile solved on a more global scope (unused modulators don't process, as does nothing that's hidden in any Grid).

Cheers,

;) Urs
Top

Post

Urs wrote:
billstei wrote:Simple Question #3724 - Global.Parameter[1203] is the Bypass On/Off for the Effects grid. What is the class name that it properly belongs to? My wrong guesses: Core.Bypass, VoiceMix.Bypass, VoiceCircuit.Bypass, Master.Bypass .
:shock: :shock: :shock:

Must be VoiceCircuit...

Nevermind. Bypass parameters are the on/off switches that you have in Filterscape/FilterscapeVA. They are pretty useless in Zebra because this is meanwhile solved on a more global scope (unused modulators don't process, as does nothing that's hidden in any Grid).

Cheers,

;) Urs
I think what you're saying is that this does not exist on the Zebra GUI, but it does, and it does bypass the entire effects grid when I toggle it. So it must have a class name, but it's not VoiceCircuit@ from what I can tell.
Top

Post

I tried loading *all* the enums from the Parameter Name lists that I have been creating, and it will not compile. Here is the error:

OUT OF MEMORY ERROR: can't create int MMAP_MSRC_VELOCITY
Error in Line 735: Code -15

Keep in mind that there are probably hundreds of variables being created, and this is not something I need to actually do, so please don't waste time trying to fix this (now), but I just think it's interesting to see what happens when I torture the compiler. Bwahahahaha
Top

Post

billstei wrote:OUT OF MEMORY ERROR: can't create int MMAP_MSRC_VELOCITY
Error in Line 735: Code -15
Both compiler and virtual machine are pretty fast. Part of that is being limited to a maximum number of variables. In my code this is:

#define SCRIPT_MAX_FLOAT 256
#define SCRIPT_MAX_INT 256
#define SCRIPT_MAX_ARRAY_FLOAT 16
#define SCRIPT_MAX_ARRAY_INT 16

Which should usually be enough for any type of Smart Preset :)

Btw...

Try...

int numModulators = Modulator.count;

int idOfVelocity = Modulator.Velocity; // or any other ModSource

I have never tried that myself though, but from the looks of it it should just work...

;) Urs
Top

Post

Sounds good about the Modulator methods. Will add that to the list. Should have called that thread Parameter & Method Names I guess.
Top

Post

Modulator.Velocity is not correct. Also tried Modulator.velocity but nope.
Top

Post

billstei wrote:Modulator.Velocity is not correct. Also tried Modulator.velocity but nope.
Hmmm... must be a bug then... :oops:
Top

Post

This thread has been dormant for a long time. Did the scripting stuff ever get fully documented anywhere?
Top

Post

rockin1 wrote:This thread has been dormant for a long time. Did the scripting stuff ever get fully documented anywhere?
Nope.

We might go LUA at some point, for various reasons.
Top

Post

Urs wrote:
rockin1 wrote:This thread has been dormant for a long time. Did the scripting stuff ever get fully documented anywhere?
Nope.

We might go LUA at some point, for various reasons.
Is there still a plan to get it documented better and officially support it? I am very interested in diving into this...

Also, if you have any notes at all about where it's at today other than this thread I would love to see them. I can deal with a change down the road if that happens.

Also, it sounds like JavaScript is now out in favor of LUA if you make a change?
Top

Post

rockin1 wrote:
Urs wrote:
rockin1 wrote:This thread has been dormant for a long time. Did the scripting stuff ever get fully documented anywhere?
Nope.

We might go LUA at some point, for various reasons.
Is there still a plan to get it documented better and officially support it? I am very interested in diving into this...

Also, if you have any notes at all about where it's at today other than this thread I would love to see them. I can deal with a change down the road if that happens.

Also, it sounds like JavaScript is now out in favor of LUA if you make a change?
I don't think there's any better documentation of it, other maybe than the presets that were made for it. I had a webpage about it once (with not much more info), but that got sacrificed for server security.

JavaScript would be my favourite, but it seems that Lua is better suited for what we do.
Top

Post

Have you collected the presets anywhere? It would be nice to get a look at them in one spot. I can probably figure it out on my own, especially if I have a few working examples to look at...
Top

Post

rockin1 wrote:Have you collected the presets anywhere? It would be nice to get a look at them in one spot. I can probably figure it out on my own, especially if I have a few working examples to look at...
Check out the all-device-presets in http://www.u-he.com/PatchLib

There were more presets, but I can't remember where...
Top

Post

Awesome, thanks Urs! This should be plenty to get me started for now! :)
Top

Post

Urs wrote: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
Top
Post Reply

Return to “u-he”