Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By sans soleil Mon Sep 10, 2007 1:06 pm
has anyone experienced this problem:

try to insert a mute command into a track (i.e. track 12) from step edit screen -> track mute gets written onto track 1.

i've also noticed that random mutes get written throughout a track...if i scroll through step edit, a track will have several 'mute ons' that weren't written in...doesn't really make a difference to the way the track will sound, usually (i.e. 'mute ons' will get written to a track that's supposed to be muted anyway), but still...
User avatar

By rinseout Mon Sep 10, 2007 8:51 pm
When inserting a track mute event its by default set gor track one, so it appears on track one.

When in track mute screen press overdub+play for each track a mute event will be recorded, so that might be the additional events you mentioned.
User avatar

By sans soleil Mon Sep 10, 2007 9:16 pm
ummm...that doesn't really make practical sense.

...so how would i go out about inserting a mute onto the track that i want (in step edit) ?
User avatar

By rinseout Mon Sep 10, 2007 9:27 pm
It would make more sense if you could choose the track when inserting the event, thats right. Just go to track one and edit the event, it will be moved to the appropriate track

By truvc Tue Sep 11, 2007 9:34 am
yes, track mutes are a bit of a mess.

also, in earlier os i am pretty sure one could mute the track containing the mute events, to stop having them being processed (which make sense since they are tracks events). now they always get processed (even if the track is muted...)

also i noticed a display bug: in step edit the mutes event are not always all displayed. then if one filter out the display of other events, then they appear.

i guess nobody is really bothered to report all that. and personally i do not use them. so it just stays like that :roll:

By jigginz Tue Sep 11, 2007 10:11 am
truvc wrote:i guess nobody is really bothered to report all that. and personally i do not use them. so it just stays like that :roll:


Truth is, most people will probably never get that deep into their MP, so a bug like that is not that important, or even known about!

When you start getting deep into the MP like that, I bet there's a load of bugs that have not ever been discovered......even by the JJ team.
User avatar

By sans soleil Tue Sep 11, 2007 12:23 pm
kinda surprised people don't use that...it's a good way to build up arrangements (recordable track mutes was one of the most attractive features of the JJos for me)...the fact that it doesn't really seem to work properly/logically is sort of aggravating.
User avatar

By hereo Tue Sep 11, 2007 7:11 pm
I don't know much about track mutes cause I haven't gotten that far yet, but the person who posted this should report it. Lets get rid of all bugs. I'm sure we all want a bug free OS, not just bug free on the stuff people "usually" use. Trust, you never know when that feature might come in handy. And someone else, currently or in the future, could want to use the feature only to run into a bug that didnt/doesn't have to be there.
I'm inspired to use Track Mutes now.
User avatar

By Antonym Tue Sep 11, 2007 7:13 pm
track mutes ride the short bus, i'd always rather just delete the stuff i want "muted"
User avatar

By hereo Tue Sep 11, 2007 7:23 pm
Is there a "Solo" option in Track Mutes. That would be cool for some drops and stuff.
User avatar

By rinseout Tue Sep 11, 2007 8:32 pm
Thats what i use "immediately play" for, copy your sequence, mute the tracks you want, then drop in/out on the next seq screen, rockz
User avatar

By hereo Tue Sep 11, 2007 10:50 pm
Word. That sounds like a good idea. Is that Seq option the one that starts the next seq from the start or the one that plays the next seq from the current position of the current seq? I always get the 2 mixed up.