4.68 bugs?

Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
 Reply Share on Facebook
User avatar

4.68 bugs?

By Antonym Fri Jun 08, 2007 4:11 pm
i spent all of yesterday on 4.68 and the day before on 4.67

i have literally been LIVING in my mpc, to the point where all i ate all day was rice cakes. i have a nice little job where i get to help a film crew build there set and run camera/audio for their shoots. yesterday/day before were off days so i didn't have as much to do (a little floor painting/camera chipping but otherwise i just got to make beats).

anyway, i didn't find bugs, and i was doing a LOT of midiing, loads of grid editing, and intense slicing/program building.

however, i believe it was freezerman in response to balls' post, referred to the start point slice mark in SLICE. if we could create a 1,2,3 for that, that'd be great.

as well as anything else yall find consistency wise or bug wise. cyclops, any word on the grid edit pictures?

CHUPACABRA: i'm going to suggest a WHOLE button on the GPE Velocity Layer program page as well with a picture. anything i'm missing here?

finally:

2. [GRID]
　　TAP TEMPO + Data wheel turn to right.
　　Two or more bras are chosen.
　　TAP TEMPO + Data wheel turn to left.
　　Cursor is not displayed correctly.


this has REALLY taken weight off my shoulders. i've been loving being able to "reverse select" in grid edit without worrying about a weird cursor/incorrect display.

rock on
nym
User avatar

By H-Mann Fri Jun 08, 2007 6:09 pm
I just reported this on JJ's site:

1. power on -> load or record sample
2. go to [TRIM] mode
3. press F3 (Zoom In)
4. adjust start point with jog wheel
5. press F2 (Zoom Out)
turn jog wheel
--> BUG: Start point jumps back to 0000000
-> in graphical display you can see it after zooming out
-> in numerical display you can see it after turning the jog wheel

notes:
-same problem with end point
-bug does not happen when using slider to adjust start/end point



I also have an issue with the HDD spinning up when changing modes (causes delay in playback). Reported that yesterday in a similar manner.

Peace
User avatar

By Rise of EPC Fri Jun 08, 2007 6:43 pm
H-Mann wrote:I just reported this on JJ's site:

1. power on -> load or record sample
2. go to [TRIM] mode
3. press F3 (Zoom In)
4. adjust start point with jog wheel
5. press F2 (Zoom Out)
turn jog wheel
--> BUG: Start point jumps back to 0000000
-> in graphical display you can see it after zooming out
-> in numerical display you can see it after turning the jog wheel

notes:
-same problem with end point
-bug does not happen when using slider to adjust start/end point



I also have an issue with the HDD spinning up when changing modes (causes delay in playback). Reported that yesterday in a similar manner.

Peace


excellent

By truvc Fri Jun 08, 2007 9:23 pm
true there are very few bugs left. and only really minor ones.
i believe i got a couple + maybe inconsistencies.

I will try to have a go at it and post it at the week end. (before i go to sonar :P )
User avatar

By Rise of EPC Sat Jun 09, 2007 8:32 am
TURN ON
load drums
make a loop (4 or 8 bars is what ive tried)
go to track 57 (shift +F4)
direct record a loop (ANALOG ST input)
****DOES NOT SOUND RIGHT****
go back to drumtrack (shift + F3)
go to MODE -> STEP EDIT (PAD 14)

****NOTICE SOME NOTES/PADS RECORDED AT SAME TIME*****

some are even tripled up...

EX: 001.01.00 PAD : A06 (32) etc. etc.
001.01.00 PAD : A06 (32) etc. etc.
001.02.00 PAD : A10 (41) etc. etc.
001.02.00 PAD : A10 (41) etc. etc.
001.02.00 PAD : A10 (41) etc. etc.


i just reported it to J J 's site
and what is wierd.. it did DELETE my recorded info... not double.
but when i tried to reproduce it .. it doubled notes... hm.
hopefully he finds the lil glitch
User avatar

By TalkingHats Music Sat Jun 09, 2007 12:55 pm
SONG MODE is completely **** for MIDI CLOCK AND MIDI TIME CODE,


in Midi Clock, the locate does not follow the master location signal
for example if i have the mp in song mode and cubase is located further down in the song say 16.02.00 the mp will not go to that point,

the mp is not following the midi signals.


it locates in midi time code but does not start form the beginning, kind of a lag, or offset gone wrong.

i am a bit baffed to be honest on how to address this to JJ. his bug request form leaves it slightly difficult for me to explain.

also i have back tracked this through all the previous os' and they all have this problem.

By truvc Sat Jun 09, 2007 2:05 pm
TalkingHats Music wrote:it locates in midi time code but does not start form the beginning, kind of a lag, or offset gone wrong.

ok, the lag is the bug.
i think midi clock is not meant to locate at all.

what about that ?

1: set mpc as MTC slave.
2: set cubase as MTC master
3: start cubase
4: bug: mpc starts from 00:00:?? instead of 00:00:00

btw better you email JJ (rather than the bug report form) so then he can reply to you.
User avatar

By distortedtekno Sun Jun 10, 2007 7:44 pm
Rise of EPC wrote:she hasnt froze on me in FOREVER!.
direct recording is messed up again.
after recording take03 i tried editing the wav.
and it wasnt there... there was a ??? for the endpoint and no visual of it.
i tried adjusting the ??? and it scrolled down to this page :(
i had a sickkkk hook scratched in place too.. :(

jj please save direct recording

Image
User avatar

By distortedtekno Sun Jun 10, 2007 7:45 pm
TalkingHats Music wrote:
truvc wrote:
TalkingHats Music wrote:it locates in midi time code but does not start form the beginning, kind of a lag, or offset gone wrong.

ok, the lag is the bug.
i think midi clock is not meant to locate at all.

what about that ?

1: set mpc as MTC slave.
2: set cubase as MTC master
3: start cubase
4: bug: mpc starts from 00:00:?? instead of 00:00:00

btw better you email JJ (rather than the bug report form) so then he can reply to you.


midi clock has always located where ever i move it on the master, has done form os.2.1 and before, same with other versions of the mpc.
so JJ needs to sort it out!! i use this feature everyday and its a pain to have to now manual locate the mpc back to the begining in song mode, when it used to just follow the master midi clock location.

pissed!

yeah i will email him!!
User avatar

By distortedtekno Sun Jun 10, 2007 7:46 pm
truvc wrote:
TalkingHats Music wrote:
truvc wrote:
TalkingHats Music wrote:it locates in midi time code but does not start form the beginning, kind of a lag, or offset gone wrong.

ok, the lag is the bug.
i think midi clock is not meant to locate at all.

what about that ?

1: set mpc as MTC slave.
2: set cubase as MTC master
3: start cubase
4: bug: mpc starts from 00:00:?? instead of 00:00:00

btw better you email JJ (rather than the bug report form) so then he can reply to you.


midi clock has always located where ever i move it on the master, has done form os.2.1 and before, same with other versions of the mpc.
so JJ needs to sort it out!! i use this feature everyday and its a pain to have to now manual locate the mpc back to the begining in song mode, when it used to just follow the master midi clock location.

pissed!

yeah i will email him!!

ok, you found two bugs then. make sure it is clear that there are 2 bugs otherwise it will confuse jj.

bug 1: MTC slave have an offset at start.

bug 2: locate problem using midi clock slave. sounds like the mpc is not reacting anymore to Song Position Pointers (which can be sent with midi clock, i had forgot about those).

btw, do you know if these things work when the mpc is master ?
User avatar

By distortedtekno Sun Jun 10, 2007 7:49 pm
Sorry to delete some posts and quote them here.
I tried to split the topic by request due to the complications of the pan bug, but it got messed up. :oops:
carry on.

Re: 4.68 bugs?

By cyklops Sun Jun 10, 2007 8:36 pm
Antonym wrote:

as well as anything else yall find consistency wise or bug wise. cyclops, any word on the grid edit pictures?

.

rock on
nym


this week Ant :)
User avatar

By TalkingHats Music Mon Jun 11, 2007 12:32 am
distortedtekno wrote:
truvc wrote:
TalkingHats Music wrote:
truvc wrote:
TalkingHats Music wrote:it locates in midi time code but does not start form the beginning, kind of a lag, or offset gone wrong.

ok, the lag is the bug.
i think midi clock is not meant to locate at all.

what about that ?

1: set mpc as MTC slave.
2: set cubase as MTC master
3: start cubase
4: bug: mpc starts from 00:00:?? instead of 00:00:00

btw better you email JJ (rather than the bug report form) so then he can reply to you.


midi clock has always located where ever i move it on the master, has done form os.2.1 and before, same with other versions of the mpc.
so JJ needs to sort it out!! i use this feature everyday and its a pain to have to now manual locate the mpc back to the begining in song mode, when it used to just follow the master midi clock location.

pissed!

yeah i will email him!!

ok, you found two bugs then. make sure it is clear that there are 2 bugs otherwise it will confuse jj.

bug 1: MTC slave have an offset at start.

bug 2: locate problem using midi clock slave. sounds like the mpc is not reacting anymore to Song Position Pointers (which can be sent with midi clock, i had forgot about those).

btw, do you know if these things work when the mpc is master ?



because its always recommended never to have cubase as slave, i would not know if having the mp as master would resolve, especially the way i work.

Sorry,

Btw his email is on the site right?
User avatar

By rinseout Mon Jun 11, 2007 9:58 am
I always use cubase as slave, just insert anempty bar in the beginning of your seq.

By truvc Mon Jun 11, 2007 10:18 am
TalkingHats Music wrote:Btw his email is on the site right?

nope, it should be in your mail inbox and paypal account (thats the email you used to pay him the $30).
 Reply
Return to MPC1000/2500 JJ OS