Shading empty patterns

[jlamores]

This is a great feature I have seen in another trackers. So maybe it could be added for the Nerdseq.

It's simply shaded patterns as darker colors when no notes are present in the pattern. It helps a lot visually to understand the song structure.

[mgd]

When you use such patterns deliberately to e.g. bridge gaps between islands then you could as well colour them yourself.

[jlamores]

When you use such patterns deliberately to e.g. bridge gaps between islands then you could as well colour them yourself.

Yes. The option to colour patterns is great!

I thought this automatic shading of empty patterns could be also a great adittion for the UI.

[mgd]

That got me thinking. I'm not sure I would want such an automatism. Any newly created pattern would be shaded initially.

However we have "Mute Track" and that shades/greys the track. Why not add a "Mute Sequencer Screen Position" (track being X and row being Y) function?
That would also remove the need to deliberately create empty patterns.

And while I'm at it:
"Mute Pattern" may or may not come handy.
Not sure it is really useful but I could as well imagine to mute/unmute sequencer screen positions, patterns and tracks via FX (SPFX). Together with PRF1/2/3/4 this could be fun

Sorry for hijacking your Feature Request,
Michael

[Karlo]

That got me thinking. I'm not sure I would want such an automatism. Any newly created pattern would be shaded initially.

However we have "Mute Track" and that shades/greys the track. Why not add a "Mute Sequencer Screen Position" (track being X and row being Y) function?
That would also remove the need to deliberately create empty patterns.

And while I'm at it:
"Mute Pattern" may or may not come handy.
Not sure it is really useful but I could as well imagine to mute/unmute sequencer screen positions, patterns and tracks via FX (SPFX). Together with PRF1/2/3/4 this could be fun

Sorry for hijacking your Feature Request,
Michael

This s a great idea! Having a mute command from another pattern like STSP only "mute or unmute" would allow patterns to "stop playing" (theoretically they are still playing, just not sending data) So then if you have patterns using SPFX Random Jump, they can "stop playing" when muted, versus waiting for them to cross the last step to actually stop... which could be while if they're is a few SPFX random jump commands.

...Or if you want to mute mod or FX for a few rows of a pattern. Maybe? 

I could see how mutes could get complicated quick, but that seems to be the strength of NerdSEQ, complicated quick. 

It's fun to think about.