Page 1 of 1
Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 12:50 am
by sublimation
So i've had this happen a couple of times since i started getting into producing a couple of months ago...I have massive running standalone, working on sound design and everything sounds fine (CPU is fine, nothing clipping, etc.). But then I thought of a nice synth line and wanted to get it put into live, so i opened massive in live, opened my patch and when I play any notes it just spits out this super bitcrushed sound...thats about the only way i know how to describe it.

When im playing it in live the CPU is still fine as well so i dont think its anything to do with that.
Has anyone ever encountered or heard of this before? Ive never had it happen when starting out with massive running in live so i guess thats one solution, but id still like to know whats going on here...
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 1:51 am
by dubesteppe
your massive standalone is most likely using an aiso driver. check and see if live is using the same driver.
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 3:00 am
by sublimation
Nah im just using coreaudio at the moment, but the drivers were the same on both. I'm in class right now and haven't changed any settings but i tried it out again and it's working fine (just on my laptop speakers), so maybe it has something to do with my audio setup at home? The only other time that it happened i was using headphones so maybe it has to do with using the audio line-in port (which im using for my setup at home too)...i have no idea really im just throwing ideas out there haha.
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 3:11 am
by glottis5
it's a lack of processing power/audio bandwidth, increase the size of your audio buffer or switch to asio
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 4:24 am
by sublimation
Yep that was definitely it, working smooth now.

Thanks for the help guys!
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 4:05 pm
by Killamike49
sublimation wrote:Nah im just using coreaudio at the moment, but the drivers were the same on both. I'm in class right now and haven't changed any settings but i tried it out again and it's working fine (just on my laptop speakers), so maybe it has something to do with my audio setup at home? The only other time that it happened i was using headphones so maybe it has to do with using the audio line-in port (which im using for my setup at home too)...i have no idea really im just throwing ideas out there haha.
Some laptops also super derp when you plug in headphones, because they start routing your shit through their drivers, with it's dolby surround sound, and maxx audio and shit. I forget what laptops do that, but it was a crippling problem at my friends house until i swicthed asio4all back on. (It automatically switched it to the internal card)
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Thu Feb 23, 2012 11:43 pm
by Akadia
I'm having a similar problem. When I'm playing the notes in massive they sound fine, but when I try to record them in Ableton it does that "bitcrushing" thing. How can I fix this? My driver is the default one for my laptop and I have the buffer all the way up.
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Sun Feb 26, 2012 2:44 pm
by Akadia
bump
Re: Massive 'self-bitcrushing' when opened in Live?...
Posted: Sun Feb 26, 2012 7:34 pm
by JTMMusicuk
Akadia wrote:I'm having a similar problem. When I'm playing the notes in massive they sound fine, but when I try to record them in Ableton it does that "bitcrushing" thing. How can I fix this? My driver is the default one for my laptop and I have the buffer all the way up.
have you bought massive?