
By DJ Hellfire
Mon Mar 05, 2012 4:54 pm
Everyone is talking about the fact that it's not standalone or that it should be standalone. But no one is really discussing why it's not standalone, technically speaking. I posted this in another thread, but figured I'd post it here to get some discussion going. Not discuss how you do or don't like controllers. But to discuss ways on how it could have physically/technically been able to go standalone given the features it currently offers.
STANDALONE:
Sounds good on paper, but it's easier said than done. I believe the VST functionality is the main/only thing holding it back from being that "hybrid" you all want. In order to be able to freeze VST's, it would take A LOT of ram, for one, to be able to play the files back, which hardware MPC's never had. Most likely you'd be running the VST's in at least 24-Bit, plus I run mine at 48K, which taxes the ram even more. If you have multiple large VST VI parts and multiple sequences/variations, you'd need so much RAM that you might as well have a computer. The MPC would need to have at least close to 1GB of RAM to achieve this. And given Akai's previous RAM prices, $200 for 128MB, that could be expensive, unless they fully support 3rd party RAM where you don't have to buy twice the amount just get the max the MPC can handle.
And what about your VST effects? You can't freeze those. So you'd have nice plugin effects while connected to the computer, but none during a live gig without your computer? Even if it had audio tracks and you were able to bounce, say, some eq/compressed drums to an audio track, then you couldn't do mutes on your drums because instead of one shots, your patterns would now be huge 2-4-8 bar audio file chunks. And you couldn't play your patterns live, unless you went back and rechopped everything. This is why it is not and will never be standalone.
There's no efficient way to merge VST capability with non-VST capability. Plain and simple. The Beat Thang is able to achieve this only because it only uses built-in effects, and has no VST hosting capability. The only proper way to do it right would be to make the MPC hardware able to actually run/host VST's internally. And some of these VI's are MAD GIGs worth of sound libraries. Just doesn't seem cost effective to do this efficiently. Again, like I said, you'd be looking at something more like a $5000 Meko!
The only way I see it working without going the internal VST route is if they 1) Introduced audio tracks so you can freeze VST VI's and bounce tracks with VST effects to audio. 2) Make the MPC able to playback audio from the internal hard drive like a DAW, and have the pads able to mute the tracks as they playback the same as it does one shots store in RAM. Probably will never happen! Might as well just use a computer!
Thoughts?
STANDALONE:
Sounds good on paper, but it's easier said than done. I believe the VST functionality is the main/only thing holding it back from being that "hybrid" you all want. In order to be able to freeze VST's, it would take A LOT of ram, for one, to be able to play the files back, which hardware MPC's never had. Most likely you'd be running the VST's in at least 24-Bit, plus I run mine at 48K, which taxes the ram even more. If you have multiple large VST VI parts and multiple sequences/variations, you'd need so much RAM that you might as well have a computer. The MPC would need to have at least close to 1GB of RAM to achieve this. And given Akai's previous RAM prices, $200 for 128MB, that could be expensive, unless they fully support 3rd party RAM where you don't have to buy twice the amount just get the max the MPC can handle.
And what about your VST effects? You can't freeze those. So you'd have nice plugin effects while connected to the computer, but none during a live gig without your computer? Even if it had audio tracks and you were able to bounce, say, some eq/compressed drums to an audio track, then you couldn't do mutes on your drums because instead of one shots, your patterns would now be huge 2-4-8 bar audio file chunks. And you couldn't play your patterns live, unless you went back and rechopped everything. This is why it is not and will never be standalone.
There's no efficient way to merge VST capability with non-VST capability. Plain and simple. The Beat Thang is able to achieve this only because it only uses built-in effects, and has no VST hosting capability. The only proper way to do it right would be to make the MPC hardware able to actually run/host VST's internally. And some of these VI's are MAD GIGs worth of sound libraries. Just doesn't seem cost effective to do this efficiently. Again, like I said, you'd be looking at something more like a $5000 Meko!
The only way I see it working without going the internal VST route is if they 1) Introduced audio tracks so you can freeze VST VI's and bounce tracks with VST effects to audio. 2) Make the MPC able to playback audio from the internal hard drive like a DAW, and have the pads able to mute the tracks as they playback the same as it does one shots store in RAM. Probably will never happen! Might as well just use a computer!
Thoughts?
Last edited by DJ Hellfire on Mon Mar 05, 2012 10:32 pm, edited 3 times in total.






