v1.6 bug reports

InspectahEX wrote:BUG, Mav OSX

When sequencer is in 96ppqn mode the T.C. settings are still applied as if the sequencer was in 960ppqn

for example: In 96ppq mode you have to dial in "30" to get a time shift of "3"
for example: In 96ppq mode you have to dial in a swing of "54%" to actually get a "52%"swing

This is because the sequencer is still 960! 96 only changes the display of the Now positing so when nudging notes, they nudge at 96. You can't change the actual sequencer resolution or swing.

Thanks Hellfire. When you select left or right in the record screen I'm still hearing a stereo image. When listening to the sample in the sample edit screen I'll hear it's a mono sample.

Hellfire, I talked with Pete and he SAID it was a bug. I also know this too because it worked correctly before 1.6, once again, when in 96ppq the sequencer is supposed to shift and swing according to 96ppq or whatever resolution the sequencer is set to, Pete confirmed this with me already. 96 is supposed to change the resolution, not JUST the display. Come on bro I thought you were an mpc pro! How you not come across that one??

You really think its makes sense to have to dial in "30" when you only want to move "3" ppq in a 96ppq resolution???? T.C. still acts like the resolution is 960, pete knows this. Understand?

InspectahEX wrote:Come on bro I thought you were an mpc pro! How you not come across that one??

InspectahEX wrote:You really think its makes sense to have to dial in "30" when you only want to nudge "3" ppq in a 96ppq resolution???? T.C. still acts like the resolution is 960, pete knows this. Understand?

From what we were told, the resolution setting is ONLY for the follow now position display and the ONLY difference it makes is for nudging notes in the List Editor with the nudge button or from the sequence grid using the arrow keys on your computer keyboard. The sequencer still actually records at 960 regardless of the setting, which includes quantizing and swing. Not sure why Pete told you different. Maybe he misunderstood your comment?!

Example: If you have an event at 1:1:30, at 96 ppqn, you can nudge it to 1:1:33 (or 1:1:340 or 1:1:350, and so on), and if you then switch to 960 ppqn, you can see that same note is at 1:1:330 and can further nudge to 1:1:331, 1:1:332, 1:1:333, and so on.) But it doesn't affect swing or quantize! Swing and quantize are always based on 960 ppqn.

I understand fully what u are saying but you make my point exactly which is the problem

If swing and quantize are always based on 960ppq than thats means its broken, they advertise that the sequencer resolution can be switched down to 96ppq. So if you switch to 96 it should reflect different how many parts are getting nudged. You should not have to enter "30" to nudge/shift only "3". That means even thought its set to 96, its still acting, sounding and functioning in 960. So you're telling me the point of adding 96ppq mode was just to make it look/display differently? Na Bro, think about that. That should change depending on If it's not truly 96ppq like you are claiming, than thats such a failure because I rather work with 96 ppq being I make sampled beats and want my sequence tighter.

Pete misunderstood me at first but when I explained to him, he was like ohhhh ok, and he said they are working on fixing that. It's an obvious broken feature, don't know why you're defending Akai here when they themselves acknowledged it was **** up. You really want to dial in "80" just to shift a note "8" in 96ppq? thats retarded man, come on don't tell me that.. , you work with akai bc your so called expertise, you know thats not true 96ppq

DJ Hellfire wrote:

From what we were told, the resolution setting is ONLY for the follow now position display and the ONLY difference it makes is for nudging notes in the List Editor with the nudge button or from the sequence grid using the arrow keys on your computer keyboard. The sequencer still actually records at 960 regardless of the setting, which includes quantizing and swing. Not sure why Pete told you different. Maybe he misunderstood your comment?!

Swing and quantize are always based on 960 ppqn.

This is the problem, NEVER did they say 96ppq is just for show, or just for visual purpose. (which makes it useless) They advertise that the resolution of the sequencer can ACTUALLY be toggled to either 96 or 960. So if I switch to 96 and have to nudge a note 10 to the right, I have to dial in like 100 just to nudge 10!?!?, thats not right, and if thats what was intended that just shows whoever did that is **** retard, means basically there is no real 96ppq, and its some false fake advertised shit. Some people want the tightness of 96ppq especially who make sampled hip hop beats and when I switch to 96ppq and see everything still corresponding with 960ppq it makes me feel like what the ****

What pete said to me:

@iamrocgod Gotcha: "Shift Timing" doesn't honour PPQN display setting.




He said it's being fixed also. This is exactly what I was trying to say, that shifting/nudging doesn't correspond to the 96ppqn setting. You were saying it's supposed to work like that? It clearly isn't supposed to work like that.

Look bro! I don't know what Pete told you, nor does it matter; nor do I believe Pete understood what you were talking about. I'm not "defending" anything. I'm telling you how the shit works. I'm telling you that NO SETTING in the quantize menu adjusts notes according to 96 ppqn. Everything in the quantize menu operates a 960 ppqn. Nothing different than that was ever advertised. This is how it was designed.

You seem to have a misunderstanding of what nudge is. "Nudge" is NOT the Shift Timing feature in the quantize menu. They are two completely separate features.

*Shift Timing is done through the quantize menu. This is NOT nudging.
*Nudge is done from the left/right arrow keys on your computer keyboard. This is NOT shift timing.

And now there is a new list editor in 1.6 that lets you Nudge notes from the hardware, which you could NOT do before 1.6.

With that said, 96 ppqn is not just for show. It is STRICTLY for NUDGING, not for Shift Timing, not for quantizing, not for sequencing. No one ever said that the actual sequencer can be changed to 96. Not sure where you read that!

Also, I'm not sure why you believe 96 is tighter than 960, because it's not. With 96, you can only move notes at a minimum of 10 ppqn at a time. So 1 nudge = 10 ppqn. 960 is 10x finer that 96, so that same single nudge at 96 ppqn is equal to 10 nudges at 960. Every MPC has been 960, except maybe the MPC 60 I believe. But that's all irrelevent!

Lastly, knock it the **** of with telling me what I'm "supposed" to be and all the little slick "so-called expert" shit. I'm not the one for that shit bro! I'm just here to help you guys out!

DJ Hellfire wrote:Every MPC has been 960, except maybe the MPC 60 I believe.

No, only the 4K and 5K have been 960 ppq. Other models were all 96 ppq.

DJ Hellfire wrote:I'm just here to help you guys out!

Peace !

DJ Hellfire wrote:With that said, 96 ppqn is not just for show. It is STRICTLY for NUDGING, not for Shift Timing, not for quantizing, not for sequencing. No one ever said that the actual sequencer can be changed to 96. Not sure where you read that!

It is misleading, with the setting being located in the Preferences/Sequencer section, and being called Pulse Resolution.

The version 1.5 MPC User Guide does state that it does not affect the sequencer timing, though gives no detail of where it is used...

Pulse Resolution: Click this drop-down menu to select the display resolution (in PPQN—pulses per quarter note) of pulse values in certain areas of the software. Please note that this setting affects the display resolution, not the software's timing

I am not really sure why a 96ppqn nudge is of use in an otherwise 960 ppqn sequencer, it would make more sense to me if everything was in 96ppqn when you set the sequencer pulse resolution to 96ppqn.

What is the point of it, as is?

DJ Hellfire wrote:Also, I'm not sure why you believe 96 is tighter than 960, because it's not. With 96, you can only move notes at a minimum of 10 ppqn at a time. So 1 nudge = 10 ppqn. 960 is 10x finer that 96, so that same single nudge at 96 ppqn is equal to 10 nudges at 960.

A sequencer based on 96ppqn is tighter, it has more of a standard quantize than one based on 960ppqn, so 96ppqn moves everything closer to the beat (tighter) than 960ppqn.

I understand tighter as being different than finer, and where he was coming from with that comment.

DJ Hellfire wrote:Every MPC has been 960, except maybe the MPC 60 I believe.

Most MPCs are 96ppqn, only MPC4000, MPC5000, and MPC Software, are 960ppqn.

SimonInAustralia wrote:

DJ Hellfire wrote:With that said, 96 ppqn is not just for show. It is STRICTLY for NUDGING, not for Shift Timing, not for quantizing, not for sequencing. No one ever said that the actual sequencer can be changed to 96. Not sure where you read that!

It is misleading, with the setting being located in the Preferences/Sequencer section, and being called Pulse Resolution.

The version 1.5 MPC User Guide does state that it does not affect the sequencer timing, though gives no detail of where it is used...

Pulse Resolution: Click this drop-down menu to select the display resolution (in PPQN—pulses per quarter note) of pulse values in certain areas of the software. Please note that this setting affects the display resolution, not the software's timing

I am not really sure why a 96ppqn nudge is of use in an otherwise 960 ppqn sequencer, it would make more sense to me if everything was in 96ppqn when you set the sequencer pulse resolution to 96ppqn.

What is the point of it, as is?

DJ Hellfire wrote:Also, I'm not sure why you believe 96 is tighter than 960, because it's not. With 96, you can only move notes at a minimum of 10 ppqn at a time. So 1 nudge = 10 ppqn. 960 is 10x finer that 96, so that same single nudge at 96 ppqn is equal to 10 nudges at 960.

A sequencer based on 96ppqn is tighter, it has more of a standard quantize than one based on 960ppqn, so 96ppqn moves everything closer to the beat (tighter) than 960ppqn.

I understand tighter as being different than finer, and where he was coming from with that comment.

1. It is unclear. I even had the same question myself when 1.5 was release with the option. However, when 1.6 was release I explained exactly what the feature does. And I mentioned it several different times in a few different threads since 1.6 released. The fact that it is unclear is just poor communication of the feature. But it does not mean that it was advertised to do something it does not.

2. I don't know what the point of 96 ppqn in this regard. I don't use it. I did not program it, nor did I make the decision for the feature to be added. I'm just telling everyone exactly how the feature works since everyone is so unclear on it.

3. As far as 96 vs 960 in regards to one being tighter than the other, then I guess that would depend on your definition of tight. Example, tight to a quantized grid or tight to how the performer naturally played the instrument?! For an unquantized performance, 96 ppqn will not be as tight as 960 to your actual performance. If it's quantized, then that could be the opposite. It's subjective I guess you could say!

DJ Hellfire wrote:Look bro! I don't know what Pete told you, nor does it matter; nor do I believe Pete understood what you were talking about. I'm not "defending" anything. I'm telling you how the shit works. I'm telling you that NO SETTING in the quantize menu adjusts notes according to 96 ppqn. Everything in the quantize menu operates a 960 ppqn. Nothing different than that was ever advertised. This is how it was designed.

You seem to have a misunderstanding of what nudge is. "Nudge" is NOT the Shift Timing feature in the quantize menu. They are two completely separate features.

*Shift Timing is done through the quantize menu. This is NOT nudging.
*Nudge is done from the left/right arrow keys on your computer keyboard. This is NOT shift timing.

And now there is a new list editor in 1.6 that lets you Nudge notes from the hardware, which you could NOT do before 1.6.

With that said, 96 ppqn is not just for show. It is STRICTLY for NUDGING, not for Shift Timing, not for quantizing, not for sequencing. No one ever said that the actual sequencer can be changed to 96. Not sure where you read that!

Also, I'm not sure why you believe 96 is tighter than 960, because it's not. With 96, you can only move notes at a minimum of 10 ppqn at a time. So 1 nudge = 10 ppqn. 960 is 10x finer that 96, so that same single nudge at 96 ppqn is equal to 10 nudges at 960. Every MPC has been 960, except maybe the MPC 60 I believe. But that's all irrelevent!

Lastly, knock it the **** of with telling me what I'm "supposed" to be and all the little slick "so-called expert" shit. I'm not the one for that shit bro! I'm just here to help you guys out!

First of all your acting like I'm starting some complex argument. I'm saying one simple thing, that there is a bug and that shift timing from the t.c. window on the hardware isn't accurate when sequencer is set to 96 resolution. Only reason I brought up Pete was because he said it was not intended to work that way, fully understanding what I was talking about, and then you were trying to say that's how it's supposed to be. I think it's hilarious you say I am the one on some "so called expert" shit. You're the one saying its supposed to be like that when its obviously not. When in 96, shifting "100" should not shift "10" THAT IS ALL I was saying. Also, the mpc2500, the 1000 and pretty much every mpc before that had a 96ppq, not 960. I'm not trying to come off like "ohhh I'm an expert" but I'm just correcting you with the facts because you're comments seemed to discredit the bug I posted.

DJ Hellfire wrote:You seem to have a misunderstanding of what nudge is. "Nudge" is NOT the Shift Timing feature in the quantize menu. They are two completely separate features.

Are you serious though? I never ONCE said I was referring to the "Nudge" feature, I clearly stated (don't know how u got it confused) that I was talking about Shift Timing in the T.C. Window when the sequencer is in 96ppqn. I know the difference between nudge feature and shift timing man, get your facts straight. No one is attacking you, its in your imagination.

InspectahEX wrote:

DJ Hellfire wrote:Look bro! I don't know what Pete told you, nor does it matter; nor do I believe Pete understood what you were talking about. I'm not "defending" anything. I'm telling you how the shit works. I'm telling you that NO SETTING in the quantize menu adjusts notes according to 96 ppqn. Everything in the quantize menu operates a 960 ppqn. Nothing different than that was ever advertised. This is how it was designed.

You seem to have a misunderstanding of what nudge is. "Nudge" is NOT the Shift Timing feature in the quantize menu. They are two completely separate features.

*Shift Timing is done through the quantize menu. This is NOT nudging.
*Nudge is done from the left/right arrow keys on your computer keyboard. This is NOT shift timing.

And now there is a new list editor in 1.6 that lets you Nudge notes from the hardware, which you could NOT do before 1.6.

With that said, 96 ppqn is not just for show. It is STRICTLY for NUDGING, not for Shift Timing, not for quantizing, not for sequencing. No one ever said that the actual sequencer can be changed to 96. Not sure where you read that!

Also, I'm not sure why you believe 96 is tighter than 960, because it's not. With 96, you can only move notes at a minimum of 10 ppqn at a time. So 1 nudge = 10 ppqn. 960 is 10x finer that 96, so that same single nudge at 96 ppqn is equal to 10 nudges at 960. Every MPC has been 960, except maybe the MPC 60 I believe. But that's all irrelevent!

Lastly, knock it the **** of with telling me what I'm "supposed" to be and all the little slick "so-called expert" shit. I'm not the one for that shit bro! I'm just here to help you guys out!

First of all your acting like I'm starting some complex argument. I'm saying one simple thing, that there is a bug and that shift timing from the t.c. window on the hardware isn't accurate when sequencer is set to 96 resolution. Only reason I brought up Pete was because he said it was not intended to work that way, fully understanding what I was talking about, and then you were trying to say that's how it's supposed to be. I think it's hilarious you say I am the one on some "so called expert" shit. You're the one saying its supposed to be like that when its obviously not. When in 96, shifting "100" should not shift "10" THAT IS ALL I was saying. Also, the mpc2500, the 1000 and pretty much every mpc before that had a 96ppq, not 960. I'm not trying to come off like "ohhh I'm an expert" but I'm just correcting you with the facts because you're comments seemed to discredit the bug I posted.

I'm not saying you are on some expert shit! You're throwing that shit my way basically calling me some type of idiot because I'm supposed to be some MPC expert and I don't get your "bug". Those were your words dude! I ignored it the first time!

InspectahEX wrote:Hellfire, Come on bro I thought you were an mpc pro! How you not come across that one??

InspectahEX wrote:you work with akai bc your so called expertise, you know thats not true 96ppq

C'mon bro, don't even try to play me!

I'm telling you how the system works. There is no bug. You just don't understand what Shift Timing is. Pete has no idea what you are talking about. I asked. What I'm telling you is the way it works. The fact that it's unclear is another issue. But this is the way it works and is designed to work! Period!