Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By Putter Wed Sep 27, 2006 7:06 am
Well I'm not sure if this has been noticed & I haven't seen it anywhere.

This may benefit you live MPC players alot. :o

1. Press Play / Play Start - Sequence plays

2. Press Play Start again - Sequence starts over from Bar 1

This works while in Record & Over Dub modes also. If you are recording, it does not record the stutter stop, it just starts the session from Bar 1 and continues. This may be useful in various situations such as tracking or live shows as mentioned B4. No more Stop, Play Start for a stutter effect. :o

If you have any more finds that are not known, post them here. :idea:
By defect Wed Sep 27, 2006 7:51 am
Putter wrote: No more Stop, Play Start for a stutter effect. :o

If you have any more finds that are not known, post them here. :idea:


and nomore the trackmute :D don´t work without press stop after recording....
User avatar

By mkl... Wed Sep 27, 2006 8:50 am
hi there, that's my first post in here, i'm french so please excuse my english.
i hope you'll understand.

i found that :

on the main screen, choose a tc off>>>then go to grid edit and you can edit your beat really precisely (the maximum is 96 ticks).
right now you can drill. or make really strange rythmics :D
User avatar

By Od3rus Wed Sep 27, 2006 1:03 pm
Give us a snare rush!
By truvc Wed Sep 27, 2006 2:28 pm
defect wrote:
Putter wrote: No more Stop, Play Start for a stutter effect. :o

If you have any more finds that are not known, post them here. :idea:


and nomore the trackmute :D don´t work without press stop after recording....

yes, this is really sad.
this bug appeared after 1.01 i beleive. i reckon it is a new feature which created the bug.

i think that new features are wicked, BUT if a new feature break an old feature, then this new feature should either not be there or be fixed.

maybe if people send enough polite request to have track mute back, the JJ can do something.
By cyklops Wed Sep 27, 2006 4:19 pm
truvc wrote:
defect wrote:
Putter wrote: No more Stop, Play Start for a stutter effect. :o

If you have any more finds that are not known, post them here. :idea:


and nomore the trackmute :D don´t work without press stop after recording....

yes, this is really sad.
this bug appeared after 1.01 i beleive. i reckon it is a new feature which created the bug.

i think that new features are wicked, BUT if a new feature break an old feature, then this new feature should either not be there or be fixed.

maybe if people send enough polite request to have track mute back, the JJ can do something.



what do you mean ? recordable track mutes is still there ? the stop bug still seems to be there, and i have emailed a bug report on this as well

By truvc Wed Sep 27, 2006 4:28 pm
i was not talking about recordable track mutes, but the track mute screen.

the bug is that once you have done [REC] or [DUB] then you cannot access [Track Mute] anymore. need to do [stop] and [play], which really restrain the use of the mpc for live shows imho.

By Xserch Wed Sep 27, 2006 4:49 pm
I have the same problem with not being able to use the track mutes screen after recording untill I stop the sequence, I am using JJ os 1.0 so it's not just after 1.1

By sleepersriddle Wed Sep 27, 2006 5:19 pm
ooh, that's a bad one, cause i did use that function before. hope it gets fixed. do we need to add it to some bug thread?

By truvc Wed Sep 27, 2006 5:23 pm
yes, that's a bad one. especially since it used to work fine before.

so i think it is better to send it directly to the JJ using their bug report.
http://www7a.biglobe.ne.jp/~mpc1000/report.htm

and the more people doing it then the more chance we have to get it fixed.
User avatar

By chilom Thu Sep 28, 2006 10:57 am
i send an email yesterday to JJ asking about the 128 Mo and BPM detector.
they anwser fast through their webpage.

i asked if the 256 mo ram detected as 128 was only an os issue, and if so can be corrected.
JJ FAQ wrote:[128Mbytes memory]
A memory cannot be increased more than 128M on the problem of CPU and hardware.
It seems that the memory of 256M is used since the memory of 128M cannot be obtained.


i asked a correction about the BPM, giving him the proper equation for solving :

JJ faq wrote:[DETECT TEMPO]
  It knows that TEMPO does not operate well.
It also knows asking by calculation.
It is easy to correct itself.
However, since there is another problem, it cannot do simply.
Please wait for a while until it is corrected.