Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By mkl... Sat Aug 18, 2007 11:14 am
since nobody answered in the bug report topic, i post a new thread about it:

can you confirm this bug i've just discovered using loop mode and sliders :
1>take a quite long sample w(e.g. ride)
2>hit loop on
3>st : 00000 /loop (eg) : 00015000 /end (eg) :00035000
4>go to GPE (mode+pad11) assign your sample to a pad
5>set play mode to note on on this pad
6>go to slider mode (mode+pad1)
7>follow those settings : note on : s.end :100>track
8>press the assigned pad and let the sample play until it repeats try different q link values but when you're above 60 (between 60 and 100) there's a glitch where the first sample play and then another sample is taken randomly...

can you confirm this one guys?
User avatar

By mkl... Sat Aug 18, 2007 4:36 pm
wow 26 views no reply? how should i understand this?
User avatar

By Antonym Sat Aug 18, 2007 4:40 pm
i'll check it today if i get a chance mkll, sorry i couldn't do it sooner
User avatar

By rinseout Sat Aug 18, 2007 8:51 pm
I dont like the sticky, rarely look into it because you never really see if theres a new post. Also for more complicated bugs its hard to discuss them in there all at once.


No for your bug, i did the same, it doesnt play another sample, just some high noise (like a real short loop), but what should the mpc do if you move the sample end point before the loop start?
User avatar

By TBonus76 Sun Aug 19, 2007 2:01 am
rinseout wrote:I dont like the sticky, rarely look into it because you never really see if theres a new post. Also for more complicated bugs its hard to discuss them in there all at once.


I agree... having individual topics for bugs seems like a better way to organize, and it allows you to do a search on the topic names for bugs, instead of searching the text of all the posts in the sticky.
User avatar

By mkl... Sun Aug 19, 2007 11:20 am
the JJ team told me that they are going to correct this bug in the next os version :D