2710 Views 5 Replies Latest reply: Mar 17, 2011 2:33 AM by michaelhuisman
Currently Being ModeratedMar 12, 2011 9:17 AM (in response to NMcQ)Hi Neil
Really, Mainstage IS stable assuming you have RAM and a strong processor.
I've been touring with a MS only setup running loads of Omnispheres, Kontakts as well as Logic instruments and Ivory, and never had a glitch, except for a sustain pedal issue that what caused by a master kbd/pedal association problem. I must say with were not changing a lot of parameters, just expression pedals (mapped) and at that time Ivory was at Set level to avoid redundancy, (that was Mainstage 1, with no "paste as clone" function).
I just splitted the show in 2 to make sure I would have enough headroom on the processor.
We made it on Mac Pros, Nehalem first gen, which seemed little bit touchy at the beginning, since some songs were to be played in front of stadium audiences, with Ivory solo piano parts topped with up to 3 omnispheres and 2 Symphobia patches. In these particular songs, we initially planned to have a spare Mac ready for quick switching in case of disaster, but it was so rieliable that we decided mid-tour to use one computer for part 1 of the show and the second for part 2, thus avoiding the need to load half-way.
Having used Logic in the pre-MS ages has a virtual rack using some environment, which worked quite OK, I think multi-core action will be from far better handled in MS: Logic need to run to correctly use multi-core. If you use more sequences and less real time, Logic is of course a better solution. I used to MD another popular artist with time code everywhere in the show, and video-lip-sync'd. Logic was perfect and never failed, and I used another Mac for software instruments.
Hope this helps,
JLMac Pro Quad Xeon 2,8 gHz, Mac OS X (10.6.6), Logic Master Trainer - Logic Mentor Trainer Apple EMEIA
Currently Being ModeratedMar 12, 2011 12:44 PM (in response to Sarl Apaxx Designs)That's great information, a serious setup. If you did all that without backup hardware midi modules, I admire your bravery. You'd be a fabulous spokesperson for MS after all that.
My current setup is on a MacBook Pro laptop, a fairly powerful one (or was at the time), usually using Duet. So although the multiple core comments and a few others might not apply, I pull from your information that MainStage was quite solid under a pretty heavy load, in a hgih-risk environment. If you'd change any comment based on my system it would be great to know.
Did you not have ANY backup system in place for failure? Even in medium-sized gigs, I always have an A-B switch that goes immediately to a small but capable hardware midi module as backup. I'd be terrified otherwise.
I would be interested to find out if changing parameters live is the chief cause of failure, "assuming" everything else has been done right.
I "THINK", but am not sure, that most MainStage freezes happen in the editing window. I've read that the Perform window is optimized for stability more than the editing window, but that's just something I read here.
Thanks for the great info, hope to get more info on this subject from other such players.
NeilMacBookPro 3.06gHz 4GB ram, iMac 24", PowerBook G4, iMac 22", Mac OS X (10.6.1), www.Prymary.com, myspace.com/AlteredDominant, Logic 9, Digital Performer, Duet
Currently Being ModeratedMar 14, 2011 9:47 PM (in response to Sarl Apaxx Designs)i have been running mainstage here for about 1 year now . latest vers on a macbook pro with a i7 2.66 processor and 8 gigs of ram. i still find i have to run a buffer of 256!
I two use omnisphere, kontak and ivory. we have a fairly large set and use only 1 instance of each instrument per song and still find that even in 64 bit mode it will crash or not always load all the samples. nerve racking every night when half way through the set all of a sudden the patches are not loading and you have to reboot. yet when you check it and verify the system and all the samples before the show they are all working flawlessly. this computer config should be plenty for this and yet with all plugins optimized , caches cleaned ect nothing else running, it still is a game of chance as to whether or not it will make it the full show,, by the way i am very fluent on macs ,been on em since the early 90s. The load on this computer is so minimal, just patch changes and barley touching the ram.
dont, get me wrong, i switched from a motif , emulator and korg radias and a m3 hoping to just use this for touring but still have to bring my m3 as the computer just cant handle the load,..... there have been many thoughts on this problem here on the web and some great and helpfull hints or strategies from some great minds here but still i find that this is at best a chance for stage.macbook pro i7 2.66, 4gig of ram
Currently Being ModeratedMar 14, 2011 11:59 PM (in response to blaze of glory)Hey,
You're right about the buffer, I'm also use 256 samples, which is fair even for piano.
The i7 MacPro has been accused to be not so efficient on Logic, I have no experience with it and MS.
But as for reliability, almost every major act here in France uses MS, some of them I've been touring with, others building the setup, and being at the convergence of pros using it, I really do not get a negative feedback about MS. I'm talking about musicians, backliners & kbd techs, sound engineers, all people that would drop such a product if it would happen to put them in danger in a live situation.
However, I always use it on racked MacPros not laptops for big setups. On laptop, I just used it has an extension of my hardware setup, but it worked fine !
JLMP Dual Xeon QUad Core 2,8, Mac OS X (10.6.6), Logic Master Trainer
Currently Being ModeratedMar 17, 2011 2:33 AM (in response to Sarl Apaxx Designs)great thead, as this is something I'm struggling with as well. Am using Mainstage, 2 latest version, 64-bit mode. Used to use Ivory 1, but v2 isn't 64-bit, and that 32-bit audio bridge crashes - can't have that live. So... I'm using Kontakt in 64-bit mode, and streaming one of the pianos that came with Komplete 7. It's not Ivory, but it's okay. As for the pianos, it's only one instance, routed to a bus... so any patch that needs piano gets a alias copy of the Kontakt instance, routed to the bus. Additionally in that patch, there's an audio channel that picks up the audio off of that bus, and can be EQd, effected, whatever... as needed for that particular patch... this is the best memory saving option I could think of.
unibody macbook pro 17". I also have a octo Nehalem here in the studio, but in terms of MainStage performance, it's not any better than the MBP, with the exception of one thing... disk I/O. all the samples on the octo are on a RAID stripe, internal to the box. I stream samples in the live rig from an Glyph quad interface drive... over FW800, as I don't trust the eSATA connectors for live...
back to performance - Logic, for any record-enabled tracks are all tied to one core only. quad or octo, no difference, it's all coming from a single core. that core may bounce around from one core to another, which might seem as if things are multi-core, but they're not. This is a challenge to say the least...
I'm quite happy to hear that you've got Ivory running, and multiple instances of Omni going as well. I do too (substitute Kontakt for Ivory though). I've got to say though... it only went stable once I said 64-bit ONLY, 64-bit kernel, 64-bit MainStage.
I'm looking to get more out of this though, and am considering that VSL host as an intermediate stop, hoping that somehow, more cores can be available/utilized... dunno if that's going to help or not, any suggestions?
To summarize, it works. the only device I have on stage that produces sounds is MainStage - use 3 controllers live, that's it. my live sound is... better than anything I've ever used before (20 space rack full plus 4 workstations/synths). Seriously... is it as rock-solid as that? nope... good enough? yeah, but barely... sure would like more peace of mind with this setup!iPhone 3GS, 8-core MacPro, QUAD G5, 2xMBPro 17", G5x2.0, PB 17", Mac OS X (10.6.6)