10 posts
Page 1 of 1
Dear all,

I was wondering:
Is there documentation about what values are valid for Command Arguments ?

For example:
The command "Arm" is a Toggle (State) command.
I would like to make a Macro that , when executed, just always Arms a Track, so no toggle.
So: If the Track was already armed > execute macro > it stays armed.
If the Track was unarmed > execute macro > it arms it
I assume there is some value i have to put in,in the Command Arguments > State textfield,that should work for this.

Anyone knows ?

Warm Regards.
Last edited by vanhaze on Fri Apr 26, 2019 8:54 am, edited 1 time in total.

Macbook Air M1 2020, 8 gig RAM, 256 gig SSD | OSX Ventura -latest Beta | Presonus Studio 24C audio interface.
User avatar
by garyshepherd on Thu Apr 25, 2019 5:09 am
I don't fully understand how this element of the shortcuts/macros works, so some instruction of the possibilities would be helpful.

Please note that I may express opinions that are different from yours but I do not intend to cause offence.
____________
iMac 27" 3.3 GHz Intel Core i5, 32 GB Ram, Monterey 12.7, 64 bit, Studio One 6.5 Professional (always the latest) , Reason 11, Melodyne 5 Studio, Digital Performer 11.2, Korg Legacy Wavestation and M1, Arturia minimoog V, Helix Native 3.71, Bias FX 2 Elite, Superior Drummer 3, EZkeys, EZbass, Nektar Panorama T4, Motu M4, Faderport 2018, Gibson Les Paul Standard, James Tyler Variax JTV-59 and other gear.
User avatar
by vanhaze on Thu Apr 25, 2019 5:31 am
Thanks for your reply Gary !

Example:

- Open Macro Organiser.
- Click the "New" button.
- On the leftside, type "arm", in the search field.
- Click on "Arm", then on "Add" button (on the right side).
- Double click on State("")

Now you can type something in, (this is called the Command Argument).
But what exactly ?
What values are possible ?
So that's my OP question.

Warm Regards.

Macbook Air M1 2020, 8 gig RAM, 256 gig SSD | OSX Ventura -latest Beta | Presonus Studio 24C audio interface.
User avatar
by vanhaze on Fri Apr 26, 2019 9:02 am
Ok, so i solved it so it seems (and i already was guessing it was super easy and logical):

- You can put it in a 0 in the Argument field and then the command will de-activate whatever it stands for.
Example: Create a Macro which has the Command "Arm", set Argument to 0.
Outcome: when executing this Macro, selected Track(s) will always be disarmed, whatever it's Arm Status was.

- You can put it in a 1 in the Argument field and then the command will activate whatever it stands for.
Example: Create a Macro which has the Command "Arm", set Argument to 1.
Outcome: when executing this Macro, selected Track(s) will always be armed, whatever it's Arm Status was.


So this logic goes for other commands too, which are Toggles (like Mute, Solo, etc.)

Nice !

Macbook Air M1 2020, 8 gig RAM, 256 gig SSD | OSX Ventura -latest Beta | Presonus Studio 24C audio interface.
User avatar
by jazzundso on Mon Jan 24, 2022 6:46 am
An in-depth macro documentation can now be found here. We will expand this documentation over time.

https://s1toolbox.com/macrodocumentation

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate
User avatar
by robgrigg on Sat Nov 26, 2022 7:16 am
jazzundso wroteI in-depth macro documentation can now be found here. We will expand this documentation over time.

https://s1toolbox.com/macrodocumentation


In depth! my bottom!
Unless I am missing something the documentation covers a dozen or so commands. It is totally inadequate. For such and important feature, I can't believe it is so poorly documented.
User avatar
by jazzundso on Sat Nov 26, 2022 7:37 am
robgrigg wrote
jazzundso wroteI in-depth macro documentation can now be found here. We will expand this documentation over time.

https://s1toolbox.com/macrodocumentation


In depth! my bottom!
Unless I am missing something the documentation covers a dozen or so commands. It is totally inadequate. For such and important feature, I can't believe it is so poorly documented.

Sorry, I don't understand. Are you saying my documentation covers too few commands? (a dozen commands!?!)

If you're looking for a tutorial about creating macros, this video should cover everything you need to know.

phpBB [video]

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate
User avatar
by Tacman7 on Sat Nov 26, 2022 9:47 am

Forum Moderator.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Studio OnePro6 Melodyne Studio
Win10 Ryzen 5 3600 - Motu M2
Ventura Mac Mini M2 - Zen Go TB
User avatar
by Tuoni64 on Sun Nov 27, 2022 1:32 am
I think there is a gap in understanding here. The documentation provided by Lukas only covers the additional macros that front-end the s1toolbox scripting add-on.

The s1toolbox adds a single new toolbar to the S1 macros, the "Navigation Essentials" if you use the free install that Lukas very kindly provides. The scripts provide new functions that could not be created by orchestrating the standard S1 macros provided.

I think that Robb was looking for detailed documentation for the official set of S1 macros, those that are provided in the S1 product and that have grown over the years from the tools used by the beta-testing teams.

I could be wrong but that is how I read the sequence.

Cheers,
Jason.

Studio One 6 (Windows 11 22H2) | Dorico 5/ Notion 6| Focusrite 18i20 | Korg D1 | Hammond SK1 | Korg Prologue 8 | Sledge 2.0 | Maschine MK3 | Faderport 8 | X-Touch One|Self-designed Hardware Synths

https://www.yizakat.com

Friend of Bill

User avatar
by jazzundso on Sun Nov 27, 2022 4:09 am
Tuoni64 wroteI think there is a gap in understanding here. The documentation provided by Lukas only covers the additional macros that front-end the s1toolbox scripting add-on.

No, not at all. The documentation covers all (built-in) Studio One commands that have additional arguments that can be used in macros. There was a great demand for explanation of these arguments, for example the arguments of the "Create Crossfades" command which requires certain keywords as arguments. The documentation lists and explains these arguments.

It's totally independent from additional add-ons.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate

10 posts
Page 1 of 1

Who is online

Users browsing this forum: musicchamber, strumpy_strudel, Trucky, Vocalpoint and 57 guests