Suggestion for an alternative Shift function method!

Honestly,The only one that bothers me is "SAMPLE REC" Having to press shift for that really annoys.I should be able to go straight to the mode! one button access, no hassle,no prob.MPC 's are samplers right???? That should sum it up.

Im pretty sure peeps would agree!!

xparis001 wrote:this is one of those feature implementations that I worry about. In theory, it could be done, but please understand from a system point of view what this might mean.

take for instance the DATA SELECT buttons. if we were to blindly implement it, if i wanted to go to FOLDER 1, and I double clicked, PROJECT would be set first, then FOLDER 1 would open.

this would be annoying, to say the least. so to remedy this, we have to incorporate what's called a "wait state".

what this wait state would do is essentially, sit back, acknowledge the button press, and then wait a certain amount of time to see if the button is pressed again. a good example of this is the delete key on your keyboard. if you press it and hold it, it deletes 1 character, then pauses slightly, then starts moving backwards. its waiting to see if the holding down is intentional.

blah blah blah, what does this all mean for a user? well, it means that if you press a button, say SAMPLE EDIT just once, you're going to have probably 200ms pause before the mode is activated. it MAY be fast enough to not notice, but people might perceive it as lag.

is that a dealbreaker?

No no no! This suggestion WOULD NOT apply to any of the data select buttons. Only pad bank, program edit, program mix, sequence edit, sample edit, song, Main, pad mute and Window.

Data select buttons, undo, browser, pad copy, full level, note repeat would all be excluded from this suggestion.

DJ Hellfire wrote:

xparis001 wrote:this is one of those feature implementations that I worry about. In theory, it could be done, but please understand from a system point of view what this might mean.

take for instance the DATA SELECT buttons. if we were to blindly implement it, if i wanted to go to FOLDER 1, and I double clicked, PROJECT would be set first, then FOLDER 1 would open.

this would be annoying, to say the least. so to remedy this, we have to incorporate what's called a "wait state".

what this wait state would do is essentially, sit back, acknowledge the button press, and then wait a certain amount of time to see if the button is pressed again. a good example of this is the delete key on your keyboard. if you press it and hold it, it deletes 1 character, then pauses slightly, then starts moving backwards. its waiting to see if the holding down is intentional.

blah blah blah, what does this all mean for a user? well, it means that if you press a button, say SAMPLE EDIT just once, you're going to have probably 200ms pause before the mode is activated. it MAY be fast enough to not notice, but people might perceive it as lag.

is that a dealbreaker?

No no no! This suggestion WOULD NOT apply to any of the data select buttons. Only pad bank, program edit, program mix, sequence edit, sample edit, song, Main, pad mute.

Data select buttons, undo, browser, pad copy, full level, note repeat would all be excluded from this suggestion.

^^^This is what I understood when I voted positively, only apply where suitable...not function keys...

xparis001 wrote:this is one of those feature implementations that I worry about. In theory, it could be done, but please understand from a system point of view what this might mean.

take for instance the DATA SELECT buttons. if we were to blindly implement it, if i wanted to go to FOLDER 1, and I double clicked, PROJECT would be set first, then FOLDER 1 would open.

this would be annoying, to say the least. so to remedy this, we have to incorporate what's called a "wait state".

what this wait state would do is essentially, sit back, acknowledge the button press, and then wait a certain amount of time to see if the button is pressed again. a good example of this is the delete key on your keyboard. if you press it and hold it, it deletes 1 character, then pauses slightly, then starts moving backwards. its waiting to see if the holding down is intentional.

blah blah blah, what does this all mean for a user? well, it means that if you press a button, say SAMPLE EDIT just once, you're going to have probably 200ms pause before the mode is activated. it MAY be fast enough to not notice, but people might perceive it as lag.

is that a dealbreaker?

just pad banks and sample edit/sample record only Dan, everything else could become a little confusing .If I toggle bank A I want bank E if I toggle sample edit I want sample record.No 2nd guessing that.. NO "wait state" if i mistakenly goto the wrong function Ill just toggle it again to undo.

This would be great for live performances (picture arab muzik ) quick access to your sounds just a button push away,Not Shift than which ever .......thx for listening Dan and replying back.

xparis001 wrote:blah blah blah, what does this all mean for a user? well, it means that if you press a button, say SAMPLE EDIT just once, you're going to have probably 200ms pause before the mode is activated. it MAY be fast enough to not notice, but people might perceive it as lag.

is that a dealbreaker?

The lag of going from one mode to another is a big complaint of the MPC 5000 OS2. Thinking about this more.....this idea is great for Pad Banks as older MPCs like the MPC 3000 used a single button to access different banks. This wouldn't be any different.

But double clicking a Mode button to access a secondary function? I don't think it is a good idea if the implementation results in there being a delay every time you want to change modes.

I would personally prefer a SHIFT lock function.

JAH wrote:

xparis001 wrote:blah blah blah, what does this all mean for a user? well, it means that if you press a button, say SAMPLE EDIT just once, you're going to have probably 200ms pause before the mode is activated. it MAY be fast enough to not notice, but people might perceive it as lag.

is that a dealbreaker?

The lag of going from one mode to another is a big complaint of the MPC 5000 OS2. Thinking about this more.....this idea is great for Pad Banks as older MPCs like the MPC 3000 used a single button to access different banks. This wouldn't be any different.

But double clicking a Mode button to access a secondary function? I don't think it is a good idea if the implementation results in there being a delay every time you want to change modes.

I would personally prefer a SHIFT lock function.

Yeah, I really don't quite even understand the need for this delay for any of the suggested buttons we are requesting!

DJ Hellfire wrote:

JAH wrote:

xparis001 wrote:blah blah blah, what does this all mean for a user? well, it means that if you press a button, say SAMPLE EDIT just once, you're going to have probably 200ms pause before the mode is activated. it MAY be fast enough to not notice, but people might perceive it as lag.

is that a dealbreaker?

The lag of going from one mode to another is a big complaint of the MPC 5000 OS2. Thinking about this more.....this idea is great for Pad Banks as older MPCs like the MPC 3000 used a single button to access different banks. This wouldn't be any different.

But double clicking a Mode button to access a secondary function? I don't think it is a good idea if the implementation results in there being a delay every time you want to change modes.

I would personally prefer a SHIFT lock function.

Yeah, I really don't quite even understand the need for this delay for any of the suggested buttons we are requesting!

the problem is you have a product out in the world, and suddenly, buttons that are all labeled the same are doing different things. Its confusing. Not everyone understands the logic, and not everyone's on the forum. if the hardware is marked with orange silk screening, all buttons affected by it have to act the same.

xparis001 wrote:

DJ Hellfire wrote:

JAH wrote:The lag of going from one mode to another is a big complaint of the MPC 5000 OS2. Thinking about this more.....this idea is great for Pad Banks as older MPCs like the MPC 3000 used a single button to access different banks. This wouldn't be any different.

But double clicking a Mode button to access a secondary function? I don't think it is a good idea if the implementation results in there being a delay every time you want to change modes.

I would personally prefer a SHIFT lock function.

Yeah, I really don't quite even understand the need for this delay for any of the suggested buttons we are requesting!

the problem is you have a product out in the world, and suddenly, buttons that are all labeled the same are doing different things. Its confusing. Not everyone understands the logic, and not everyone's on the forum. if the hardware is marked with orange silk screening, all buttons affected by it have to act the same.

Ah, I see what you're saying!

DJ Hellfire wrote:

xparis001 wrote:the problem is you have a product out in the world, and suddenly, buttons that are all labeled the same are doing different things. Its confusing. Not everyone understands the logic, and not everyone's on the forum. if the hardware is marked with orange silk screening, all buttons affected by it have to act the same.

Ah, I see what you're saying!

That is why the SHIFT lock function would be a good compromise.

JAH wrote:

DJ Hellfire wrote:

xparis001 wrote:the problem is you have a product out in the world, and suddenly, buttons that are all labeled the same are doing different things. Its confusing. Not everyone understands the logic, and not everyone's on the forum. if the hardware is marked with orange silk screening, all buttons affected by it have to act the same.

Ah, I see what you're saying!

damn!

xparis001 wrote:
the problem is you have a product out in the world, and suddenly, buttons that are all labeled the same are doing different things. Its confusing. Not everyone understands the logic, and not everyone's on the forum. if the hardware is marked with orange silk screening, all buttons affected by it have to act the same.

Ain't computer world a world of possibilities? Why not Standard + alternate options.
I mean leave the shift functions as they are now but give us the possibility to use the double click way in those suitable buttons.

xparis001 wrote:the problem is you have a product out in the world, and suddenly, buttons that are all labeled the same are doing different things. Its confusing. Not everyone understands the logic, and not everyone's on the forum. if the hardware is marked with orange silk screening, all buttons affected by it have to act the same.

We discussed the ergonomics of the button placements early last year and nothing was resolved, so it's no surprise that the shift button is causing issues. It was obvious to any serious MPC user from simply looking at a photo that it wasn't right.

Switching the shift function to a Nukai style mode button/shift toggle would be a positive first step.

Ultimately the controller needs to be opened up to be software configurable.

so an option in the preference menu for those that want that ability is out of the question?

Im not hating the toggle idea... hm. We'll have to see what we come up with

I'm repitting myself but...
Why an option in preferences?
Just put in the manual..."SHIFT+BUTTON X" and let discover the users that some cases you can ALSO do the same operation, just double clicking the BUTTON X...