Mute/Quantize Script

gpoorman

Hi all. I have my quantize set to "cycle" all the time and my mute mode set to "start". I want my muting to follow the quantize but I want my unmuting to always happen immediately. To that end I write a script that was working for me in build 28 appears to have stopped in the latest build. The script looks like:

if inMute
set quantize off
mute
set quantize cycle
else
mute
endif

What happens is that the script correctly turns the quantize off when it goes to unmute but then the quantize stays off until I to a global reset. I know there've been some changes so I likely just have some reading to do but wondered if anyone sees a glaring error in what I'm trying to do.

alexs1

Hey @gpoorman ,

To my understanding, the older MOS script language is getting phased out for the newer MSL, which is still in development and in the process of being documented by Jeff, last I heard.

Good news is it doesn't look too hard to convert this script to MSL. Here's a crack at it that might work in the latest build (it at least compiles successfully in the editor):

if mode == "mute"
quantize = "off"
Mute
quantize = "cycle"
else
Mute

gpoorman

Thanks! I'll give that a try. I tried just copying that into an "msl" file (text file) but Mobius errored out when I tried to import it. Clearly this is a sign that I need to stop for a moment and catch up on the new scripting language and how to use it ;-)

alexs1

gpoorman

Hm, maybe give it a name in the first line?

#name Mute Quantize Script

Also, you might have better luck creating the script from directly inside the editor rather than importing from notepad.

gpoorman

Ok I'm all set! Thanks! So I was able to get the script in place using the new editor (which is awesome BTW). As you typed it above, the script didn't work and was behaving really odd. Then I realized that, like other programming languages, multiple statements need to be enclosed in curly braces. So just writing it as shown below did the trick.

if mode == "mute"
{
quantize = "off"
Mute
quantize = "cycle"
}
else
Mute

alexs1

gpoorman

nice! that makes total sense. I remember Jeff mentioned that you could use curly braces for multiple functions.

gpoorman

Yep. Now the only question for Jeff is ... will the language have local variables? Could I write a script that saves off the current quantize value and restores it so that I'm not hard coding it to "cycle"? Honestly I pretty much leave it on cycle all the time but the developer in me gets nitpickey wants to make it work for all cases.

jeff

gpoorman

Yes, MSL has local variables.

variable saveQuant = quantize
quantize = "cycle"
Mute
quantize = saveQuant

This little dance happens a lot and one of things on the list is something makes this temporary value override automatic. It's somewhat like what other languages call "dynamic binding". I've done some experimentation with that but it isn't ready yet. It would look similar to this:

with quantize = cycle {...do something...}

The things that happen between the braces will see quantize set to cycle, but once that ends, quantize reverts back to what it had originally.