Wasn't Akai too busy selling MPCs, portable recorders, rack mount samplers, etc?ekwipt wrote:RENs OS might be 1.0 but they've had 20+ years to get this shit right on release
This is what I'm waiting on, a dedicated controller for Geist. Ren, Maschine, Drum Racks have nothing on Geist as a software drum sampler. Well, except for the controllers.yur2die4 wrote:If only they could cut a deal with fxpansion haha
These things really suck. I don't like to have to even look at the screen/software/etc.humnumb wrote: - 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 basic things like loading samples/files (source: Jahrome)
So if you're editing something that involves the MPC on a plane... you have to get the giant MPC out? What? This I did not know at the time, but it seems like a big limitation ONLY because of how big the controller is.humnumb wrote: - no 64bit support (source: Jahrome)
- no RTAS support (for anyone using Pro Tools) (source: Dan Gill, Akai)
- it doesn't receive MIDI clock or MTC in standalone mode(source: Jahrome)
- 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)
This means that the workflow/APC integration/etc I linked to in my post above is not particularly useful for the MPC.humnumb wrote:
- 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)
Just like the features that require a mouse, this slows one down a lot.humnumb wrote:
- 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. Maschine's way doesn't interrupt the workflow because it doesn't prompt you to save as new or overwrite the original in the process, and it's easy to undo. (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)
If you've made the investment in Ultimate, then you'll miss this a lot.humnumb wrote:
- 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)
- there's a growing list of bugs that the beta testers missed. Simplest things makes it crash (Copying sequences, Clearing programs, Duplicating Inst Program...etc.)
and other bugs like notes getting stuck, screen problems...etc.
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."
ttilberg wrote: "Hey, Live isn't just for DJs checkin' their email, or Expiremental Dave at the astronomy theater."
passionate but unlikely, unless you're name is propeller head you're not releasing any software without bugs, not even Reason is without bugs on release…. and incase anyone didn't know, coding apps has changed allot in the last 20 years as well.ekwipt wrote:RENs OS might be 1.0 but they've had 20+ years to get this shit right on release
all this stuff will change it's only 1.0 and the ren is the largest flagship controller, it's the mpc studio that is what you should be comparing to the maschine, and the mpc studio won't be out until mid or the end of october, and it's formfactor is smaller than that of maschines so you'll be okay on your Aero-Plane while making your cloud rocking beats lolbotstein wrote:These things really suck. I don't like to have to even look at the screen/software/etc.humnumb wrote: - 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 basic things like loading samples/files (source: Jahrome)
So if you're editing something that involves the MPC on a plane... you have to get the giant MPC out? What? This I did not know at the time, but it seems like a big limitation ONLY because of how big the controller is.humnumb wrote: - no 64bit support (source: Jahrome)
- no RTAS support (for anyone using Pro Tools) (source: Dan Gill, Akai)
- it doesn't receive MIDI clock or MTC in standalone mode(source: Jahrome)
- 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)
This means that the workflow/APC integration/etc I linked to in my post above is not particularly useful for the MPC.humnumb wrote:
- 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)
Just like the features that require a mouse, this slows one down a lot.humnumb wrote:
- 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. Maschine's way doesn't interrupt the workflow because it doesn't prompt you to save as new or overwrite the original in the process, and it's easy to undo. (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)
If you've made the investment in Ultimate, then you'll miss this a lot.humnumb wrote:
- 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)
- there's a growing list of bugs that the beta testers missed. Simplest things makes it crash (Copying sequences, Clearing programs, Duplicating Inst Program...etc.)
and other bugs like notes getting stuck, screen problems...etc.
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."
Thanks for posting all these!
what a fucking joke. but I'm a samplist samplist so I gets down with it anyway, I use my maschines purely for sound design at this point.
you know me I'm all about equality, there are allot of short term memories dancing about, not remembering Native instruments actually making it's 1.0 release so bad that they had to take out some features all together that they had put in at first, now keep in mind that the 1.0 release of maschine was the most featureless os release of any drumsampler in history, even ipad drumsamplers have more on their 1.0 releases so its not like maschines 1.0 release was so bursting at the seams that they just made a few mistakes and couldn't get it together, it was already a skeleton to begin with but still they fudged up some features so bad that they had to remove them, not fix them but take them out completely not to be seen again until 3 years later, and that's not even all of them yet that they had taken out back then….. they boxed and released the units this way so anybody with amnesia can say what they want, and if you say you don't want to do research and learn about the instruments you're purchasing that's fine too I mean you gotta be you right, but don't act like maschine has some kind of high horse to look down from……. talk about etcha sketch moments hahabeats me wrote:@starv stu
If I have to admit that Apple fucked up the iPhone 5 and iOS 6 then you can admit that Akai, your Apple, fucked this one up big time too.
We can cry together for different reasons.
i know you weren't being serious but if you were you'd a said the only feature akai copied was vst integration, and then you would've said but ni didn't invent vst usage so akai didn't copy that from them, the rest of the features almost all come from prior mpcs, as do all of the feature request over at NI…… those feature request come from people who've used mpcs and are wondering where those features are.arctic ranger wrote:akai devs....how are we gunna make ren better than machine?
well we could go to machines website and copy all their features and whatever the longtime users are asking for....get in touch and really make it a dealbreaker
wait what?