Mutes in scenes?

vinja · 2015-10-09T15:46:02.000Z

+1 as well! Applying all those volume changes is bummer and you use up all the available scene/performance locks so quickly.

bauer · 2015-10-09T15:53:28.000Z

""vinja"":

+1 as well! Applying all those volume changes is bummer and you use up all the available scene/performance locks so quickly.

you can lock multiple tracks VOL in a single scene/performance pad - i think each pad can lock 40 parameters or thereabouts?

the main issue for me in using track vol to mute/unmte is that you have to be spot-on with your timing, or you end up cutting off/cutting in on the tail of sound/s, which can sound crap

using the ‘real’ mutes avoids the issue with tails - trigs only play if the track is unmuted when the sequencer hits them. this is why it’d be great to be able to plock the actual track mutes, or some other way to silence them, which stopped them trigging - maybe by letting the perf/scene pad plock the track masks on/off?

mute groups could also be a solution - i can see an easy-ish wat to implement thing by using the FUNC + PAD method in the mutes page, similar to the way the perf and scene editing is done…?

that said, i won’t hold my breath on this one. work around and hope something comes down the pipe to help us, but don’t count on it

vinja · 2015-10-09T16:12:14.000Z

""bauer"":

[quote=“vinja”]+1 as well! Applying all those volume changes is bummer and you use up all the available scene/performance locks so quickly.

you can lock multiple tracks VOL in a single scene/performance pad - i think each pad can lock 40 parameters or thereabouts?

the main issue for me in using track vol to mute/unmte is that you have to be spot-on with your timing, or you end up cutting off/cutting in on the tail of sound/s, which can sound crap

using the ‘real’ mutes avoids the issue with tails - trigs only play if the track is unmuted when the sequencer hits them. this is why it’d be great to be able to plock the actual track mutes, or some other way to silence them, which stopped them trigging - maybe by letting the perf/scene pad plock the track masks on/off?

mute groups could also be a solution - i can see an easy-ish wat to implement thing by using the FUNC + PAD method in the mutes page, similar to the way the perf and scene editing is done…?

that said, i won’t hold my breath on this one. work around and hope something comes down the pipe to help us, but don’t count on it
[/quote]
True, and if I want a scene to essentially solo a track, (and I have one or two scenes like that on a pattern) then you quickly eat up all avail locks. I guess my frustration is with the limitation itself, but allowing scenes to mute/unmute would be awesome (although I’m thinking its a pipe dream as well )

Rael · 2017-01-16T19:54:09.592Z

This would be sooo useful
I hope this gets implemented one day

stutech · 2017-01-16T20:20:17.849Z

You can remote control both scenes and mutes. Not ideal but if you don’t mind mind an extra controller, works really well.

AdamJay · 2017-01-16T20:23:29.770Z

“Scene select” is on a single CC#, so it is simple, one MIDIknob/fader assignment.
I did this often with my JLC FaderMaster, but eventually got fast enough at moving between the scene and mute page that it was unnecessary.
And that’s my advice - do some drills, get fast!

Lieder · 2019-04-16T00:31:17.000Z

I’m trying to figure out how to use scenes to mute triggers on tied tracks.
I know you can reduce the volume all the way down effectively removing it from the mix but the trigs still trig which will still negate a trig on the tied track (ie the hats).
Any ideas?

safetyofobjects · 2019-04-16T17:09:53.137Z

chain/song mutes could be of use to you

Lieder · 2019-04-16T23:32:25.943Z

Standalone they would be but I’m using the dark trinity and the OT is handling the song arrangement.

Open_Mike · 2019-04-16T23:36:53.786Z

Scenes won’t work for that.
In your case you can use an OT midi track and send cc 94 (track mute) on the appropriate track channel, I’m not sure if it’s any value=mute and then after any value=unmute, or perhaps a certain range will mute and the rest will unmute, haven’t tested…

Lieder · 2019-04-17T13:59:39.158Z

That was how I had it setup previously but the issue is OT doesn’t have enough tracks to cover all 12 mutes on RYTM.
I get why Elektron chose the same cc for mutes and you can use different channels per track but different ccs per track on the same channel would’ve been a better choice in my opinion.
I have a Korg Radias that actually allows you to define what CC a parameter is. That would be fantastic if Elektron allowed that. Perhaps a future OB update would allow it…

Open_Mike · 2019-04-17T15:31:24.839Z

The only way I can think of at the moment besides programming AR song mode the same as OT arranger and automating mutes there would be to set up 8 midi tracks for the tied tracks and have one of those tracks also send a scene cc where the scene mutes the rest of the tracks. There goes all your midi tracks though unless per OT part you know you’ll only need to mute and unmute some of the tied tracks…

tnussb · 2019-04-17T15:52:17.301Z

To just mute single trigs as @Lieder wants (very short mutes) this is quite some effort …

Open_Mike · 2019-04-17T15:56:01.645Z

That’s how I read it at first too… Almost sugested looking into trig mutes which is an AR feature…
But… On AR the choke track’s trigs interfere with each other unless you mute and unmute them with the pads or CC’s, which basically trig mutes the entire track. He wanted to mute entire tracks using a scene targeting amp vol but that doesn’t work as the track trigs still interact…

Jacknoid · 2020-06-21T13:33:53.536Z

Bumping this up to the top again as surprised this still hasn’t been implemented by Elektron!

Could be pretty simple, auto channel CC number 94, instead of it being a toggle between 127 and 0 to mute and umute the currently selected channel, you could just have a series of toggles for all pads instead, e.g;

0 = BD1 unmute
1 = BD1 mute
2 = SD2 unmute
3 = SD2 mute
4 = RS3 unmute
5= RS3 Mute…
etc.

This would be great (for dark trinity workflow) as you could use the Octatrack conditional triggers to switch between mute states all within one pattern, no need for song mode. This would be so much better than the current workaround which is to use up patterns in the octatrack just to build up patterns.

The only other current workaround is to have the Rytm as the master and run song mode from that, which isn’t ideal for lots of reasons

Lieder · 2020-06-21T14:25:54.126Z

A workaround I use is to use scenes as mutes. Just plock volume under AMP (and LFO if it’s been assigned to volume).
CC92 I believe, value 0-11 for scene 1-12.

DanJamesAUS · 2020-06-21T14:55:48.668Z

I would also like to see mutes per pattern to make forming a song structure easier
maybe Something that could work is when in mute mode pressing page could swap mute modes
from the green mute mode to the yellow
It works so well on the digis would be great to get it ported to the analog series as well

johngredin · 2020-06-22T15:02:31.950Z

Already there in song mode

DanJamesAUS · 2020-06-22T15:06:03.120Z

johngredin:

Already there in song mode

not much use if you have it receive program changes for patterns from the octatrack…
could mute and unmute differnet patterns without having to delete them

DanJamesAUS · 2022-01-11T10:40:39.711Z

we already have trig mutes why not hit the pads to mute the whole lot
the top tier analogs get less attention than the digi series…
sound locks dont even work! cmon bro!