Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
By souleymaz Mon Nov 12, 2012 1:06 pm
And now, the fantom xr software doesn t work on mountain lion...

Would be a great feature for the renaissance.

PEACE
User avatar
By JAH Mon Nov 12, 2012 1:45 pm
souleymaz wrote:And now, the fantom xr software doesn t work on mountain lion...

Would be a great feature for the renaissance.

PEACE

Need to have a petition for this one. Been trying to get Akai to add this since the MPC 2500. It would be amazing if I can read the name of my synth patches from the Ren.
User avatar
By charlieocali Mon Nov 12, 2012 8:55 pm
JAH wrote:
A patch script, or patch list, is the bridge that integrates your external MIDI keyboards and sound modules with your sequencing software. Without this list, there is no way for the software to know which sounds reside in your gear. A patch script is a listing of all the sounds with their MIDI addresses programmed in the format that the software requires.


With legacy MPCs, when you assign a MIDI sound module or keyboard to a track, there is no way for the MPC to identify what sounds are in these sound modules. MPCs just treats all external sounds as Programs 1-127, without the names of the patches.

It would be awesome if the MPC Ren can support Patch Scripts like Cubase. So when a Patch Script is loaded for a sound module, like the Fantom XR, and you choose a MIDI Track, that tracks' Program field will list the names of all the patches found in the Fantom XR. This will allow you to select pacthes by their names instead of program numbers.



This would be a great feature.

What would need to happen first in my opinion:

Implement a external sync feature. As it stands now in version 1.1 the Ren CANNOT slave to Midi Beat Clock, or MTC, and DOES NOT transmit midi when in plugin mode.


This leaves you to have to sample all of your external gear once you are ready to "track out" (record all of your midi to audio). This is process of resampling everything can be convoluted, and the sample mode lacks features to make this a viable option.

YMMV.

If and when these things get sorted, I will be buying up a few choice pieces.
User avatar
By JAH Mon Nov 12, 2012 9:33 pm
charlieocali wrote:
JAH wrote:
A patch script, or patch list, is the bridge that integrates your external MIDI keyboards and sound modules with your sequencing software. Without this list, there is no way for the software to know which sounds reside in your gear. A patch script is a listing of all the sounds with their MIDI addresses programmed in the format that the software requires.


With legacy MPCs, when you assign a MIDI sound module or keyboard to a track, there is no way for the MPC to identify what sounds are in these sound modules. MPCs just treats all external sounds as Programs 1-127, without the names of the patches.

It would be awesome if the MPC Ren can support Patch Scripts like Cubase. So when a Patch Script is loaded for a sound module, like the Fantom XR, and you choose a MIDI Track, that tracks' Program field will list the names of all the patches found in the Fantom XR. This will allow you to select pacthes by their names instead of program numbers.



This would be a great feature.

What would need to happen first in my opinion:

Implement a external sync feature. As it stands now in version 1.1 the Ren CANNOT slave to Midi Beat Clock, or MTC, and DOES NOT transmit midi when in plugin mode.


This leaves you to have to sample all of your external gear once you are ready to "track out" (record all of your midi to audio). This is process of resampling everything can be convoluted, and the sample mode lacks features to make this a viable option.

YMMV.

If and when these things get sorted, I will be buying up a few choice pieces.

In Plugin Mode, the DAW takes over MIDI. The Ren's 4 MIDI outs should be listed as options in your DAW.
By boomspot Mon Nov 12, 2012 11:29 pm
JAH wrote:In Plugin Mode, the DAW takes over MIDI. The Ren's 4 MIDI outs should be listed as options in your DAW.


What good is this when the sequence data is inside the MPC plugin?
User avatar
By Metatron72 Tue Nov 13, 2012 12:43 am
boomspot wrote:
JAH wrote:In Plugin Mode, the DAW takes over MIDI. The Ren's 4 MIDI outs should be listed as options in your DAW.


What good is this when the sequence data is inside the MPC plugin?


They want it to be able pass some of that data to the output ports for any outboard stuff they may have.

The original topic request is a good one and shouldn't be too hard to add as it's been done many times previously in the world of MIDI.
User avatar
By JAH Tue Nov 13, 2012 2:13 am
boomspot wrote:
JAH wrote:In Plugin Mode, the DAW takes over MIDI. The Ren's 4 MIDI outs should be listed as options in your DAW.


What good is this when the sequence data is inside the MPC plugin?

If I get time, I'll post a video.
By boomspot Tue Nov 13, 2012 4:31 am
Metatron72 wrote:
boomspot wrote:
JAH wrote:In Plugin Mode, the DAW takes over MIDI. The Ren's 4 MIDI outs should be listed as options in your DAW.


What good is this when the sequence data is inside the MPC plugin?


They want it to be able pass some of that data to the output ports for any outboard stuff they may have.

The original topic request is a good one and shouldn't be too hard to add as it's been done many times previously in the world of MIDI.


Right, I was questioning the logic in having the DAW take over outputting the midi when Ren is inserted as a plug. The MPC handled the original sequencing and should be sending the midi out of the 4 ports to the hardware synths, not the DAW ports.

The original request would be cool, shouldn't be hard to have the software read the .midname files.

D
User avatar
By JAH Tue Nov 13, 2012 8:58 am
boomspot wrote:
Right, I was questioning the logic in having the DAW take over outputting the midi when Ren is inserted as a plug. The MPC handled the original sequencing and should be sending the midi out of the 4 ports to the hardware synths, not the DAW ports.


I don't see it as the DAW taking over the ports. It seems pretty simple and logical to me.



1. Connect MPC Ren MIDI output A to the MIDI input of Motif rack

2. Create two Instrument Tracks in your DAW

3. Insert an MPC Ren plugin on Instrument Track 1 of your DAW

4. Set the Ren's Track 1 to MIDI, Port A, MIDI Ch 1

5. Name Instrument Track 2 of your DAW 'Motif synth'

6. Set MIDI Input of Instrument Track 2 to 'MPC'; set MIDI Out to 'MPC Port 1 (A), MIDI Ch 1'

When you press the pads and record sequence data inside the Ren, it triggers your Motif. Ok...so what else?

Your DAWs instrument tracks are also audio tracks with inputs. Connect the outputs of the Motif to Input 1/2 of your sound card. On your DAWs Instrument Track 2, set the input to Input 1/2. When you are ready to record actual audio, the Ren will play the MIDI sequence created using the Motif while your DAW records the audio. You can also use this method for plugin instruments.

This method will allow you to use the Ren as your MIDI sequencer. Your DAW will me your plugin host and multi-track recorder. If you have a 64 Bit DAW that can host 32 bit Ren plugin...you know have a work-around to the 32 bit limitations of strictly using the Ren.
By boomspot Tue Nov 13, 2012 10:05 am
JAH wrote:
boomspot wrote:
Right, I was questioning the logic in having the DAW take over outputting the midi when Ren is inserted as a plug. The MPC handled the original sequencing and should be sending the midi out of the 4 ports to the hardware synths, not the DAW ports.


I don't see it as the DAW taking over the ports. It seems pretty simple and logical to me.



1. Connect MPC Ren MIDI output A to the MIDI input of Motif rack

2. Create two Instrument Tracks in your DAW

3. Insert an MPC Ren plugin on Instrument Track 1 of your DAW

4. Set the Ren's Track 1 to MIDI, Port A, MIDI Ch 1

5. Name Instrument Track 2 of your DAW 'Motif synth'

6. Set MIDI Input of Instrument Track 2 to 'MPC'; set MIDI Out to 'MPC Port 1 (A), MIDI Ch 1'

When you press the pads and record sequence data inside the Ren, it triggers your Motif. Ok...so what else?

Your DAWs instrument tracks are also audio tracks with inputs. Connect the outputs of the Motif to Input 1/2 of your sound card. On your DAWs Instrument Track 2, set the input to Input 1/2. When you are ready to record actual audio, the Ren will play the MIDI sequence created using the Motif while your DAW records the audio. You can also use this method for plugin instruments.

This method will allow you to use the Ren as your MIDI sequencer. Your DAW will me your plugin host and multi-track recorder. If you have a 64 Bit DAW that can host 32 bit Ren plugin...you know have a work-around to the 32 bit limitations of strictly using the Ren.


How are you getting your GUI to let you choose Port A, MIDI Ch 1 while in plugin mode? I'm only able to select DAW when my Ren is in plugin mode, I need Ren MPC port 1. Akai confirmed that the Ren won't output midi while in plugin mode.

Interesting.

D
User avatar
By JAH Tue Nov 13, 2012 10:36 am
Yes, your MPC should have DAW in Preferences.

But look to your DAW. Your DAW should show MPC ports as options for MIDI I/O.
By boomspot Tue Nov 13, 2012 4:10 pm
Please send me a copy of your pro tool session to see how you have it routed. Still not getting the MPC to send midi to my synths while in plugin mode despite following your instructions.

Thanks.

D