I'm getting crashes for sure, but only during editing, and loading and unloading (auditioning) plug-ins and their settings...frustrating, but in performance the Mainstage versions up till now have been very solid for me. I haven't performed with 2.2.1 yet. (of course it just came out a few days ago)
The main reproducable bug for me is that it freezes when I try to edit a parameter curve or slope for a controller. Frustrating, as right now I have to live with them they way they are, I can't edit them. I've reported the bug and hope it gets fixed soon.
I do get some random quits, but usually while loading/changing large Native Instruments plug-ins....
If you are seeing problems with random quits when loading/changing large Native Instruments plug-ins, then you might be running out of memory. If the NI plugins you are using are available as 64-bit AUs, then you might want to try running MainStage as a 64-bit app rather than 32-bit which should fix the issue.
i'm getting some crashes.
I'm using kirnu to supply the lack of a arpeggiator. But to run kirnu, I need to create a input (another keyboard on the screen), put the input 'from kirnu' on that keyboard and assign this entry in my desired audio unit.
I'm receiving objc_msgSend() selector name: _removeAllCellMouseTracking too. And errors on com.apple.mainstage.workspace.draw.
ON a wild guess: My arpeggiator is generating a lot of notes and the midi input graphical interface (the keyboard) is stressing the system. Maybe Mainstage should allow a virtual input without the need to put a keyboard on the screen.
Maybe Mainstage should allow a virtual input without the need to put a keyboard on the screen.
Mainstage does allow this:
For a basic "all MIDI goes to everything" setup, just delete the Keyboard Screen Control.
If your issues is simply graphic-related, you could try using Activity Monitors instead of Keyboard controls.
Finally, the new "Assignments and Mappings" pane in Edit mode allows you to route/block and map incoming MIDI without the need for any Screen Controls at all.
I will try a MIDI Activitity Control instead of a Keyboard. Looks that there's no way to add a hardware input (the one that receives mdi notes and has a velocity sensitivity level) from a specific midi input (not a generic 'All') without having to add it to interface... Or i'm totally dumb
In the assign and map I can't create a notes assignment.