3k freezing on shifting notes...

I have experienced one or two 3k freezes in 3-4 years, which is okay compared to other machines stability...

Is there any way to rescue the 4 beats I made today? I was going to shift a percussion hit 2 ticks and now im stuck with the sequence> shift notes > shifting notes... busy screen.

I can still hit play and the red LED will light up, but nothing will play.
I'm pretty sure there is nothing I can do but hit the switch and start over again,
however if there is a chance so save these things with a "press this+this+that" thing to get out of this freeze?

.toon

...thought so

already rebooted my baby

to me freeze only occurs when i got midi time code to all 4 outputs.
- it slows down step editing
- sometimes the machine freezes.

i guess the cpu can't handle it. i think its a cool feature but before using it you should have everything saved to zip/cf reader.

i never got the mpc switching back from freeze without turning it off and on again. but i also noticed that some buttons change the columns and rows i see when it freezes. it could be possible to get it working again but i tried every button and i didnt make it.

Now that you mention it I had quite some after touch data recorded, perhaps it was too much to shift all these notes at once?

no clue


.toon

With the MIDI routing in your respective setups.

Are any of the MTC receiving devices connected back to your MPC3000 MIDI input and as a result, allowing an opportunity of inadvertent looped back MTC message streams to be present ?

This would potentially cause a system hang as a result of inbound/outbound message loop overflow.

Can either of you show your MIDI routing ?

IE: how various devices are connected and routed to and from your MPC3000 and what type of data is being sent to and from each respective port.

Let me know.

Cheers,

Rohan

I have my Motif XS7 hooked up to the 3000, with sync set to internal on the Motif and local turned off.
The 3000 is sitting on Sync=OFF. Sometimes I have the 3000 hooked up to my mac pro running logic,
but I havn't had a crash yet with this kind of connection

.toon

c.toon wrote:I have my Motif XS7 hooked up to the 3000, with sync set to internal on the Motif and local turned off.
The 3000 is sitting on Sync=OFF. Sometimes I have the 3000 hooked up to my mac pro running logic,
but I havn't had a crash yet with this kind of connection

.toon

Ok... That sort of gives me a sketch of how things are routed.

Can you tell me more about the sequence contents ?

How many tracks ?

How many note, events, event types and such per step, how many sequences in memory ?

What the MPC3000 sync out options were set to ? OFF like the sync reception options ?

Let me know on any points above if you can.

Cheers,

Rohan

Seems like I was running SYNC OUT back to the Motif with Clock and TC turned on.

I cant really tell you about the Tracks since I just powered the machine down, but I usually do the same stuff for my synth based tracks:

A couple of tracks with samples from the mpc ram for kicks and some percussion hits.
Triggering the Motif I'll have about 6-8 MIDI tracks setup with long notes, some repetitive stuff and a lead or two on top.
All these midi tracks are recorded via Motif Keyboard (Local off triggering back from the MPC into the Motif) with all data.

The amount of after touch and poly pressure is not incredible but I might have to adjust my MIDI input filter to reduce data overflow. I must admit I'm not too knowledgeable with this kinda stuff since I normally record my Synths directly into Logic.

I wish the 3000 would Sync properly with Logic releaving me of the MPC Loop vs Logic Timeline problem.

I'm not a 3.5 user btw, havn't had the time to rethink my setup yet and I'm not sure whether to add a 5000 to my setup for strong Midi production.

.toon

hoveone wrote:to me freeze only occurs when i got midi time code to all 4 outputs.
- it slows down step editing
- sometimes the machine freezes.

Likely if you have a MTC feedback loop in your system without realizing.

hoveone wrote:i guess the cpu can't handle it. i think its a cool feature but before using it you should have everything saved to zip/cf reader.

Maybe ... maybe not.

Is MIDI CLOCK and MIDI TIME CODE being sent out all ports at the same time

hoveone wrote:i never got the mpc switching back from freeze without turning it off and on again. but i also noticed that some buttons change the columns and rows i see when it freezes. it could be possible to get it working again but i tried every button and i didnt make it.

Assuming the system is apparently or seemingly frozen in this mode; try disconnecting all the MIDI outputs and/or the MIDI inputs.

If the system comes back from a hang in this instance then a MIDI feedback loop must have been present without your knowledge ...

Rohan.

c.toon wrote:Seems like I was running SYNC OUT back to the Motif with Clock and TC turned on.

A possible MIDI feedback loop then

Running MIDI CLOCK concurrently with MTC is NOT recommended as not all target devices can handle processing of these messages at the same time.

c.toon wrote:I wish the 3000 would Sync properly with Logic releaving me of the MPC Loop vs Logic Timeline problem.

Which is the master ?

What sync method are you using between LOGIC and the MPC3000 ?

Is your MPC3000 in pattern or song mode ?

Rohan.

hi rohan!
i messed up the words MTC and midi clock. i dont use MTC - i use only midi clock. when i send it through all 4 midi outs my system runs slower. i got no midi clock running back into the mpc. i use a moog prodigy, a sp-1200, a s950, a triton rack. only my master keyoard runs in the 3000. my sync in is set to "off" all time.

when you use the 4 x midi clock feature - don't you think that it takes longer to jump from 1 event to another in the step edit or to copy some events? if not i'd really wonder about some strange MTC feedback loop (although its turned "off" on my mpc).

Ok ... two different problems here.

C.TOON : Your freeze under 3.11 when shifing events in the timing correct screen could be to do with the following scenarios:

1: Your MPC3000 has on older than 3.11 OS in its ROM and you are booted to 3.11 from floppy disk. This scenario causes a reduction in sequence memory available and in some case can create some over all system instability.

2: Your MPC3000 work RAM is failing. ( this is not to be confused with the sample RAM )

In either case if you are prepared to email me the sequence that is causing problem I can analyze it for potential corruption ( or potential to corrupt ).

HOVEONE : Your feeling of machine slugginess with MIDI CLOCK going to all ports when stepping between event locations within the step editor is not easy to replicate here in my lab or by a few other users I have asked.

Looking at how your system is connected I would ask that you disconnect the master keyboard and any other devices from the MPC3000 MIDI IN. ( let me know what effect this has )

...and also, send me an example of a sequence that appears to be causing your some problems.

Rohan.