Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mainstage 3.4 alias issue (one more)

Hello Everybody,

Since i've updated mainstage, i've got an other problem with alias. The patch recorded value of button with a command on a alias channel doesn't remain after save/re-open.

Does anybody else meet the problem ?

Posted on Oct 2, 2018 12:37 AM

Similar questions

Parameter jump I am struggling to create the set up I desire in MainStage... I have a Midi controller keyboard with rotary knobs configured to INC/DEC In MainStage I have created and mapped corresponding 'round knob controls', one for each MIDI channel. They are assigned to the Volume (CC 7) with a type of "Relative (2's complement)" So when I turn the knob on my keyboard the volume of the corresponding channel in MainStage increments / decrements as I desire. So far so good. I have then created patches and in the attribute settings for each knob I have set it to "Revert to saved value" because when I switch to a patch I want the volume to start from what I've got saved but then I want to be able to control the volumes of each channel whilst I play via the keyboard knobs. Now here's my issue - as an example let's say I have a patch named A where the volume of channel 1 is saved to a value of 100 If I open this patch for the first time the volume is at 100 and if I change the volume via the keyboard I can do so - let's say I turn it right down to zero If I then open a different patch (e.g. patch B) but then return to patch A then the volume of channel 1 is set to 100 - which is what I want so good so far... However, if I now try to change the volume with the hardware knob it now jumps straight down to zero (basically it always jumps back to where I last had the volume before I left the patch - but this isn't the saved value and I don't want volumes to jump like this) Is there something I can do to get it so that I can recall a patch and then adjust the volume without the potential for it to jump to a previous position? I don't think the keyboard has any bearing on this problem - if I have 2 patches both with a volume saved at 100 and on patch 1 I increase it to 127 then on patch 2 I decrease it to 0 and then return to each of the patches they will both initially have a volume of 100 but changing the volume in patch 1 will instantly jump to 127 and on patch 2 will instantly jump to 0 - so my keyboard would not know these values. Hope this makes some sense and that somebody might be able to help me please :) Thanks
444 1
Control Center Shortcut NOT working after update My control center slide from the right top corner won’t work after update (15.6), I use this shortcut function a lot and after the update it stopped working please assist.
222 3
In FCPX 10.4 In the keyword shortcut dialog box, numbers 1 to 5 are missing? In FCPX 10.4 In the keyword shortcut dialog box, numbers 1 to 5 are missing? Has anyone experienced this?Thank You.Danny.
187 6

4 replies

Oct 4, 2018 2:59 AM in response to the_great_bounty

Hello,

I have almost the same problem. After assigning the drum machines on the drum pads on my Akai MPK249 then saving and re-open, it doesn't make a sound, only keyboards work, but not the drum pads, don't know how to fix it.(

Oct 18, 2018 7:08 PM in response to the_great_bounty

Yes. I have exactly that issue for any onscreen control mapped to a plug in parameter set to revert to the saved value. The onscreen controls changing Mainstage parameters like channel volume, send levels etc seem to work though.

Oct 26, 2018 11:17 AM in response to DenCherry

Me too, It seems like I will have to re-assign drum pads to their MIDI instrument sends after relaunching the program.

This video shows the problem https://www.youtube.com/watch?v=8FOGnJgLT0U

Nov 9, 2018 4:12 AM in response to the_great_bounty

Just update 3.4.1 ... Seems the it's fixed.

Mainstage 3.4 alias issue (one more)