By Cinetrax
Wed Jul 15, 2015 6:29 pm
Letter to the developers from a DAW user.
If 1.9 is still in active development, could you consider the request asked by many to improve the use of Renaissance hardware as controller, MPC software as sound module with DAW as sequencer.
When I bought the Renaissance (v1.2), one of the advertised selling point was: Use your MPC within a DAW. So my expectation was to use MPC hardware to input midi notes inside DAW midi tracks (as I do with any midi keyboard) to make my DAW play MPC sounds. Actually that was not possible.
Then v1.5 brought Midi Control Mode and added ability to use pads to input midi notes into DAW. Great! But midi note mapping is not the same in Midi Control Mode as it is in MPC default "normal" use:
Default (and historical) MPC midi note mapping goes C#1, C1, F#1, A#5, E1, D1, A#2, G#2, etc, etc… This is also the default mapping for every MPC factory or extension programs. But Midi Control Mode is C1, C#1, D1, D#1, E1, F1, etc… You see the conflict here.
To change default midi mapping, the only existing solution was given by DJ Hellfire on the forum: open .xpm files in a text editor and manually edit each pad midi note.
Even if my Autoload template has now this custom midi map, I have to copy and paste this Text Edited map inside every factory or extension .xpm that I want to use. Veeeery time consuming.
The other way around is to save a midi control scene following the "bizarre" MPC default mapping to be used in Midi Control Mode . This is not a good solution for DAW use: editing all over the place midi notes inside DAW is not funny at all…
1st) request would be an optional Preference to choose C1, C#1, D1, etc… as default midi mapping (as it exists in previous MPCs)
2) Please, enable Note Repeat inside Midi Control Mode. This MPC constitutive feature is very needed to enter repeated midi notes following pad velocity pressure into DAW tracks.
3) Enable 16 Level as well (I can imagine this one is tricky but you guys are geniuses!)
4) Multitimbrality
5) A nice touch would be retaining MPC pointer of choice within MPC project. Personally, I like to use the arrow pointer but MPC software always opens up with the pen.
One nice quiet improvement from 1.7 was Ren's pen not taking the lead over Nuendo pointer anymore.
Thanks for your attention
If 1.9 is still in active development, could you consider the request asked by many to improve the use of Renaissance hardware as controller, MPC software as sound module with DAW as sequencer.
When I bought the Renaissance (v1.2), one of the advertised selling point was: Use your MPC within a DAW. So my expectation was to use MPC hardware to input midi notes inside DAW midi tracks (as I do with any midi keyboard) to make my DAW play MPC sounds. Actually that was not possible.
Then v1.5 brought Midi Control Mode and added ability to use pads to input midi notes into DAW. Great! But midi note mapping is not the same in Midi Control Mode as it is in MPC default "normal" use:
Default (and historical) MPC midi note mapping goes C#1, C1, F#1, A#5, E1, D1, A#2, G#2, etc, etc… This is also the default mapping for every MPC factory or extension programs. But Midi Control Mode is C1, C#1, D1, D#1, E1, F1, etc… You see the conflict here.
To change default midi mapping, the only existing solution was given by DJ Hellfire on the forum: open .xpm files in a text editor and manually edit each pad midi note.
Even if my Autoload template has now this custom midi map, I have to copy and paste this Text Edited map inside every factory or extension .xpm that I want to use. Veeeery time consuming.
The other way around is to save a midi control scene following the "bizarre" MPC default mapping to be used in Midi Control Mode . This is not a good solution for DAW use: editing all over the place midi notes inside DAW is not funny at all…
1st) request would be an optional Preference to choose C1, C#1, D1, etc… as default midi mapping (as it exists in previous MPCs)
2) Please, enable Note Repeat inside Midi Control Mode. This MPC constitutive feature is very needed to enter repeated midi notes following pad velocity pressure into DAW tracks.
3) Enable 16 Level as well (I can imagine this one is tricky but you guys are geniuses!)
4) Multitimbrality
5) A nice touch would be retaining MPC pointer of choice within MPC project. Personally, I like to use the arrow pointer but MPC software always opens up with the pen.
One nice quiet improvement from 1.7 was Ren's pen not taking the lead over Nuendo pointer anymore.
Thanks for your attention
MPC X - 3.9 - MPC VST3 beta 3.9
MPC X - 2.15.1 - MPC VST 2.15.1
Mac Pro M2 Ultra 2023 - 192 Go RAM
OSX 26.5.1 Tahoe
Nuendo 12.0.70
Nuendo 15.0.30
Apogee Symphony MkII I/O 32 x 32 SE
MPC X - 2.15.1 - MPC VST 2.15.1
Mac Pro M2 Ultra 2023 - 192 Go RAM
OSX 26.5.1 Tahoe
Nuendo 12.0.70
Nuendo 15.0.30
Apogee Symphony MkII I/O 32 x 32 SE
