Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By wudsiba Sat Sep 11, 2010 9:55 am
1.42 seems to have a few bugs. First off, the timing seems to change when using the shift note repeat method if you have it running and touch the Tap button. Only seems to happen the first time, and still not quite everytime. Also, if you have say a simple 1/8th note high hat repeating and you try to play a bass and snare over top, it has a flanging or double note effect that is not there if the same high hat is sequenced. The only reason for this addition would be to repeat one note so that you can free up the other pads to play normally. Unfortunately this leaves this feature useless. As for the sample looping... You have to loop everything on the same button push. Simply not as good as the older Numeric button method. (Reminds me... Need to check if that option still works if I switch numeric key to it's original function. Hopefully there will be some improvements. Haven't gotten to the Q-link addition and must go to work. Peace. JJ still rules.
User avatar
By mikolo Sat Sep 11, 2010 10:59 am
the flanging/double note thing is because note repeat is engaged globally when shift and pad is used (normal note repeat is global too) . if you hold down the additional pads you'll notice that they repeat until you take your finger off.


ive noticed a cool thing when you use the old methond of holding shift + note repeat button to display the t.c. note repeat values. If you also use the new shift+pad feature to lock your note repeat - the locked repeat will turn on/off/on as you toggle with the t.c. values. it will also jump between the different values when you hit dfferent f keys - continuing with the locked repeat.
User avatar
By le rat Sun Sep 12, 2010 2:49 pm
Regarding the SHIFT + PAD function, it would be cool if it could remenber the latest value pressed. For instance, if you keep SHIFT pressed and press the pad gradually, when you release it the MPC remember the first value (which was a lower value in that particular case).

Peace
By phx_chronic Wed Sep 15, 2010 8:35 pm
wow

I just updated to the 1.43XL for my 2500 last night.

After working for about two hours, i was randomly navigating on the main screen (i think pressing the + and up buttons) when the MP kinda froze for a second and then just rebooted itself.

very frustrating because i lost some work, but, also scary because i don't want to be thinking about this all the time or save my workin the middle of a session.

Has this happened to anyone?


double posted from Bug Report thread for those that don't check it regularly.
User avatar
By distortedtekno Wed Sep 15, 2010 9:42 pm
phx_chronic wrote:
wow

I just updated to the 1.43XL for my 2500 last night.

After working for about two hours, i was randomly navigating on the main screen (i think pressing the + and up buttons) when the MP kinda froze for a second and then just rebooted itself.

very frustrating because i lost some work, but, also scary because i don't want to be thinking about this all the time or save my workin the middle of a session.

Has this happened to anyone?


double posted from Bug Report thread for those that don't check it regularly.


I'll see if I can make my 1000 crash. I recorded a track that I wrote on the previous version and had no problem. But I'll see what happens when I start from scratch.
Hopefully this bug can be pinned down.

I dont like how the Q-link resets itself when having it assigned to LFO parameters. Cant wait to see that corrected.
User avatar
By le rat Mon Nov 22, 2010 8:34 pm
I thought the loop hold function had a strangeness but I realized that it also loops the layer. That means you can have different loops with different lenght as layers and make them looping at the same time in the main screen with the shortcut pad bank + a pad. Pretty cool :)
User avatar
By le rat Wed Nov 24, 2010 11:02 pm
You can make a pad or sereval pads looping and still playing other pads at the same time.

But the main drawbacks of that function in its actual state are :

-if you press a previously looped pad again it will stop
-it's not possible to add a loop on the fly.

What I'm doing for the moment is making one pad (and its layers) loop and play drums with the other pads at the same time.

I hope that it will be possible one day to add loops on the fly though.
(would be cool if it could work with SIMULT2 too)
User avatar
By le rat Thu Nov 25, 2010 9:29 am
I've just sadly noticed if we want to record the performance with the loop hold function we are still limited by that 9999 duration value in playback after recording :(
User avatar
By le rat Mon Nov 29, 2010 12:30 pm
Yep as I told you if you use layers or if you press the bank button and several pads at the same time it is possible.
By rarara Mon Nov 29, 2010 2:08 pm
le rat wrote:Yep as I told you if you use layers or if you press the bank button and several pads at the same time it is possible.

don't have access to my machine to test this right now but with layers if you have samples with different lengths do they all loop independently? or is the loop-point set from the main sample for the pad, so longer layered samples are potentially cut-off?