Currently Being ModeratedNov 26, 2013 4:24 AM (in response to CommanderCool)
If your MacBook doesn't have an SSD but a regular hard disk, the problem could very well be related to physical vibration / loudness. The MacBook does have a "sudden motion sensor" which is intended to detect if the device is accellerating suddenly (as in falling), so it can park the drive's read/write head before it hits the ground.
It is a known issue, that this sensor can also be triggered by the kind of vibrations which can occur on a loud stage. This would explain why you can't replicate the problem in your studio. It also would explain why it happened during a song which featured loud drums and bass.
There is a way to disable the sudden motion sensor via the terminal. You might want to read this:
Hope this helps.
Currently Being ModeratedNov 26, 2013 8:13 AM (in response to cronbg)
Hi thanks for this, it sounds like its definitey worth me turning this off for gigs. However I'm not sure that it explains the strange warped sound that I experienced... My gut feeling is that this is something else, and that if it was the sudden motion sensor it would be a stop/start sound rather than a warped slow down/speed up effect (which I've never experienced before).
Also, the time that I mentioned an hour prior to the gig when this happened, I was in my studio and definitely didin't have any loud bass & drums happening. I'm pretty sure I was playing things heaps softer than I do at other times without this weird result....
Currently Being ModeratedNov 26, 2013 6:53 PM (in response to CommanderCool)
Has anyone had experience with the sudden motion sensor causing sample playback and instruments to warp and slow down? I remember now that the first time it happened I was playing samples and the arturia ProhetV, and the sounds from both of these instruments were being warped, the soft synth as well as the samples.....
Currently Being ModeratedNov 27, 2013 2:46 AM (in response to CommanderCool)
I have not, but I can give you some advice based on testing that made me a nervous wreck.
Put your samples on a dedicated partition, or find a utility program that rearranges your hard drive's actual files into consecutive strips on the media. This is the equivalent of "defrag" and many people HATE the mention of it. However, I can tell you that no only did my session loads "feel" faster, it shaved a WHOE TWELVE SECONDS of the boot time of my MBP.
Turn off wifi. Turn off time machine, turn for EVERYTHING you aren't using. Learn how to use Activity Monitor. KILL processes that aren't required. Go to your user' slogan items, delete iTunes helper. DELETE EVERYTHING!
In fact, for playing live, I have an entirely separate boot partition of OSX that has NOTHING installed except my performance software. No printer drivers (my awesome canon multi has software that CONSTANTLY runs). NOTHING but the essentials of what I'm doing on that stage. You can just open your projects from the drive that you built them while using--the user account where you also use safari and whatever else you like to do.
I would be loathe to tell you that you should switch to ESX sampler sounds, because you built your performance with a specific sound and you shouldn't have to change it!!
However, why do you have that esoteric synth loaded that you said you didn't play? Do you have multiple setups you load/change out during a set?
It may be my paranoia, but I always feel like a rig that just loaded is MORE RELIABLE right now, than a rig I loaded six hours ago. I'd load initial during sound check, and then I swap on the fly.
Your post described my WORST NIGHTMARE, and may keep me up tonight. But I hope my ideas give you ideas that lead to confidence.
One last bit--start transitioning to Mavericks, Mac OS 10.9. It has features that kill background processes to save energy--but they do so by managing CPU use to give you more juice all around. And when you are load testing, even in ML 10.8, it is useless to open apps and let them sit. Try playing while FCP is RENDERING A VIDEO, or injesting from FireWire. At least make the apps work!
Currently Being ModeratedNov 27, 2013 7:51 PM (in response to Landrix)
Lots of good optimisation suggestions there thanks. I'll be doing all of those and more.
It occured to me today that my issue might have something to do with some sort of a sample rate conflict?
I didn't consider sample rate compatability when I was bouncing my audio samples out of logic, and bounced them at 48kHz (24Bit). I've now checked Mainstages Sample rate and found that its set to 44.1kHz.
Could this be a problem? For the most part they were playing fine so its not like in logic where any audio files that are at a different sample rate to the session are played back at the wrong speed... I'm assuming Mainstage (or kontakt?) has a some a way of matching sample rates on the fly. But perhaps it was getting confused and switching back and forth between 44.1 and 48khz and that was what was causing the slow down speed up issue??
Also I also noticed after going through all of my samples that there were 2 audio files that I'd accidently bounced as 44.1 (although they weren't on a song that encountered this problem), maybe this created further cunfusion?
I'll be changing all of my audio files to 44.1 regardless as I've also just read that 48kHz samples use more CPU, but it would be great to know for sure if this is the problem....
Sounds like the most likely candidate so far.....
Next gig is in a little over 24hrs so I'd greatly appreciate any feedback! Thanks!
Currently Being ModeratedNov 28, 2013 12:38 AM (in response to CommanderCool)
OK, I've managed to recreate the problem after about 4 hrs of playing through songs and mucking around. I now think its to do with My CPU heating up or bad memory or buffer settings...
Heres what I've established:
Once a song/patch starts to glitch it gradually gets worse until its pretty much just garbled static, and then it stays like that until I reset things somehow. I have a plugin for logic called "buffer overide", and this noise sounds a lot like that....
Strangely, if I switch to another song in the same mainstage session, that song is fine but then switching back to the effected song, its still garbled.
The fan on my computer goes on full bore when this is happening.
The first thing I tried was changing the sample rate setting to 48kHz which fixed it and then back to 44.1. Both fine for a while but I think thats because when you click Apply changes it reloads everything.
My activity monitor is looking pretty extreme (although I'm not an expert on reading this)... I'm guessing that CPU usage at 630% is a lot right?
Here is a pic of the 2 instances of Kontakt in the effected song. You can see that on the "piano in blue" instrument the CPU meter is maxed (and stays that way) and when I trigger a sound the (word) disk in the disk meter flashes which apparently means something to do with the "preload buffer".
I've done an OSX "hardware test" which came back fine.....
Currently Being ModeratedNov 28, 2013 12:41 AM (in response to CommanderCool)
My Preference settings for mianstage are as follows:
I/O Buffer: 128
Driver latency: 128 samples
CPU usage: 8cores
Currently Being ModeratedNov 29, 2013 5:27 PM (in response to CommanderCool)
One of your screen shots shows that you only have 137MB of free memory... that's tight with (presumably) all those samples flying around. Made me think about Kontakt memory management, which brings up this page: http://www.native-instruments.com/knowledge/questions/56/Optimizing+the+performa nce+of+KONTAKT+5
Might be worth checking out the advise on there.
Currently Being ModeratedNov 29, 2013 11:13 PM (in response to CommanderCool)
Wow. Congrats on doing your due diligence, but wow that is a world of strain.
It will depend on your audio interface, and to you ears, but from what I see, you have a couple options here.
I wasn't keen on the bitrate mismatch being the issue, and since it was holidays here I held back on responding. I say that, because regardless of the bitrate of the instrument's samples, everything gets mathematically mixed up again to create the final product. Plugs are made to fix this on the fly, and the engine ( logic ) forces everything to play nice. What you've got is technically a dropout style glitch due to CPU loading, and the fact that the other instruments and presets are able to keep going is both remarkable and gives you some play options if this patch fails, and it also demonstrates just now power hungry this particular setup is.
Option one: I don't recall if this is a Kontakt library patch, but almost all NI patches come with multiple versions (small medium large) that exist for flexibility and usability in systems where you don't just need that one thing running but also other instruments and effects (small and medium) and the large instrument sets are for when NOTHING else is running and for maximum fidelity for mix down or track freeze only. If you have the option, you really need to load the lighter version.
Honestly, with numbers like these, I'm absolutely shocked that you didn't get sudden silence, and that the rig continued to make sound at all. Earlier versions of this software don't fare so well.
Option two: I don't know this to really solve your particular issue, but it's worth a shot. Your mate above mentioned the Kontakt settings. There are specific settings in Kontakt itself for sample preload, CPU and memory footprint characteristics. These appear in the plug-in as well as the standalone, accessible in the setup pane. Fiddle with them in an effort to limit CPU max load to somewhere in the 90s, because mainstage can use the overhead.
Option three: this involves a bit of two, but consider divorcing Kontakt from the host entirely. If you truly cannot reduce the demands of that specific piano in blue patch by choosing a lighter sample set, this may be your only hope to salvage that patch. I don't know if resources allow it but you could run Kontakt on another machine if you have to, and I'm afraid something has to give. If you can't access the limiting settings within the. Kontakt plugin, you could run it separately. And one last thing, I know it's great to play all this live, but if you are dead set on this sound, you can mix it down to an audio track .wav or .aiff and trigger it. I know it' snot glamorous, and you may feel like a tool miming along, but don't tell anyone. And for that matter, don't tell them I told you to do it! :P
Hope this continues to give you ideas. Keep it up...you're going great!
Currently Being ModeratedNov 30, 2013 9:51 AM (in response to Landrix)
And... look at all the instances, treads and memory used by that Chrome helper process. I understand that you may have Chrome launched to be making these posts, but if all those are running even when Chrome isn't launched it might be worth killing them just to clean things up.
Currently Being ModeratedDec 1, 2013 1:03 PM (in response to aerol)
It might be also worth finding out what "memtest" is, because it uses one full core of the CPU.
Currently Being ModeratedDec 3, 2013 10:29 AM (in response to CommanderCool)
All these suggestions are good, but I'm going to suggest something entirely different on top of this that needs to be said: have a plan for what to do when things go wrong, and accept the fact that someday, sometime things will. Guitar strings break, drum sticks snap, and computers crash, it's just one of those things. It's great when musicians can work together well enough that they can instantly change their parts to fill other rolls or improvise a bit to compansate for equipment failiour. I know it's not a nice thing to say, but it does happen and it will happen. The only absolutely 100% fix for this is to be able to cover for it when it does.
Maybe it even involves turning it into a joke for the audience... a technical bobble can make for a great stage joke and get the audience laughing more than they ever would. I recently watched a Devin Townsend video in which he screwed up a tune, and then went on to highlite and lampoon himself doing it and talk about what was going through his head at the time, and you can just hear the audience doubled over laughing.
Turn the accident into an unforgetable magical moment if you can, either have the band create an interesting new "sans-keyboard" arrangement on the fly, or get your audience involved. Being a truly great performer isn't just about perfection, it's about how to deal with the unexpected.