Monome & Renoise 2.6

[samBiotic]

@danoise

If I understand you correctly, the problem is to translate the matrix slot states to a device with just on & off? Remember, the Launchpad has 15 colors to choose from, which makes it pretty simple to illustrate a empty+muted slot, etc. On the monome, there’s really no right or wrong way of doing this, but I found it most practical to be able to distinguish between muted/empty and active slots - you can change this to your own desire, by editing the matrix palette (colors with an average above 0x80 will be lit on the monome).

I’ve figured out that this means by default that if a pattern isn’t blank and is not muted then the corresponding led will be lit.
My initial testing was just with a blank song so I was too early to criticise the lack of visual feedback.

@danoise

This is something I’ve got planned - an alternative to the basic slider the matrix currently has. UISeqControl, or something like that…

awesome.

@danoise

There’s already a mechanism in place for following the song-position when global song-position follow (SCROLL_LOCK) is enabled. However, it could be expanded to follow tracks as well. Once this is in place, you can simply configure the device to use the entire surface for the matrix (as determined by the controlmap + mappings).

track following on the mixer and automatic horizontal matrix scrolling based on the screen cursor would be great.

@danoise

Absolutely - they are two different things. Muting the channel will be the same as telling the instrument to stop playing, but the release and effect (reverb tail, etc) will still be playing. Turning down the volume, on the other hand, will do what it says. Think of it as the difference between a conductor telling a musician to stop playing, or a producer muting a certain track on the mixing console.

ok, understood, so long as duplex is set up to control prefx volume i can see the distinction.

@danoise

By default, F1/F3 are already assigned to view presets in Renoise, but I get the idea, and it would definitely be easy to implement! Even better - to have global shortcuts on the controller?

The reason I suggested a link between view presets and duplex was that I more often than not I found myself with the pattern editor on screen when using the matrix and with the mixer on screen when using the… erm mixer on device.

So the way i saw it working was that you could navigate to the thing you wanted to use on screen then control it on device straight away, (kind of like the way the a nocturn speed dial knob works but for more controls at once) and was the reason I was asking about something like renoise.app().window:select_preset_observable on the api wishlist thread
when I was building my own monome tool.

Many users may be wanting device only performance so having a button press sequence that wouldn’t normally be pressed accidentally like hold bottom left and press bottom right for config switching right and opposite for left would work too. It could even change the global view on screen at the same time.

Of course people may have altered their own personal global views but you get the idea I’m sure.

Would it speed up the switch by having everything in in one control map xml then offsetting the grid, rather than switching to a brand new config?

thanks for answering all my questions.