to lock the mute state per pattern (as with the effect lock per pattern) and save those locks (on a pattern basis!):
this would greatly increase the flexibility/possibilities for jamming live performances!
to lock the mute state per pattern (as with the effect lock per pattern) and save those locks (on a pattern basis!):
this would greatly increase the flexibility/possibilities for jamming live performances!
or maybe midi control over the mute screen… or the pattern screen. i mean we have so many inputs over usb now
that would be an option as well..
however, i would strongly prefer to have it inside the Hapax:
While The Hapax is really great on (Midi) FX etc I would love to have more performance/arrangement orientated features like eg mute locks, pattern locked loop points/ or count ins or, to put it more general improved realtime orientated (one handed..) mute/solo options in the pattern screen.
Mixmute is great, but you always have to change to that screen, so youre just loosing all the options that you have in the pattern screen…
In my opinion that’s where I still see the greatest potential for improvement for the Hapax.
(which is nonetheless already a really great sequencer! :-))
yeah i said midi control over mixmute so you could be in another screen and still have control over it as well. but yeah its different from writing it into an arrangement.
got you
if squarp gave us cc control over mixmute and loopback, you could then create a cc event in a sequence to mute tracks… as long as you didnt mute your mute track! and the mute track would only be as long as your midi track. this would work best with midi input from another sequencer like an mpc or something. i know some people must be looking at this and wondering why you would want to remotely control a sequencer from another sequencer but i definitely see the potential benefits.
btw renoise and redux allows access to sequences and mute states with simple midi notes and cc, and will also capture your note sequence from hapax. you can then layer several phrases over each other with simple note commands. you can even do this kind of thing with pure automation sequences. i would toally love it if hapax were to expand in this direction, i feel meta sequencing is the way forward since it really hasnt been done much in hardware. there have been a few that allow external control such as zaquencer. supposedly pyramid lets you control whats playing from external midi. do you know of other hardware that does this?
have you considered using midi volume commands to ‘mute’ tracks? my peavey pc1600x will let me send scenes with simple midi note commands or program change commands… could be good for multitimbral synths. it works well with reaper! but you could write those into a hapax pattern even now. you just need to remember to turn volume back up with another command.
Is this about MIXMUTE mutes or pattern mutes?
What’s the point of current pattern mutes implementation anyway?
It’s very limited. Kind of equivalent of changing a given track to an empty pattern.
It would be useful if we could mute patterns without switching to them.
So a single row of patterns is playing, but then before changing to a next row / section, we could mute a couple of patterns in advance, while that their tracks keep playing in the current row, but don’t play once we move onto the next row.
And of course stay muted, until manually unmuted and allowing any number of patterns on a given track to be muted.
@RadekPilich Its about the Pattern Screen.
The goal is to improve the mutes on it, that you a) dont have ton switch alway to the Mixmute screen and b) give an additional layer to expand the arrangement/songwriting possibilities.
With Mute Locks on patterns you could store the mute state of a specifc pattern and unmute it during the performance (so you dont have to manually chose or place an empty pattern).
That could for example be accessed by pressing SECOND + MUTE to show all the current mutes and manually mute patterns.
Yeah there are/would theoretically be some more advanced options (eg. im also using an external controller to mute with velocity on certain tracks) but those are a) use external gear and b) much more complicated (given the limited internal routing options we currently have).