Lock chain in mixer view

smespresati · November 16, 2025, 11:31am

Hi guys,

I’ve been searching without results how to lock chains in mixer view, I mean a way to prevent selected chain to move when scrolling horizontally through the rest of chains. What I would like to achive is to get a specific chain to always stay just left side of main mix. Is this possible?

Regards.

jofemodo · November 16, 2025, 12:04pm

not possible yet
I’m sure you know the way…

riban · November 16, 2025, 12:57pm

As @jofemodo says, this is not currently implemented and would require a feature request.

It would be interesting to hear the reason you want to do this. It may influence and future implementation.

smespresati · November 16, 2025, 5:54pm

github.com/zynthian/zynthian-issue-tracking

Lock specific chain in mixer view

opened 05:43PM - 16 Nov 25 UTC

smespresati

Context. I use zynthian to play keyboard and guitar with my spanish folk band.… We are 7 singers 1 guitar and me (guitar and keyboard) all connected to a cheap chinese 12 channel mixer which only have 1 aux send for monitoring. We have 3 floor monitor connected to the aux send located in front of singers We don't have a sound guy so we cannot change anything of sound when playing. I use zynthian outs as dual mono, left channel goes to mixer and right channel direct to my personal monitor . I mostly play comping but sometimes I have to play solo, that's why I need to manage left channel volume. To achive that I have 2 chains whith Calf Stero Tools (one panned all the way left and the other all the way right) to which I route all other midi and audio chains. I also have a pedal connected via **m-vave chocolate plus** midi device which control Calf Stereo Tool volume left chain. Feature request. The snapshot may have a douzen of chains and when scrolling may happen that one important chain is not visible. It would be good to have the possibility to lock one (or more) chain in order not to move when scrolling. I think this way you can easily check what you need.

Hi @jofemodo and @riban this is the feature request. There I explain my use-case and how I managed it. The feature request I made will help me a lot (I think to others too).

Perhaps is not the clever way to manage the issue but I didn’t find any better.

Regards