2000xl erase problem

pchv wrote:Thanks for your trust, but I`m not insane ! They are the same here.

didn't mean that to imply YOU need to check your sanity.

it's just a term used to describe a test that is so basic you would think you shouldn't do it, but really you sometimes should just to make sure the basics are working as you think they are.

tapedeck wrote:didn't mean that to imply YOU need to check your sanity.

it's just a term used to describe a test that is so basic you would think you shouldn't do it, but really you sometimes should just to make sure the basics are working as you think they are.

I know. Just thought it was funny, because sometimes, you really wonder. This issue is so far out, I had to go through the procedure ten times, watching my fingers real closely, to make sure I didn`t do anything crazy without knowing.

tapedeck wrote:dose it erase the sounds on all tracks or just the track you are supposedly 'overdubbing' on?
also, if you are 'overdubbing'...are those new notes still getting in to the track?

Ok! I found out that it does erase on all tracks.
And yes, when I`m overdubbing, the new notes get into the track, but they aren`t "really" there since they don`t show up in step edit.

pchv wrote:Ok! I found out that it does erase on all tracks.

ok that's weird.

pchv wrote:And yes, when I`m overdubbing, the new notes get into the track, but they aren`t "really" there since they don`t show up in step edit.

well, if you have any swing or 'lateness' or 'earlierness' applied to the track, you wont see them when you hit 'step' because that might be locked to the grid.

there is a way to go directly between events in step edit - i believe it's 'go to' and 'step' left/right (where it says 'event' left/right underneath).
try that, and see if you can find those notes.
you could also be somehow looking at the wrong track?

again, these are just basic checks to make sure we are not crazy.

do whatever it is that causes the error, then get back to where you are in step edit and cannot see the notes, but they are still there.
then use the 'event' step keys (by holding down 'go to') and let's see if we can find these notes.

finally, if you are still having issues, i know this sucks, but explain how you do it button press by button press. i mean really break it down into too much detail like this..

1) press power button
2) hold shift button, press load button
3) hit up cursor three times, hit right cursor once
4) rotate wheel 3 times to select aps file
5) hit do it
....
etc....no need to document the loading process, just trying to explain the level of detail i need to see.
go ahead and load up a kick and a hihat, and start documenting from there as you go through the motions to generate the bug.
that or make a very detailed video - sorry im just losing track of exactly what you are doing.

Hey! Thanks a lot for taking your time to help me:) You`re being really patient.
Just one observation I made today: It doesn`t happen when it`s not triggered from PT it seems. I tried 50 times with the MPC not connected to any midi, and all worked fine. Then I tried with a daw called Anvil and a usb to midi cable, and it worked fine too. Then I went back to PT and my Mbox2 - bang! F...`d on first attempt. It`s no 100% proof, but I`m quite sure it only happens in PT. Will test it on a Digi 002 tomorrow.

tapedeck wrote:well, if you have any swing or 'lateness' or 'earlierness' applied to the track, you wont see them when you hit 'step' because that might be locked to the grid.

Yes, I have some swing on it, but I see all events before this happens...

tapedeck wrote:there is a way to go directly between events in step edit - i believe it's 'go to' and 'step' left/right (where it says 'event' left/right underneath).
try that, and see if you can find those notes.
you could also be somehow looking at the wrong track?

Not looking at the wrong track. I see the events before this point. I tried locating the notes this way, but they`re def gone.

tapedeck wrote:again, these are just basic checks to make sure we are not crazy.

Still sane, I think

tapedeck wrote:do whatever it is that causes the error, then get back to where you are in step edit and cannot see the notes, but they are still there.
then use the 'event' step keys (by holding down 'go to') and let's see if we can find these notes.

No notes. I noticed right now that when I switched windows between PT and Internet Explorer, the lost notes were gone soundwise too. As if I had saved the seqs, turned off the MP and loaded it again.

tapedeck wrote:finally, if you are still having issues, i know this sucks, but explain how you do it button press by button press. i mean really break it down into too much detail like this..

1) press power button
2) hold shift button, press load button
3) hit up cursor three times, hit right cursor once
4) rotate wheel 3 times to select aps file
5) hit do it
....
etc....no need to document the loading process, just trying to explain the level of detail i need to see.
go ahead and load up a kick and a hihat, and start documenting from there as you go through the motions to generate the bug.
that or make a very detailed video - sorry im just losing track of exactly what you are doing.

1) Set cursor at bar 162 in PT
2) Press "Overdub" on MPC
3) Press "Space" on keyboard to start PT, while holding "Overdub" down"
4) Release "Overdub"
5) Push pad3 (or any other pad) on the Mpc to record BD
6) Press "Space" to stop PT and recording after 8 bars
7) Press "Space" to play back what I have recorded. Seems fine....
Move cursor in PT to 163 and press "Space" - No sound

I get a feeling it might be PT or the Mbox2. Although I never had any issues with my MPC 3000. Have you heard of Mbox and 2000xl communicating badly?

dang dude - well unfortunately i am not a protools user, and i cant say i'd ever do things like where i'm holding buttons on one machine and hitting buttons on another machine - imo that is just asking for problems.

im afraid i wont be able to help much more, but at least by breaking it down into these smaller steps, you've found a clearer picture of what works and what doesn't work.

it sounds like some sort of sync issue - like i have experienced with logic, jumping around the timeline will make the loops in the mpc not start at the right place.

good luck

tapedeck wrote::?
dang dude - well unfortunately i am not a protools user, and i cant say i'd ever do things like where i'm holding buttons on one machine and hitting buttons on another machine - imo that is just asking for problems.

im afraid i wont be able to help much more, but at least by breaking it down into these smaller steps, you've found a clearer picture of what works and what doesn't work.

it sounds like some sort of sync issue - like i have experienced with logic, jumping around the timeline will make the loops in the mpc not start at the right place.

good luck

Thanks a lot, Tapedeck! Really appreciate it.
Can I ask you one last thing? How do you sync your Mpc to your DAW? If you have the music on the Daw and want to record drums on the mpc synced to that...

pchv wrote:Can I ask you one last thing? How do you sync your Mpc to your DAW? If you have the music on the Daw and want to record drums on the mpc synced to that...

generally, i never work like that. if anything, i would be adding the music in the daw after the fact...not vice versa. so i use logic's beat mapping to match the daw to my mpc-recordings. i do this with tape tracks a lot.

however, i have successfully synced my mpc to logic before. generally, i send the sync to the mpc, and if anything is 'off', i shift the events around in logic until it is right.

if i am running with the mpc synced to logic, say using logic as a sound module, then what i do is i hit play on logic and i let them run for a second, then if i need to overdub on the mpc, i hit the overdub button and press play - all AFTER i have started the sync via logic.
call me old fashioned, but i still think holding down overdub on the mpc while hitting spacebar on the daw is just asking for problems.

tapedeck wrote:if i am running with the mpc synced to logic, say using logic as a sound module, then what i do is i hit play on logic and i let them run for a second, then if i need to overdub on the mpc, i hit the overdub button and press play - all AFTER i have started the sync via logic.
call me old fashioned, but i still think holding down overdub on the mpc while hitting spacebar on the daw is just asking for problems.

I`ll try it! Hmm... bit of a disappointment
Maybe I`ll sell it and get a 2500 instead. The new ones should work

pchv wrote:Maybe I`ll sell it and get a 2500 instead. The new ones should work

id try it out first - the old ones are actually more robust as far as midi goes, seeing as that's what they were designed for.

having said that, a new os might be different in that one little way that makes it work correctly.

i dont think this is an mpc problem as that's a weird way to manifest a bug, but things like this...

pchv wrote:I noticed right now that when I switched windows between PT and Internet Explorer, the lost notes were gone soundwise too. As if I had saved the seqs, turned off the MP and loaded it again.

...make me feel like this is not a bug with the xl (hell at this point id say ie is causing the error ).
still, a new machine and new os might work - do what you gotta do to make it right.

tapedeck wrote:...make me feel like this is not a bug with the xl (hell at this point id say ie is causing the error ).
still, a new machine and new os might work - do what you gotta do to make it right.

It`s def not ie. I tested it in another studio on a digi 002 - same sh*t! And that machine doesn`t have ie.
Well... I`ll dig deeper into the problem. Will post if I ever find a solution

Have u tried MTC, not beat clock? Has been issues with this model when using beat clock and PT.

hallman wrote:Have u tried MTC, not beat clock? Has been issues with this model when using beat clock and PT.

Wow! You saved my life
Been recording with this setting for an entire evening, and had no problems. Thanks!!

glad to know that's what it was - it was mentioned early on that there were issues with midi clock but i guess t wasn't spelled out - 'try something other than midiclock'.

thanks hallman.

tapedeck wrote:glad to know that's what it was - it was mentioned early on that there were issues with midi clock but i guess t wasn't spelled out - 'try something other than midiclock'.

thanks hallman.

My bad. I need it spelled out in huge letters.