MPC plugin mode enhancement requests

Yeah, 32 mono I meant!

Summary so far:

* 32 stereo virtual outputs
* drag / drop midi from MPC plugin to DAW track
* enable MPC sounds to be triggered from DAW midi tracks (multi-timbral mode)
* toggle to turn off MPC sequencer (if using as a sound source, only need the DAW sequencer)
* Should allow 4 simultaneous MIDI outputs, to external MIDI devices, so that projects work with external MIDI devices in plugin mode in the same way that standalone mode does.
* Multiple instances like Maschine (and other plugins)

Anyone else?

In VST mode the DAW should be able to access parameters for fx, tempo, mixing. that way you could use tools to generate LFOs or other envelopes in your DAW

Eyalc wrote:* enable MPC sounds to be triggered from DAW midi tracks (multi-timbral mode)

This one may be tough. This sounds like it would require MPC Programs to have individual midi input capability.

DJ Hellfire wrote:

Eyalc wrote:* enable MPC sounds to be triggered from DAW midi tracks (multi-timbral mode)

This one may be tough. This sounds like it would require MPC Programs to have individual midi input capability.

The MPC tracks would have individual MIDI input capability, the tracks would play whatever program is on it.


Should be possible, NI can do it...

http://www.native-instruments.com/en/support/knowledge-base/show/476/pro-tools-guide-how-to-insert-native-instruments-plug-ins/

Multiple MIDI tracks to the same plug-in

In the case of KONTAKT 5 it is possible to load multiple instruments into one instance and trigger them via different MIDI channels. In some cases you may want to send different MIDI tracks via different MIDI channels to the same plug-in.

Thanks to Eyac for this topic and to DJ Hellfire who has inspired it. Long time lurker here, eagerly waiting since 1.2 for the following features (already asked for months by many on this forum):

REQUEST N°1: MPC hardware as controller to input midi notes inside DAW midi tracks.

This is the most obvious basic function. Even the cheapest plastic midi keyboard or midi controller does that. Advertised selling point was: use your MPC within a DAW, so at least you'd expect it can input midi notes in your DAW.

The paradox is I can use my midi keyboard to play the MPC as a sound module but what's the point? Playing pads is NOT the same feel and you DON'T get the same results. Another paradox: since 1.5, Renaissance is a midi control surface for other softwares…

I understand that Ren's software is becoming a DAW by itself. Great for standalone users but I don't need a DAW within my DAW (sounds like Inception).

REQUEST N°2: Multitimbrality.

REQUEST N° 3: Renaissance pointer saved with the DAW project.

Everytime I open a Nuendo project including Renaissance, Ren's pen always takes the lead over Nuendo pointer. Before starting to work, I always have to go to Renaissance GUI to select the pointer to get normal use of my DAW. I would expect that my Ren's pointer selection would be saved with my DAW's project but not; kind of buggy.

comtox wrote:Would be great if we could use the MPC plugin like a sound module.. like I.E Kontakt, Sampletank or MachFive... the Hardware as a controller + a multi-sound module and the Daw as the sequencer + CC automation + Mixin' Audio returns from MPC .

I'm requesting that since October 2012. Don't think it's so difficult to have a multitimbral MPC plugin and allow coexistence with the Element plugin in controller mode.

highcaliba wrote:That ^^^ has been the only real thing i've asked for since day one and the only reason I first bought the REN to begin with. Thinking I was going to be able to use it as a sound module in my DAW (ie, battery, kontakt and etc) Hopefully they incorporate a multi-timberal feature or a drag and drop... Something less time consuming than exporting and re-importing.

You're not alone brothers. Don't have time to make a full forum research but there are many more.

Looks like my plugin issue with not having visibility of the plugin presets may be resolved.

aldred411 wrote:I'm confused now because the keyboard triggers pads cubase sees it mpc sees it but the pads don't trigger midi
Ive tried searching for info and sat here for hours and played with different settings the best i can get is to record mpc midi via keyboard in cubase or record mpc midi in its daw then record the audio into cubase
I've tried the iac driver thing on the mac don't know if i done it right and i tried input transformer which someone was on about online but again i don't know if i did this right as i haven't used this before.
any help would be most helpful

from england

chopchop wrote:the minute the mpc is loaded up pads and qlinks stop send note and cc messages

Is there anyway around this it doesnt seem possible to me it seems like akai has locked the midi to within the plugin and the only thing that sends cc once loaded up is are the transport button

which is very lame to be honest why on earth would you want to export a midi track then import it this does not aid work flow in teh slightest its anti work flow and to me renders the plugin useless


Come on akai!

Just a little search on this topic shows that request of using the Ren as a sound module, its pads as a controller and DAW as the sequencer has been there for a while.

If I read correctly 1.7 released notes, using MPC as a sound module, Ren hardware as a controller and DAW as the sequencer is still not there.

Maybe I 'm going to campaign about this.

Cinetrax wrote:If I read correctly 1.7 released notes, using MPC as a sound module, Ren hardware as a controller and DAW as the sequencer is still not there.

Maybe I 'm going to campaign about this.

That's what this thread is all about. Hopefully you can keep pushing too. The plugin needs a LOT of attention IMO.
But what you're describing is absolutely necessary IMO.

One thing for sure, the update might just fix my preset view problems. Now i can save custom presets and pull them up on the fly.

Let's see how this goes.

Can any of the beta testers confirm that these requests "made it" to Akai?