Zynseq - A native step sequencer

[jofemodo]

@riban

The velocity input level is displayed by a green bar in the bottom left corner of the grid. I wonder if this is sufficient and avoids clinical use of exact velocities . I am not sure where a 3 digit numeric value would best be displayed.

• The green bar sticked to keys is perfectly OK for me. It’s a little bit too small and green doesn’t contrast too much. I will test with other colors …
• Definitely, I would enable acceleration for velocity encoder.

@riban

It is a bit of a mix of menu entries. I have put them all there for now because I need a working interface to develop against but we can consider how to handle this better in the future. I wonder if menu dividers might be beneficial.

Yes. I understand all this. We will find a better way when things get more stable …

@riban

Maybe a BACK button could appear in the topbar when menu is showing. (I think I had that idea but then forgot to implement it.)

I’m OK with that, but ALL touch-specific widgets have to be “optional”. A “touch UI” flag should be added to config ASAP.

@riban

I could use the assert button to assert changes, avoiding grid redraws but there are some things where that reduces user experience, e.g. adjusting the zoom feels like it should do so live rather than after assert.

If it’s working fluid with touch interface, then it can work equally fluid with encoders.
I will take a look to the code …

@riban

I avoided “Launch Pad” due to its similarity with Novation’s product name. I don’t know if that is a registered trade mark.

IMHO, nobody has the right for kidnapping words. “Launch Pad” are a combination of 2 words and we can use it. Of course, if we try to register a product with this name, then Novation will come to open our asses … Anyway, and thinking about it, you are right and we could find a better combination of words … like “trigger grid” … or “Trigrid”

OK OK … i think we have to vote … so, please, tell your proposals and we will make a nice votation

Choosing a name for the ZynStep's "live pattern triggering" feature

Please, make your proposals and we will vote: TriGrid (from Trigger Grid), by Jofemodo Pad Zoo, by @mheidt HARAMSLDGI , as in Highly Advanced Rhythmic And Melodic Sequences Live Deployment Graphic Interface, by @lisacld ZynGrid, by @Jtunes Thanks!

@riban

The touch interface elements I have devised have been based on the principal of minimal use of screen real estate.

But encoder’s interface users don’t want to see these elements. I will add the “touch UI” config flag ASAP.

@riban

Have a think then confirm and I will so as you wish.

I already have thought quite a bit about this question, @riban.

Zynstep should be a MIDI-clock consumer, same that other sequencers already working in the system, or arpeggiators, or a synced delays. In fact, some of the current engines already include stepseqs or arpeggiators, like NoizeMaker, Triceratops or Helm. Also MOD-UI include some MIDI tools that can be synced with MIDI-clock.

Any of these “consumers” shouldn’t make a difference about the “clock source”. ZynMIDIRouter will take care of this, so everything can be synced together flawlessly.

Also, as everything have to work perfectly with an external MIDI-clock, this will be our main use-case. And the best way of avoiding problems with this is to completely erase this difference. I mean, from the application/module POV, there is no external/internal clock. Only one clock does exist. Without adjectives. Only ZynMIDIRouter will know about clock sources …

Thanks a lot!