scripts arguments in the binding dialog

Leftyloopy

On my forever moving towards to Mobius 3 instead of 2.5 for our weekly sessions, I am still stuck as I was last summer.
Somewhere I read Jeff saying every script needs an argument on the binding window if I am correct. I'm lost of which arguments could those be. In Mobius 2.5 there were not arguments on the binding dialog, as I can remember, can't check now because I have 2.5 on a different PC.
Any ideas, pointers?
Thanks.

jeff

Scripts don't need arguments in the binding. They can allow binding arguments if they are set up to take arguments, but most do not, especially if you're migrating older ones from 2.5.

If you do have old scripts that used arguments, I'll need to review how those worked and see if that is still supported. You might need to rewrite them in the new MSL language, but script args were very rare so I doubt that is the case.

Leftyloopy

Ok, now I understand, I think. I've found on another thread you wrote:

jeff Which functions were you trying to give arguments?

Almost none of the built-in functions use arguments, every script should though.

But clearly this is me misterpreting something that meant probably arguments inside the scripts themselves. also, I don't recall using any arguments in 2.5 either. But what it's been happening is I am having a hard time being able to execute scripts. You've had written for me in .msl one translated form .mos to change the output for tracks ( in reality in binding I would scope it to a group) and I can't make it work. Even writing very simple like:

#name output
#focused
outputPort = 2

doesn;t do anything. I am extremely confused with most sctripting, moreso in .msl, but I have several scripts that I copied and modified over the years from the old forum, we are talking more that 8 years ago, so that doesn't help.

There some old .mos scripts that stragiht shut down Mobius with no warning, so I am more than happy to get them all done in .msl, but it seems I'm struggling with scripts een working, at least when the binding should be to groups.

I'll keep eating at it these days, as in the summer I have the time I don't have during school year 😅.
Thanks for the response. I'll try to start over by working on one script at a time, and come back with more informed questions.

jeff

Okay, "should though" should have been worded "allow though".

Functions arguments are hard wired in and known. They either have optional arguments or they don't. If it is known that they don't have any, then the UI won't display an Arguments section in the binding windows.

Since scripts are user written, whether they want arguments or not is unknown. I could analyze the script contents to see how it might be using arguments, but I don't right now. It is just assumed that any script has the potential to want arguments, so the binding window should always show an Arguments field where you can type them in. If you entered something here and the script didn't actually look at those arguments nothing would happen.

It should be possible to set outputPort in a script, I don't see anything wrong with that script as written. I'll run some tests.

Leftyloopy

Ok, I have some info. After erasing all scripts, succesfully copying/adapting a unquantizedmute for groups, I went ahead and I tried again the abovewritten outputPort = 2 script.
I added a print ("output" outputPort) and in the console it tells me that it is in fact in the audioport equivalent to 3 in settings, as we established the offset between scripts and settings) and in the instant parameters it also shows me the port as 3 as wanted. But nothing is changing in the physical outputs of my interface. Weird thing is that if I open the session settings dialog and saving it WHITOUT CHANGING ANYTHING it executes the output port change as the console and instant parameter field shows me.
I tried to find if there's anywhere related to outputs that need confirmationm but to not avail.
I also looked under Sessions>Default Parameters>Audio Output Port and all those fields have a 0 in them. I tried to change to 6 (thinking as in number of outputs??) but behaviour hasn't changed, so got it back to 0.
Hope any of this helps.