Xenophile Posted January 24, 2016 Share Posted January 24, 2016 Not a good first impression. On patches in an existing Concert, external instruments don't work. No midi at all is sent to the external instrument. If I create a new external instrument, it works. All my screen control mappings to Panorama P6 are gone. None of the controls are mapped. Buttons don't light. Keyboard input works, but that is all. I didn't even take the time to see if I could re-map the P6 controls. I have too much time invested in getting everything set up the way I want it to start all over again. I used Time Machine to go back to Mainstage 3.2.2 after only a half hour with the update. Color me disappointed. Link to comment Share on other sites More sharing options...
DolmensDude Posted January 24, 2016 Share Posted January 24, 2016 Yeah... HATING that Panorama/MainStage integration broke with this update. Logic integration still seems to function but I've not tried much. This is about my live rig and MainStage, which just broke with this update. I've messaged Nektar on their FB page - assuming everyone is at NAMM though... They're going to have to update how they integrate Panorama into MainStage - which apparently looks like it could break every time Apple updates MainStage (or at the least updates the files Nectar "patches" so that the P6 understands what's going on with MainStage). I think they're going to have to re-think this. Class compliant MIDI device, and patching MainStage files versus having a specific MIDI driver for their device, because my Korg NanoKontrol still works after every update, including this one... or insure that Apple goes "lock step with them" on updates so they both stay in sync with each other. Reinstalling the MainStage integration patches via the installer, followed by a reboot of the Mac does not help. Disappointed? That's putting it mildly... "uuuuuugly..." comes to mind... Want to applaud the attempt though... Link to comment Share on other sites More sharing options...
TChandler Posted January 28, 2016 Share Posted January 28, 2016 Hi there, Just to say, I've seen the Nektar integration issues and we are on this. Update coming soon. Best Regards, Tim Link to comment Share on other sites More sharing options...
DolmensDude Posted January 28, 2016 Share Posted January 28, 2016 Have responses from Nektartech confirming the issue. Good response. Believe there needs to a short term fix and also an agree to architecture between Apple and Nektar so that one team doesn't break the other's work on a X.y.z update. Looking forward to this working again. Was able to copy a MainStage 3.2.2 .app over to the affected machines and integration came back. Alchemy had to reminded its internal library but it doesn't seem to fall over for now. Link to comment Share on other sites More sharing options...
Macnl Posted February 4, 2016 Share Posted February 4, 2016 Another BIG dissapointment.. All external instruments.. all gone.. Link to comment Share on other sites More sharing options...
Xenophile Posted February 4, 2016 Author Share Posted February 4, 2016 I got an email reply from Nektar rep Justin Sullivan saying that the fix for Panorama is in Apple's court, as it affects other controllers too. But I haven't seen any mention of problems with other controllers here or in Apple's community forum. Maybe very few people are doing the update? Link to comment Share on other sites More sharing options...
vrsound Posted February 5, 2016 Share Posted February 5, 2016 Unbelievable!! Every time I open a session I have to toggle form internal audio to the MOTU 1248 to get it to recognize the interface. Then when it does, the audio sent to various busses don't get sent properly, bus names are all messed up, and audio doesn't get sent out the proper outputs. Back to 3.1, the last stable version! Link to comment Share on other sites More sharing options...
DolmensDude Posted February 6, 2016 Share Posted February 6, 2016 I saved v3.2.3 to the desktop, then restored a v3.2.2. Exported existing concert as a set, then re-created my full layout in 3.2.3, and imported the previously exported as a set concert into 3.2.3. Of course, at that point, *lots* of things were wrong, but I went thru patch by patch and fixed all of them and for now, all seems stable using v3.2.3, with the exception of the Panorama integration, so using the P6 in internal mode. Added some new patches, a couple of which were reasonably complex, and zero problems - all good. 3 hour rehearsal of new songs and full show. This was a lot of work, and really shouldn't be necessary in a 3.x.y update, but it just feels like they're fixing some inconsistencies in how files have been being saved, and that from version to version it's turned into a bit of a mess. Link to comment Share on other sites More sharing options...
2xbasssist Posted February 29, 2016 Share Posted February 29, 2016 Hi guys, Same problem here, but nothing to do with Nektar Products. I use 2 Nord keyboards, a Roland Keyboard, plus a TC Helicon Voice processor, and after the update to 3.2.3, none of the Program Changes sent from Mainstage patches to the keyboards, are being sent. So it appears to be an Apple issue for sending external data for any midi equipment. I re-installed 3.2.2, reboot, and everything went back to normal. It is amazing how this guys release an update, without checking basic Mainstage features. I hope that 3.2.4 update will come soon. Regards, 2xbasssist Link to comment Share on other sites More sharing options...
Xenophile Posted February 29, 2016 Author Share Posted February 29, 2016 As I posted earlier, Nektar support also said the issue is on the Apple side. I would have expected a quick update if several controllers were affected... But still nothing. Meanwhile I'm still on 3.2.2. Searching for stable alternatives. Wondering what can be done with Bidule... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.