Slight rework of FP Grids

[ArthurGibert]

Fix timing and phase issue

[rjsmith]

HI @ArthurGibert I am struggling to understand what this code does, and why it is necessary.

When I now call generator.reset(), then query the generator.getSteps(), it is already set to 2 ...?
This means that code that should be triggered at the start of a pattern sequence after a reset is never executed, like this https://github.com/ATOVproject/faderpunk/pull/467/changes#diff-0a1fb26733375c0300e1f03e83ace8d18a39cbde92ddb571fa966037075aa848R404.

[rjsmith]

Hi @ArthurGibert I've experimented with this variation instead , I find it really useful to quickly be able to land on 1/16th notes visually

                            if matches!(div, 2 | 4 | 8 | 16) {
                                leds.set(3, Led::Bottom, Color::Orange, Brightness::Mid);
                            } else if div == 6 {
                                // Highlight 1/16th note default
                                leds.set(3, Led::Bottom, Color::Yellow, Brightness::High);
                            } else {
                                leds.set(3, Led::Bottom, Color::Blue, Brightness::Mid);
                            }

[rjsmith]

Perhaps a simpler alternative for FP-Grids is just to run it on a fixed clock division per output mode:

• div = 6 for Euclidean (16 steps in one bar)
• div = 3 for Drum Mode (32 steps in one bar)
• div = 6, 4 depending on the number of steps per bar in the DnB pattern

This merging solution is going to mask the original underlying drum patterns I think.