Akai is really LISTENING!!

peteblues wrote:

advancedbreed wrote:Welcome! Since this is running on a computer, I am assuming that there are no limitations in terms of the number of effects inserts like you will find on the legacy standalone hardware?

There are limitations of 4 inserts per pad (we had to draw a line somewhere, in order to keep the qlink integration), but each pad can have separate inserts, so you could theoretically have 4 inserts * 128 pads + 4 inserts * 64 tracks + 8 master fx (4 inserts, 4 returns).

That's very comprehensive and more than most will ever get to fully utilise ... good looking.

@peteblues

What quality are the converters used on the REN ? are they comparable to say an Apogee Duet,RME BAbyface, Mbox 3 or......??

Retrofreak wrote:@peteblues

What quality are the converters used on the REN ? are they comparable to say an Apogee Duet,RME BAbyface, Mbox 3 or......??

I actually don't know the answer to that, as I focus on the software.

peteblues wrote:

Retrofreak wrote:@peteblues

What quality are the converters used on the REN ? are they comparable to say an Apogee Duet,RME BAbyface, Mbox 3 or......??

I actually don't know the answer to that, as I focus on the software.

Ok thanks,

Will the software be able to be controlled and mapped by other midi controllers?

As there's times i'll be on the move and would like to map my keyboard controller to software.

Welcome Pete,

Can you comment on how the software will handle effects plugins that cause latency, like PSP Vintage Warmer or a look ahead limiter like an L16 for example? Will there be at least some sort of latency monitor per pad/track so we can see if/which VST's cause delay? In Maschine for example, there is no way of knowing if a plugin is causing delay or how much the delay is. The only way you'd know is if it's enough to actually hear it. I'm not requesting delay compensation at all, but would really like to see a monitor implemented that shows plugin delay in samples and in optional milliseconds. Thanks!

Retrofreak wrote:

peteblues wrote:

Retrofreak wrote:@peteblues

What quality are the converters used on the REN ? are they comparable to say an Apogee Duet,RME BAbyface, Mbox 3 or......??

I actually don't know the answer to that, as I focus on the software.

Ok thanks,

Will the software be able to be controlled and mapped by other midi controllers?

As there's times i'll be on the move and would like to map my keyboard controller to software.

at the very least, the pads will be triggerable via external midi.

DJ Hellfire wrote:Welcome Pete,

Can you comment on how the software will handle effects plugins that cause latency, like PSP Vintage Warmer or a look ahead limiter like an L16 for example? Will there be at least some sort of latency monitor per pad/track so we can see if/which VST's cause delay? In Maschine for example, there is no way of knowing if a plugin is causing delay or how much the delay is. The only way you'd know is if it's enough to actually hear it. I'm not requesting delay compensation at all, but would really like to see a monitor implemented that shows plugin delay in samples and in optional milliseconds. Thanks!

unfortunately we won't have a latency monitor in the first version. It's a possibility for an updated version though.

Would you allow knobs and transport to be midi learnable like Motu Bpm and Geist etc?

Retrofreak wrote:Would you allow knobs and transport to be midi learnable like Motu Bpm and Geist etc?

It's not planned in the initial release, since that's what the mpc controller is for.

peteblues wrote:

Retrofreak wrote:Would you allow knobs and transport to be midi learnable like Motu Bpm and Geist etc?

It's not planned in the initial release, since that's what the mpc controller is for.

I think what Retrofreak is asking is whether the new controllers will work with software other than the bundled software by utilizing midi learn. Maschine allows it, even other controllers from Akai such as the MPD32 allow it. After all it is a midi controller, right? It would be crazy for Akai to prevent it from being able to utilize midi learn or work with the software we have already purchased and use daily.

peteblues wrote:

Retrofreak wrote:Would you allow knobs and transport to be midi learnable like Motu Bpm and Geist etc?

It's not planned in the initial release, since that's what the mpc controller is for.

I can see myself leaving the REN in my studio and attaching a portable midi keyboard with knobs, pads and a transport when traveling.

It would be nice if the software could respond to Midi CC data from other controllers (even if other functions are crippled or reserved for the MPC Ren).

Will I be able to use a legacy MPC as a basic controller for the Ren Software?

coolderb wrote:

peteblues wrote:

Retrofreak wrote:Would you allow knobs and transport to be midi learnable like Motu Bpm and Geist etc?

It's not planned in the initial release, since that's what the mpc controller is for.

I think what Retrofreak is asking is whether the new controllers will work with software other than the bundled software by utilizing midi learn. Maschine allows it, even other controllers from Akai such as the MPD32 allow it. After all it is a midi controller, right? It would be crazy for Akai to prevent it from being able to utilize midi learn or work with the software we have already purchased and use daily.

oh, I misunderstood. Yes, it can be used as a controller.

It seems like there are two feature requests here:

1. Use the actual MPC Ren/Studio controller as a Super MPD so you can use it with other software.

2. Used 3rd party controllers to control the MPC Ren/Studio software.

I like #1 although I can just use the 3rd party software as a plugin within MPC Ren/Studio...and Map BPM/Geist paramters to the Qlinks.

My mistake, I just read Retrofreak's update. He is asking if the reverse is true. Can the REN/Studio software be used with other midi devices?