Script Processor component state does not load with preset.

[d.healey]

@CyberGen Presets only store/restore the state of controls on the Interface script. So whatever controls you have in your secondary script that you want to restore with the preset need to be linked to some control on the Interface script.

[CyberGen]

@d-healey in doing that don't I loose the other parts of the controlCallback for that knob in the UI?

[d.healey]

@CyberGen said in Script Processor component state does not load with preset.:

don't I loose the other parts of the controlCallback for that knob in the UI?

Not sure what you mean.

[CyberGen]

@d-healey sorry, so when I link a control from the property editor, It takes over the controlCallback and only operates the linked component but does not run the controlCallback. Is there any other way to link them without loosing the controllCallback?

[d.healey]

@CyberGen When I said linked, I didn't necessarily mean through the property editor. You can do it through your control callback using setAttribute

[CyberGen]

@d-healey yeah, that is the way I have all the controls linked. But that does not seem to automatically recall the state of the non-UI script for me. Even recalling all the controllCallbacks post load only works inside HISE but not in the exported app.

[d.healey]

@CyberGen Maybe it's the order of your scripts, put the secondary script below the Interface script.

@CyberGen said in Script Processor component state does not load with preset.:

that does not seem to automatically recall the state of the non-UI script for me

It won't. It will recall the state of the controls on the UI - that is all a preset does - and the UI controls will set the secondary script's controls.

[CyberGen]

@d-healey said in Script Processor component state does not load with preset.:

Maybe it's the order of your scripts, put the secondary script below the Interface scrip

I've thought about that, but I believe that is not an option for me. I've tried that in the past (not because of this issue) and nothing works. That processor handles arpeggiator and glide functionality.

[d.healey]

@CyberGen said in Script Processor component state does not load with preset.:

I've thought about that, but I believe that is not an option for me. I've tried that in the past (not because of this issue) and nothing works. That processor handles arpeggiator and glide functionality.

I'd need to see an example where it's necessary to put the script before the Interface script, sounds unusual to me.

[CyberGen]

@d-healey Let me experiment moving things around a bit. Maybe a can split things up. I'll get back to you. I do think the solution could be there.

[CyberGen]

@d-healey said in Script Processor component state does not load with preset.:

Maybe it's the order of your scripts, put the secondary script below the Interface script.

So, I was able to move the glide/arp script below the interface one. Unfortunately, the problem persists. I can't think of a reason why it would work inside of HISE and not in the compiled version. Any other suggestions?

[d.healey]

@CyberGen Can you make a minimal example that demonstrates the issue with the scripts in those positions?