Mute group across different tracks

this was posted by Cyrus in the bug fixes a while ago - ive noticed it still seems to be apparent in OS2XL ver 3.16.. Im wondering if there is an option somewhere that i dont know about.. Or if it still hasnt been fixed?

"mute groups messed up. jjos2xl v2.30 - they are not working cross track even though the same program is used.

1. assign Program 01 on track 1 and track 2
2. make all pads assigned to mute group 1.
3.record pad A01 event on track 1
4.go to track 2 (uses same program),
5.play sequencer
6.press arbitrary pads part of mute group 1 and Program 01 on track 2
7.mute group does not work

how it should work, and has in the past:
regardless of what track you are on, mute group should work for all tracks that use the same program, mute groups are not track dependant, they are program dependant"

im answering my own question here.. but ive since heard from JJ that it cant be done at present with version 2 up of XL.. just thought id post in case anyone else comes across this issue and wonders about it.

A bit of a shame as it was quite a useful feature in the older versions and i hope an option comes into a future OS to have mute groups extending across tracks or not.

argh!!

You know I read this and thought to myself, that I actually prefer it working this way. I find it very useful. I know what you mean by program dependent but after using it for a while I find it very useful to layer stuff that I have done. If I need a particular sample muted, I use appropriate track but it does not interfere with other tracks that are using same program as well and have muting going on

I'm not sure now, but I think it supposed to work across the tracks. Like having two separate tracks with the same program, and they will sound different when I merge them to one? No way.

Bugfix wrote:I'm not sure now, but I think it supposed to work across the tracks. Like having two separate tracks with the same program, and they will sound different when I merge them to one? No way.

Nah this way is way better as it gives you a choice and it still works but on that track. If you really want to you can always paste the tracks together, and then this will work like you want it to. If you think about it it gives you so many more options this way so IMO its killer

Really bliprock, I ain't got any point to arguing what's better. Just wanted to point out inconsitency, as you working this way now, and if few people send a report about that, all your work will be ruined because of that. That's all I mean here, compatibility.

yeah having played with it a bit now ive concluded theres pros and cons to both, on the one hand it now functions much more like a standard multi track DAW being able to achieve thicker layering but it loses a certain level of instrumentality that comes with being able to create a new track that will mess with the tracks that are already playing.. I only discovered it had changed quite recently just cos i went into some old sequences that sounded way different now as a result.

i like the idea of copying tracks into each other so that the muting works, but that slow things down a bit.

in terms of reporting it. all i would really hope for is an option to turn mute group across different tracks on or off..but from what i can gather it sounds like this isnt a particularly easy thing to do from the way OS2 is set up.

meh - just got to adapt to it

yeah you make some fair points. Consistency and compatibility are good things to bear in mind yes, that is true. No one likes having to redo stuff, even me, but I just use pad move function. I find it more difficult remembering what I did and figuring out what I did three months ago to fix it, and do not even know if the outcome is the same, but doing this I did actually feel that it was an improvement in that I could choose what pads I wanted muted by track. This and pad move meant I could alternate muting easily and still drop in things like note repeats that muted in a program on that track. I found the most work was in thinking what I want muted, not the actual time on the MPC. I mean just thinking about what I want muted and building it up that way means more consideration than before. If this is done then its great, but yeah can understand that you would want to have all tracks with said program to react the same with muting.

Another method would be just to copy actual performance that you want that is muting and copy this to other track you want the same muting effect, with pad move or whatever, and drop velocity to zero, creating a ghost hit, and so then acts as the mute for other track and it wont be heard at all. invisible ninja notes like this can help, and its easy as to do pad move from grid edit.

Nice. Some good workaounds there.. Yeah it's not the end of the world it seems. Good ol ghost hits.

I've found if I reinstall back to (edit OS 2) I can get the effect for certain sequences where I want it to happen on the fly. I find it really useful for longer musical samples like classical guitar sounds awesome with the muting chopping effect.. And then I can use your method to merge them into os2 compatible version if necessary to maintain the effect.

Cheers for the suggestions

cool, anytime. Glad I could help you keep chopping. I had my full level set to 1 for the ghost notes to, that helps. Except when you forget and wonder why you can not hear anything

I have a similar issue, I have set a program to mono so all sounds cut off each other, but if I use the same program across multiple tracks they can play multiple notes. So it seems a mono program is only mono on one track, and if you use another track with the same mono program you will not cut off sounds across the tracks.

Does anyone know if there is a setting to make a program mono no matter which tracks the data is coming from?

to me this doesn't make sense in practice, since they are referencing the same program, the mono program should only play one pad. It should at least be selectable at the program level, multi track mono or single track mono.

Am I missing something?

elmacaco wrote:to me this doesn't make sense in practice, since they are referencing the same program

+1

and the thing is they say it will be like that

In OS2XL, even if it is using the same program, other tracks are not influenced.
It is clearly written in the following link.
http://www7a.biglobe.ne.jp/~mpc1000/os2xl/

Damn. I blame the multitibral mode implementation.

Was there an earlier 2XL version that didn't behave this way, or is it just OS 2 and lower?

Since it seems a fair amount of the mpc 2500 jjos xl user base use this as their "typical work flow", can we just agree to show a sign of unity and ask for this to be an option in a feature request? This is one of my biggest limitations right now and its forcing me to drop the whole beat in a single sequence. Huge bad workaround.