SEQ 1.4-1.5

[gospodindilly-ops]

Felucca 1.5 — amazing update! Thank you!

First of all, thank you so much for your hard work! It’s really exciting to watch Felucca become more polished and refined with every update. I really appreciate the direction the project is taking.

I did run into one workflow issue with the sequencer, though.

I like the idea of reducing the number of screens, and I can see how the new approach is intended to make things faster. However, editing step parameters such as Chance and Ratchet through the Automation screen feels quite cumbersome to me.

The main problem is that I can’t simply select a step directly in the step sequencer and edit its parameters right there. Instead, I have to remember which step I want to change, switch to Automation, find or add the corresponding entry, select the step number, choose the parameter, and then adjust its value.

For example, if I want to add Ratchet to a few steps in an existing pattern, I first have to go back to the step sequencer to check which steps contain the notes I want to edit. Then I have to return to Automation and go through several more actions for each change. It’s easy to lose track of what I’m editing, especially when working with a longer pattern.

Would it be possible to edit step-specific parameters directly from the Step Sequencer screen? Ideally, I could select a step and immediately adjust its Chance, Ratchet, and other step-level properties.

The Automation screen could then focus on displaying and managing the list of parameter changes, including the ability to remove individual entries.

I think this would make the workflow much more intuitive and faster, while keeping the streamlined interface you’ve been working toward.

Thanks again for the fantastic work on Felucca! I’m really enjoying seeing it evolve, and I hope this feedback is helpful.

[oMauNaProducer]

I ran into the same difficulty. Being able to change basically every parameter is amazing, but how to set them up is quite confusing. My suggestion for any automation, PAN for example: SEQ > AUTOMATION > PARAM (PAN) > ADD > EDIT PARAM, and then a page similar to EDIT > OP ENV 4/8 on the FM6 engine, where you could see the whole automation and add a keyframe on each STEP with the desired parameter value. Setting STEP 1 = -100 PAN and STEP 16 = +100 PAN would give us a complete side-to-side PAN automation without having to change each step manually or record it in real time with REC.

While I’m at it, I found 2 bugs:

PAN only goes up to +98, not +100.
On the AUTOMATION page, with certain parameters, K3 jumps to the ROW below when turning forward, and goes up a row when turning back. If I force it by always going back to the desired ROW with PRESET and changing it with K3 all the way from the start, it behaves normally from beginning to end, but as soon as I add a new parameter, the error happens again.

Thank you as always for your patience and dedication, Leo ♥

[gospodindilly-ops]

Another idea regarding the SELECT control: on the modulation page, could SELECT be used to navigate between modulation slots instead of K1?

The modulation matrix currently follows the Source → Destination → Amount structure. Moving slot selection to SELECT could free up K1 for an additional parameter or a new modulation feature.

For example, it would be interesting to have an optional modulation curve / quantization stage between Source and Destination:

Source → Curve / Steps → Destination → Amount

This could reshape an existing LFO or other modulation source, from smooth exponential curves to stepped, rhythmic modulation. It could create more complex timbral movement and interesting harmonic changes without requiring another LFO or oscillator.

Other lightweight options could include polarity inversion or a simple curve selector. These should be relatively inexpensive to implement if they reuse the existing modulation system and run at the control rate.

This way, bringing back SELECT navigation could do more than improve page navigation — it could also make the modulation matrix more flexible without adding much CPU overhead.

[gospodindilly-ops]

One more thought: in SAVE → PROJECT, there doesn’t seem to be an option to delete a project.

If SELECT could be used for navigation or project selection instead, it might free up a control or UI slot for a Delete Project option.

This would make project management more convenient, especially when the project list gets crowded. Of course, deletion should include a confirmation step to prevent accidental data loss.

[kurogedelic]

1.5.1 is out: https://github.com/hugelton/Felucca/releases/tag/v1.5.1

Thanks for spelling this out so clearly, @gospodindilly-ops, you were right that going through AUTOMATION for every ratchet was too many steps. SEQ now goes STEP, DETAIL, AUTOMATION. DETAIL is the step page, with the same cursor and the same piano roll (or drum grid) underneath, and the four knobs are the cursor step's own values: KNOB 1 CHANCE, KNOB 2 RATCH, KNOB 3 NUDGE, KNOB 4 VEL. PRESETS walks the steps, and on a drum track a white key picks the step. So adding ratchets to a few notes is: tap SEQ twice, turn PRESETS to the step, turn KNOB 2, move on to the next one. The four are drawn as small lanes over the steps, so you can see where the ratchets and chances are at a glance, and on STEP and the drum grid a step with a CHANCE, RATCH or NUDGE gets a small mark. EDIT on DETAIL puts the step's four back to their defaults.

AUTOMATION is still the list of everything, as you suggested, and you can already remove single entries there: select the row and press EDIT, one row at a time. It's the same data, so a value set on DETAIL shows up as its row on AUTOMATION and the other way round.

@oMauNaProducer thanks too. A keyframe view for automation (set PAN at step 1 and step 16 and let it sweep) isn't in this one, but I like the idea and have noted it. I've also noted the two things you found, PAN stopping at +98 and KNOB 3 jumping rows on AUTOMATION, to look at separately.