|
Support |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() |
This actually sounds like the preferred mode to me...
-Miko
>>> Matthias Grob <matthias@grob.org> 06/02 10:22 AM >>>
>Yes, I have found myself wanting a solution to this situation too.
An
>alternate idea to the new command solution would be that whenever a
muted
>loop is exited, the next time one comes around to it, it would be
>automatically unmuted. Muting it would be by request only
(Next-Mute).
Ok, sounds easy, maybe better to operate since you dont need to
remember which loop is muted and which not. I think I had it like
this once and then found it inconsistent in case of not quantized,
where you dont have time to press Next-Mute. But it still might not
make sense to come back to a muted loop.
What do other users think of this solution?
>Eric Zang
>www.listen.to/zang
thats a cool URL!
---> http://Matthias.Grob.org