By emptysea
Sat Sep 22, 2012 6:19 pm
This thread is specifically about sharing the limitations of the "MPC" Ren in comparison to Maschine, without sales pitches from people who stand to profit from them being sold, like MIDIchlorian who sells samples and tutorials for MPCs, or xparis001/Andy Mac who are employees of Akai, or collector fanatics like Jahrome who has affiliations with Akai.
Note: None of these are bugs. There's already a long bug report thread in this forum (including the most basic of tasks like copying sequences/undo after sample editing causing crashes). All these issues are currently by design.
- the Ren still requires you to use the mouse for a lot of things. You can't even nudge notes from the Ren controller (source: Jahrome) and you can't open/close instrument plugin windows from the Ren controller (source: Pete blues, Akai)
- you have to stop the Ren's sequencer to do things like loading samples/files (source: Jahrome)
- no 64bit support (source: Jahrome)
- it doesn't receive MIDI clock or MTC in standalone mode(source: Jahrome)
- no RTAS support (for anyone using Pro Tools) (source: Dan Gill, Akai)
- Ren doesn't have independent swing (Maschine has it per sound/group/master) and it doesn't work in realtime (source: Dan Gill, Akai)
- you can't manually add/remove slices (source: IMAKEMADBEATS)
- Ren's software will not run without the Ren controller being attached (source: Dan Gill, Akai)
- the Renaissance controller is not usb bus-powered and requires an ac adapter (source: Bremen)
- the Ren doesn't have a fast pad duplicate feature like Maschine and even if you copy samples to different pads in the Ren, editing a pad will affect all pads instead of each pad having its own setting like Maschine (source: LMSW, Blue Haze)
- copying sequences eats up memory when you're using plugins on the Ren's software. Only the sample kits qualify as programs that can be shared across sequences. That means a few instances of a heavy plugin will peak your CPU. (source: Jahrome)
- Ren doesn't even output MIDI as a plugin (source: bobbybland)
- Ren can't even export a program out to separate sounds. You can't get anything other then a single wave file for an entire sequence and .pgm. Ren forces you to manually copy and paste separate tracks for each drum hit that you want separate, which is extremely tedious and a complete workflow killer. (source: bobbybland)
- using Ren's timestretch and pitchshift overwrites the original sample without giving you an option (source: MIDIchlorian)
- editing multiple pads on Maschine is much quicker. When editing multiple samples on different pads on Maschine, as soon as you hit the pad it pulls up the sample on screen ready to be edited. On the Ren, if you want to switch to another sample to edit.. you have to scroll to it, which is a workflow killer. (source: KnockSquared)
- it's hard to do anything but the most basic functions with the Ren controller's built in screen alone. You can do just about anything on Maschine's hardware with my laptop closed. (source: Bremen)
- And even with all that clicking around on the computer screen required on the Ren, it can't even highlight and drag more than one sample at a time. (source: SquareBanger)
- the Ren's sequencer stops every time you simply drag a sample from the browser to a pad (source: Jahrome)
- you can't drag and drop to bounce/export. (source: bobbybland)
- it doesn't even support all of Akai's own legacy MPC file formats (doesn't read .ALL or .APS and ignores things like "Effects, Q Link slider events, Mute groups/mute targets, velocity sensitive parameters (V > Att etc), LFO, sequence track assignments, song files, any JJOSXL specific feature (e.g. NDC related data etc") (source: MPC-Tutor)
and it obviously doesn't have Komplete 8 integration that Maschine has where all presets from Komplete 8 can be browsed and loaded just from the hardware.
Note: None of these are bugs. There's already a long bug report thread in this forum (including the most basic of tasks like copying sequences/undo after sample editing causing crashes). All these issues are currently by design.
- the Ren still requires you to use the mouse for a lot of things. You can't even nudge notes from the Ren controller (source: Jahrome) and you can't open/close instrument plugin windows from the Ren controller (source: Pete blues, Akai)
- you have to stop the Ren's sequencer to do things like loading samples/files (source: Jahrome)
- no 64bit support (source: Jahrome)
- it doesn't receive MIDI clock or MTC in standalone mode(source: Jahrome)
- no RTAS support (for anyone using Pro Tools) (source: Dan Gill, Akai)
- Ren doesn't have independent swing (Maschine has it per sound/group/master) and it doesn't work in realtime (source: Dan Gill, Akai)
- you can't manually add/remove slices (source: IMAKEMADBEATS)
- Ren's software will not run without the Ren controller being attached (source: Dan Gill, Akai)
- the Renaissance controller is not usb bus-powered and requires an ac adapter (source: Bremen)
- the Ren doesn't have a fast pad duplicate feature like Maschine and even if you copy samples to different pads in the Ren, editing a pad will affect all pads instead of each pad having its own setting like Maschine (source: LMSW, Blue Haze)
- copying sequences eats up memory when you're using plugins on the Ren's software. Only the sample kits qualify as programs that can be shared across sequences. That means a few instances of a heavy plugin will peak your CPU. (source: Jahrome)
- Ren doesn't even output MIDI as a plugin (source: bobbybland)
- Ren can't even export a program out to separate sounds. You can't get anything other then a single wave file for an entire sequence and .pgm. Ren forces you to manually copy and paste separate tracks for each drum hit that you want separate, which is extremely tedious and a complete workflow killer. (source: bobbybland)
- using Ren's timestretch and pitchshift overwrites the original sample without giving you an option (source: MIDIchlorian)
- editing multiple pads on Maschine is much quicker. When editing multiple samples on different pads on Maschine, as soon as you hit the pad it pulls up the sample on screen ready to be edited. On the Ren, if you want to switch to another sample to edit.. you have to scroll to it, which is a workflow killer. (source: KnockSquared)
- it's hard to do anything but the most basic functions with the Ren controller's built in screen alone. You can do just about anything on Maschine's hardware with my laptop closed. (source: Bremen)
- And even with all that clicking around on the computer screen required on the Ren, it can't even highlight and drag more than one sample at a time. (source: SquareBanger)
- the Ren's sequencer stops every time you simply drag a sample from the browser to a pad (source: Jahrome)
- you can't drag and drop to bounce/export. (source: bobbybland)
- it doesn't even support all of Akai's own legacy MPC file formats (doesn't read .ALL or .APS and ignores things like "Effects, Q Link slider events, Mute groups/mute targets, velocity sensitive parameters (V > Att etc), LFO, sequence track assignments, song files, any JJOSXL specific feature (e.g. NDC related data etc") (source: MPC-Tutor)
and it obviously doesn't have Komplete 8 integration that Maschine has where all presets from Komplete 8 can be browsed and loaded just from the hardware.
Last edited by emptysea on Sun Sep 23, 2012 9:01 pm, edited 1 time in total.









