Akai mpc two

Frisbi wrote:Touchscreen is good for editing and prepare projects for performances.
But playing live you don't want to use it in a dark club with tension and heat and so on.
But Live is well thought for that.
When I play live I never use the touchscreen, I just move around with mute+pad and qlinks.
So really nothing to complain about that, the interaction between touchscreen and physical knobs and pads are well organized on Mpc Live.

I agree, it's just more complicated for me but I assume some of Live owners are satisfied for playing live.

One thing that could resolve some frustation about it would be a full remote MIDI implementation, as MPC software haves (and it's in addition divided in global & project assignations). So that an user could use any MIDI gear he wants to control any MPC parameter. Just one example: assigning q-links to CC 17-32 would allow us to control parameters from a MIDI keyboard with knobs just after making a program with custom q-link assignations (and exchange the program with someone else). It could also be useful to control metronome, or even the looper. But it is another topic. It's just something that I don't understand, exactly as the project notes which are present in the MPC software but not in the hardware (and it's just text I guess...).

c-real wrote:

Frisbi wrote:Touchscreen is good for editing and prepare projects for performances.
But playing live you don't want to use it in a dark club with tension and heat and so on.
But Live is well thought for that.
When I play live I never use the touchscreen, I just move around with mute+pad and qlinks.
So really nothing to complain about that, the interaction between touchscreen and physical knobs and pads are well organized on Mpc Live.

I agree, it's just more complicated for me but I assume some of Live owners are satisfied for playing live.

One thing that could resolve some frustation about it would be a full remote MIDI implementation, as MPC software haves (and it's in addition divided in global & project assignations). So that an user could use any MIDI gear he wants to control any MPC parameter. Just one example: assigning q-links to CC 17-32 would allow us to control parameters from a MIDI keyboard with knobs just after making a program with custom q-link assignations (and exchange the program with someone else). It could also be useful to control metronome, or even the looper. But it is another topic. It's just something that I don't understand, exactly as the project notes which are present in the MPC software but not in the hardware (and it's just text I guess...).

Just make it simple.
I organize all before so when I play live I just move around track mute, pad mute, qlinks page and next sequence.
If you use it this way it's fast and reliable.
Also I am trying to stay on track mute and open qlink page holding the qlink button.
That's even faster, because from track mute you can also change sequence.
I just wish they put "next bar" on track mute sequence slot on the top so I could also skip next sequence page.

JUKE 179r wrote:SCSI... it’ll have SCSI.

YES! the ressurection of my Syquest EZ Drive

peace

For my money, an MPC Two would have:

- Either Force or One enclosure, or even a slightly bigger One with full sized pads.
- Footswitch input (seriously important)
- 2 MIDI I/O
- At least 4 analog outs
- No battery, pros don't produce in the park

R

flextone wrote:- No battery, pros don't produce in the park

R

yeah i don't think the whole outdoors thing would really be my thing either... but what i do like is being able to quickly pop it down next to any piece of gear and quickly plug in a 1/4 cable with record sound from a piece of gear without having to create a whole setup when all i want is a quick sample.