Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By bobbybland Sun Mar 01, 2009 12:16 am
Noticed the same thing on jjos2xl > v1.11 I sent bug report.
By bobbybland Mon Mar 02, 2009 5:24 am
jj responded with -> It's deleted.
Please use down main volume.
By dtaa pla muk Mon Mar 02, 2009 5:28 pm
there's no point in this option, hence the removal.

either use a blank pgm with no pads loaded or turn the main volume off
the first of those two suggestions is the most logical
why would you load sounds if you were going to turn pad to internal sound off?

folks have been using blank chromatic pgms to do this for years
User avatar
By Sooty_G Tue Mar 03, 2009 3:59 am
Nym wrote:why would you load sounds if you were going to turn pad to internal sound off?


so you can play your beats from the MPC, and then use the pads as a controller to play some external midi gear simultaneously. 'pad to internal sound: off' does NOT mute the recorded events from playing back, just mutes your realtime pad playing. this is why JJ's "turn down the sound" comment shows he didn't get it.

it's a neat little feature to have. it saves you from having to have a separate pad controller or keyboard or whatever to play your synth module or trigger whatever else you might have midi'd up to the MPC.

the one solution to this in XL is to create a blank MIDI program on a new track and make sure you keep that track active. then you can play your external gear while your sequence plays back.

the drawback to this is that you have to stay on that track while you play. if you move off it (say to q-link tweak another track as it plays) then you will lose contact with your external gear via the pads. if you don't want to deal with that limitation then you can use either os 1 or 2.
By dtaa pla muk Tue Mar 03, 2009 5:35 am
the one solution to this in XL is to create a blank MIDI program on a new track and make sure you keep that track active. then you can play your external gear while your sequence plays back.


create multiple blank pgms routed to multiple midi outputs and switch between these tracks while leaving the MPC internal sound tracks untouched... this is no more difficult

or better yet, incorporate a laptop into this already complex live setup...and probably take an enormous weight off your other gear at the same time
User avatar
By Sooty_G Tue Mar 03, 2009 6:41 am
Nym wrote:
the one solution to this in XL is to create a blank MIDI program on a new track and make sure you keep that track active. then you can play your external gear while your sequence plays back.


create multiple blank pgms routed to multiple midi outputs and switch between these tracks while leaving the MPC internal sound tracks untouched... this is no more difficult


that is what i just suggested. i'm assuming only one piece of external gear besides the MPC so that's why i only mentioned 1 MIDI track.


or better yet, incorporate a laptop into this already complex live setup


don't know what's so complex about 1 synth midi'd to 1 mpc. really no need for a laptop there... unless you enjoy watching it crash / get damaged due to heat, moisture, vibration, software fukcup, etc...
By dtaa pla muk Tue Mar 03, 2009 6:45 am
no more so than any other piece of gear. dunno what bad experience you've had with a laptop to warrant such distrust but my 2nd hand dell latitude d400 has survived extremely rough treatment including multiple bike wipeouts + daily elementary school beatdowns without any embarrassing crashes

i've had many more reasons to expect failure from music hardware than my PC running respectable softwares
User avatar
By Sooty_G Tue Mar 03, 2009 7:26 am
Nym wrote:no more so than any other piece of gear. dunno what bad experience you've had with a laptop to warrant such distrust but my 2nd hand dell latitude d400 has survived extremely rough treatment including multiple bike wipeouts + daily elementary school beatdowns without any embarrassing crashes


damn! definitely the exception rather than the rule. that laptop is truly blessed. don't ever get rid of it.

i've had many more reasons to expect failure from music hardware than my PC running respectable softwares


that's actually kind of sad. i think you need better hardware! :lol:
my experience has been the opposite (hardware much more stable than laptop) and i think most would agree but who knows.

from my perspective, a laptop is much too sensitive structurally & too expensive to bring to live gigs. plus software & all the other unrelated OS stuff running behind the scenes... just asking for trouble. i'm much more productive with a hardware setup.
By JaeOne3345 Sun Mar 29, 2009 5:15 am
I miss this feature also.

Sometimes I use a different sequencer but like to use the samples in my MPC as an external sound source, but at the same time use the pads to control other gear connected to the "different sequencer."

Say if my "different sequencer" is triggering the MPC program currently loaded. When I switch to the new track that has a blank program, the other program is no longer triggered. You all say turn down the main volume, but if using the MPC as a module, the samples can no longer be heard.

One OS1 and the factory OS allow it so that there is no need to go to a different track. I might keep my MPC on receive channel 1. But my Sp-1200 may be on channel 2. If I have the internal pads disabled, I can use the current track on the MPC to send data out to the external sequencer. The external sequencer is able to route its information to either channel 1 for the mpc or channel 2 for the sp-1200. When set to the channel 1, the external sequencer triggers the mpc internal sounds, but on 2, it triggers the sp-1200, but all from the mpc pads.

Someone might not understand it unless you have tons of outboard that you like to use. I've been just using an old MPD to get around this while I use JJ OS2xl.

I don't think many people, including JJ, understand the use of this feature. If the mpc was a multi-timbral device that allowed different programs to respond to different channels, it wouldn't be an issue.