1.40 AU bug: Script not regognized by parmater assignment

[Per Boysen]

Hi,

The script below has served me well for more than a year, but when trigging it by AU parameter assignment (rather than key control or direct MIDI input) it doesn't run at all. May this be a temporary AU issue?

# This script needs "Track Copy = Timing"

!name Rec 4 Tracks In 1 Swoop
Message Record Four Tracks In One Swoop

if mode = reset
for 1
GeneralReset
next
for 2
GeneralReset
next
for 3
GeneralReset
next
for 4
GeneralReset
next
Track 1
Record

else
Overdub

if mode = record
set output 60
Record
Wait last
Overdub
Wait last
set altFeedback 64
NextTrack
set output 50
Overdub
Wait loop
Overdub
RateShift 12
NextTrack
set output 100
Overdub
Wait loop
Overdub
RateShift -12
NextTrack
set output 90
Overdub
Wait loop
Overdub
RateShift -5
NextTrack
endif

end

!sustain 1000

Label sustain
if sustainCount=1
Reset
endif

[buzap]

Hi Per

I believe Jeff metioned that you can only pass momentary pedals via AU/Mainstage. Have you checked if the !sustain is the problem?

best regards
Buzap

[Per Boysen]

Good points Buzrap,

The Mainstage graphic buttons are indeed set to "Momentary behaviour", so that should be correct.

!sustain does work fine through this Mainstage setup in other scripts I'm using, so I'm still clueless here.

[Per Boysen]

Just want to add some more here for the record of this "bug". I have found that a lot commands are screwed up when called by AU paramter assignment. For example: I have assigned a button in Mainstage to the parameter Multiply. When calling Multiply Mobius starts multiplying but as soon as it completes the cycle it goes "Mute". I see no reason at all why this command "Mute" should suddenly be activated. Other issues is a script that simply isn't working when called by AU parameters and Redo not working either.

I use the host Mainstage and now I'm deleting the Mainstage objects for the parameters that are not working and then I'm setting the Bus Instrument Channel Strip that hosts Mobius to receive direct MIDI Input from the physical MIDI In port - and this works like a charm! A great thing with this concept is that you can seamlessly mix direct MIDI input and AU parameter assignment.

[Jeff]

Odd that some functions don't work when assigned to Mainstage buttons.
I guess I'll look at Redo first since that's the simplest. Unless the buttons
are sending something different when you release them I don't see
why the functions would go wonky.

[Jeff]

I tested the script, Multiply, and Redo in Mainstage 1 and didn't have any problems. So this is either related to Mainstage 2 or there is something
in your configuration files causing problems.

Let' start by setting Trace Print Level to 2 in Global Parameters, then
do a Multiply from a Mainstage button and send me the trace.

Thanks,
Jeff

[Per Boysen]

I also tested with the standalone version - no Mainstage - and had the no working Redo. So, since Redo is working fine for you on OS X it seems probable the bug is in my Behringer FCB1010 pedalboard. I will check by other controllers and let you know.

Thanks for researching the issue! :-)

[michel]

I have to second that : I have also many commands that are screwed up when called by AU paramter assignment in MS2.
I may have found part of the problem - and if confirmed a bug - and it is that Mobius can still recieve some Function/Command that are assigned in its own MIDI control window while no MIDI Plugins Input Devices are enable in the MIDI Device Selection windows of Mobius.
For exemple, I have the Scripts Loop-1 assign in MS to swicth-1 (note A2 + CC21) of my FCB. But I have also Half speed command assigned to the same switch-1 (here as CC21) in the Function-MIDI control window of Mobius. Results is that the Sripts Loop-1 when invoked from MS will produce also Half speed. And again I have no MIDI Plugins Input Devices enable in the MIDI Device Selection windows of Mobius (at the most, Standalone MIDI Input devices could be enable).

Michel

P.S. Still happen in 1.41

[Per Boysen]

@michel,

This may be normal for MS2.

If you open Mobius on a Software Instrument Channel Strip as "MIDI Controlled Effect" any MIDI input to Mainstage will be passed into Mobius - if not a Screen Control Object is created (in Layout), assigned to the actual MIDI event and set to "MIDI thru: Do not pass through".

[michel]

Hi Per

This is exactly the case. I am speaking about a Screen Control Object created (in Layout), assigned to the actual MIDI event and set to "MIDI thru: Do not pass through".
So the problem I report is certainly not normal at all. Maybe you could check on your own setup as you have been using both Direct MIdI input and MS layout to control Mobius. You may be have some commands in "double"....

Let see what say Jeff about that issue that can make messy results in MS

Michel

[Per Boysen]

Hi,

I'm not having this problem any more :)

This may be due to version 1.41 but probably has more to do with a mistake of mine, that I just discovered. I had two MIDI pedalboard buttons sending the same note while the corresponding screen object buttons in Mainstage were assigned to two different commands.

Now there is no problem with host parameter assigned Mobius functions. And I still have my MIDI assignments in Mobius pref's - just not any MIDI In port open chosen from Mobius.