Share your knowledge on these two classic MPCs
User avatar
By Philly Stress Sun Apr 03, 2005 7:34 pm
IS THERE ANY ONE OUT THERE WHO CAN HELP ME WITH FOLLOWING QUESTION:

I started to Post this on another Board but I think this is the best place for
this question. When I use the Automated mixing function the MPC 3000
never seems to be able to record the beginning of the of the track correctly.

Say I record a fade in at 101.01 the fade won't start where I initially started it. The sound will play as if I didn't try to initialize a fade then Playback the Fade later than I recorded it!! What is the best way to record an automated
fade with my MPC 3000??

By elmacaco Sun Apr 03, 2005 8:15 pm
haven't used this yet on the 60, I usually do it in the computer, but try having a lead in of2 or 4 bars of blank, then do your fade in on time, see if that helps.

By mpc3000le Mon Apr 04, 2005 1:15 am
Don't Stress Philly :-)

Here is a thought...

Consider that with any "other" mid-sequence control changes, the mix automation changes too only take effect when played in a sequence.

This means that if you play a section of a sequence containing a specific controller event, the last played value of that controller will remain until another occurrence of the same controller is played, even if you stop the sequence and start playing it from another location.

Because of this, whenever you use one of these events within a sequence, it is important to insert another event of the same type at the beginning of the sequence to set the volume, pan or mixer/effects setting to an initial value.

Consider also that if you use overdub mode to add mix changes to a region of the track where previous mix changes exist, the old changes are not erased, but rather the new changes will be added in between the old ones, producing unpredictable results. :-(

For this reason, it is a good idea to record your automated mix data on its own separate drum track, then always use record mode (not overdub mode) to punch-in any mix changes.

This will automatically erase the old changes throughout the punch-in region, but since the mix changes are on a separate track, any drum notes will not be erased.

I hope this info is of some use to you.

Rohan.
User avatar

By Philly Stress Mon Apr 04, 2005 5:18 am
mpc3000le wrote:Don't Stress Philly :-)

Here is a thought...

Consider that with any "other" mid-sequence control changes, the mix automation changes too only take effect when played in a sequence.

This means that if you play a section of a sequence containing a specific controller event, the last played value of that controller will remain until another occurrence of the same controller is played, even if you stop the sequence and start playing it from another location.

Because of this, whenever you use one of these events within a sequence, it is important to insert another event of the same type at the beginning of the sequence to set the volume, pan or mixer/effects setting to an initial value.

Consider also that if you use overdub mode to add mix changes to a region of the track where previous mix changes exist, the old changes are not erased, but rather the new changes will be added in between the old ones, producing unpredictable results. :-(

For this reason, it is a good idea to record your automated mix data on its own separate drum track, then always use record mode (not overdub mode) to punch-in any mix changes.

This will automatically erase the old changes throughout the punch-in region, but since the mix changes are on a separate track, any drum notes will not be erased.

I hope this info is of some use to you.

Rohan.



I'll give this a try. Then I'll get Back to you!!

By mpc3000 Mon Apr 04, 2005 7:01 pm
"Consider that with any "other" mid-sequence control changes, the mix automation changes too only take effect when played in a sequence. "

Sounds like something as "scene memory" would be a nice addition to the OS. Press this into a particular location and all the sysex for the mixer would get dropped into the active track.

By mpc3000le Tue Apr 05, 2005 12:10 am
mpc3000 wrote:"Consider that with any "other" mid-sequence control changes, the mix automation changes too only take effect when played in a sequence. "

Sounds like something as "scene memory" would be a nice addition to the OS. Press this into a particular location and all the sysex for the mixer would get dropped into the active track.


Hmmm ... another one for the ever expanding project.
In the true sense of "scene memories", how many would be enough in your opinion ?

Rohan.

By elmacaco Tue Apr 05, 2005 4:05 am
any would be great, but I'd say 8 would be more than enough. 16 would be over kill.

but even one or two would be nice.