Old 01-29-2024, 01:37 PM   #1
whats_up
Human being with feelings
 
Join Date: Nov 2020
Posts: 179
Default question for SAIKE about slider_automate syntax

hello saike.
while trying to build filther with
codebase

i found this:
Code:
slider_automate(
                  slider1 = slider2;
                  slider19 = slider3;
                  slider20 = slider4;
                  slider21 = slider5;
                  slider22 = slider6;
                  slider23 = slider7;
                  slider24 = slider8;
                  slider25 = slider9;
                  slider26 = slider10;
                  slider27 = slider11;
                  slider28 = slider12;
                  slider29 = slider13;
                  slider30 = slider14;
                  slider31 = slider15;
                  slider32 = slider16;
                  slider34 = slider18;
                );
can you please explain this ?
is it using slider_automate
sequently for each slider after been set by the right slider ?

thanks in advanced
__________________
Easy EEL to VST Building system
https://forum.cockos.com/showthread.php?t=245285
github: https://github.com/VisualCodeBase/CodeBase
whats_up is online now   Reply With Quote
Old 01-29-2024, 03:33 PM   #2
sai'ke
Human being with feelings
 
sai'ke's Avatar
 
Join Date: Aug 2009
Location: NL
Posts: 1,453
Default

Honest answer: I think that doesn't do what I thought at the time it did. I was still getting to grips with JSFX back then and played things fast and loose

I think to notify reaper of the parameter change, I should've done a slider_automate on each slider separately after making the change.

That said, considering that that functionality copies parameters from one polarity of the waveshaper to the other. I don't really see the usefulness of recording an automation action for that particular action. This seems like something you do during waveshaper setup, rather than automation. I'll do a fixup commit where I remove the slider_automate call entirely.

Thanks for the heads up.
__________________
[Tracker Plugin: Thread|Github|Reapack] | [Routing Plugin: Thread|Reapack] | [More JSFX: Thread|Descriptions|Reapack]

Last edited by sai'ke; 01-29-2024 at 03:53 PM.
sai'ke is offline   Reply With Quote
Old 01-29-2024, 04:21 PM   #3
sai'ke
Human being with feelings
 
sai'ke's Avatar
 
Join Date: Aug 2009
Location: NL
Posts: 1,453
Default

Now that we have touch automation, I should actually go back and check all my uses of slider_automate across all the plugins anyhow.

AFAICT, the following ways of using slider_automate work in the sense that the last touched slider becomes named_slider or slider(N) (rather than 5), though I'm not sure why.

Code:
slider_automate(named_slider = 5);
Code:
slider_automate(slider(N) = 5);
The API only documents that:
Code:
slider_automate(slider4);
or
Code:
slider_automate(2 ^ sliderindex);
should work.

Based on the API docs, I would expect the expressions in the assignment case to return "5" to automate. Though I might be thinking of this wrong and it is using pattern matching or checks whether the last assignment target is a slider identifier.
__________________
[Tracker Plugin: Thread|Github|Reapack] | [Routing Plugin: Thread|Reapack] | [More JSFX: Thread|Descriptions|Reapack]

Last edited by sai'ke; 01-29-2024 at 04:32 PM.
sai'ke is offline   Reply With Quote
Old 01-30-2024, 10:20 AM   #4
whats_up
Human being with feelings
 
Join Date: Nov 2020
Posts: 179
Default

thanks.
about the behave of slider_automate
i already discussed this with birdbird
at codebase thread.
he discovered unique behave.
__________________
Easy EEL to VST Building system
https://forum.cockos.com/showthread.php?t=245285
github: https://github.com/VisualCodeBase/CodeBase
whats_up is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:07 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.