UI bug on audio input port / audio output port

TWMM

I can change input port / output port via scripts, but when attempting to do so vie mouse in "instant paramters" it only lets me select I/O 1 or 2, nothing larger.

Think i mentioned this a long time ago but just reposting.

Leftyloopy

TWMM checking if you could help with outputs. In mobius 2.5 i have a couple of scripts to assign tracks (groups, in my case) to different output ports. But I can't manage to make them work at all. Just started doing the switch, I'm at a lost. Tried doing any sort of ouput port change even in .msl but no luck. Could you help with the syntaxis you used?
I'd appreciate it!

Howldin

Interesting. This strikes me as another pointer to there being some thing (s) awry with how Mobius ports are set up and reported to hosts.

TWMM

Howldin but in my experience this is just a UI bug, i can set the input/output accordingly via scripts.

One thing i noticed, in Mobius 2.5 all device I/O were activated so the port names matched the device, but now if you dont have all the input ports activaterd, say channels 1-8 and not activated, then mobius inputport 1 is actually input 9 on your device.

jeff

Regarding the last comment, yes that's a side effect of how Juce interacts with the audio device. That little UI widget you see in the Audio Devices panel is actually something Juce provides for device configuration. I don't have much control over that, I could write my own I suppose, and may someday, but for now I'm saving some time and using the Juce configuration UI. You have to check every channel pair you want to use, and the order of those checkboxes from top to bottom determines what Mobius port numbers are.

TWMM

jeff no worries about the juice / audio device interaction, no fix needed imho, just thought it was worth mentioning incase anyone is having trouble syncing there I/O ports between the device & Mobius

jeff

The inability change port numbers using mouse drag in the Instant Parameters is indeed a UI thing, it should be an easy fix.

jeff

Sorry for the delay. If you're still working on this, post a brief description of what you need the script to do.

When discussing output ports, there are several complications beyond scripting, there is also routing configuration in the host to make those ports do something which is a different can of worms. The number of output ports that are available is also configured within Mobius so you need to do that first. The script can assign a track to use port 6 but if port 6 is not enabled, then it will go nowhere.

For just the script part, the way you would change a port is like this:

// change the port in whatever track the script is running in
outputPort = 2

// change the port in only track number 4
in 4 outputPort  = 2

// change the port in all tracks that are in the group named "mygroup"
in mygroup outputPort = 2

The number of ports you can actually use is configured in two ways, depending on whether you are using the plugin or running standalone. If you are using the plugin, from the Configuration menu select System Configuration and click the Plugin tab. The two fields will say how many ports the plugin should have. So if the value of Plugin Outputs is 3 then you can only use port numbers 1, 2, and 3. Attempting to use a higher port number won't work. Configuring the number of ports when running standalone is less obvious and is determined by the way you have the audio device configured in the Configuration->Audio Devices window. If that's what you're using I'll walk you through how that works.

Once you've done all that, if you're using the plugin, you still need to configure the host to route the Mobius ports to channels in the audio interface. That's a much more complex topic and will depend on the host you're using.

jeff

While looking at this, I noticed that it's very hard to see what ports a track is actually using if you are changing them with scripts. Normally, I would add inputPort and outputPort to the Instant Parameters list so you could see them in the parameter table in the UI, but you can't add those to the list. I'll fix that.

If you bring up the Sessions->Edit Session window and select the Ports page, you will only see the default port numbers that were saved in the session. If the port numbers were changed dynamically using a script, you would not see the active numbers.

Leftyloopy

Thanks for the response. I am actually lost here. Down I'll paste what the script did in mobius 2.5:

`
!name Toggle output 3

if outputport = 0

set outputport 2

message Output to Mixer

else

set outputport 0

message Output to Mobius Master

endif
`

I would assign the scope on the midi binding to group A, or group B, and whichever tracks I had already set by another binding to said group, would change it's output. and if I pressed it again, it woould toggle back to the main output. I do remember, as you can see, that the output ports started in 0, whereas in track setups they would start in 1. But once I figured that out, it was all good.

Now the problems that I am having is that I just tried these options that you wrote bound to a button, just for easyness of it, but I can't change the output whatsoever. I should state that I never ran Mobius as a plugin, it's always been standalone.

Now, the other problem that I have is I haven't been able to run any script in Mobius 3 (.all mos) when trying to bind them to a group. They work just fine when they are bound to specific tracks, but not groups. Which is weird becuase I HAVE been able to bind regular functions to groups. just not Scripts.

Clearly, there are lot of things that I am failing at, so, any help it's welcome ! 😅