This is a place to put ideas. The ideas don't have to be fully thought-out at this stage. These ideas can be discarded if they don't turn out helpful.
Add ability to custom split layers to different regions of the keyboard
Options per-layer to map the instrument to a particular keyboard range so different hands can play different instruments
Pie menu
Could pie menus be useful on Floe's GUI instead of linear menus? The precision radial is an interesting idea too.
- setting parameters to default values
- picking instruments by tag
- randomly loading instruments
New minor additions
- Attack for the LFO
- Phase option for LFO
- Bypass button for effects - distinct from on/off
- Clear-all button for effects
- Tempo sync phaser frequency
- Add a sample-end parameter
- Add an alternative monophonic option that doesn't re-trigger the note if there is one playing
- Add the option to change the curves of Attack, Decay and Release
- Add a check for updates button
Add support for other audio file types
We already support FLAC and WAV. Could Wavpack be added too? What about lossy formats: MP3, OGG?
GUI ideas
- Add icons for filter types instead of just text
- Add ability to drag menus like a slider
- Add sustain pedal (CC64) rocker to represent it's current state
Presets for effects rack and layers
Add the ability to save and load presets for the entire effects rack and the entire set of layers. This would allow mixing and matching different sets of sound-generators (the layers) with sound-shapers (the effects rack)
Algorithmic legato simulation
Could we take inspiration from FrozenPlain's Arctic Strings Kontakt instrument and algorithmically simulate legato? Legato time effected by play rate and things, and a slider for portamento time - maybe even velocity controlled too
Undo & Redo
- Undo/redo for randomly selecting presets/instruments
- Undo/redo for parameters
- Support clap's undo extension
Detect type of sound for better tagging
Can we analyse the audio files to determine their character: pluck, sustain, bright, dark, etc. And use this information alongside the manually added tags of an instrument.
Add the ability to parse SFZ/SoundFont/Decent Sampler files as well as our Lua format
Alternatively, could the solution for converting existing library be an external tool like this? https://github.com/git-moss/ConvertWithMoss
Modulation system
Replace our simplistic LFOs with a full modulation system
MIDI workflow enhancements
We currently have 'MIDI learn' but it's not very fleshed out. Could we have an interface for viewing all MIDI mappings and switch between/save profiles.
Macro knobs
A set of knobs that can be assigned to any parameter. Would allow for preset designers to bring to the forefront the key parameters of a sound. Would also be convenient for mapping to MIDI CCs. Could part of this also include XY pads, or a controller like the joystick on a Yamaha TG-33? How does Arturia Pigments use macros.
Arpeggiator
Ability to sequence repeats and patterns. What features does Soundpaint's arpeggiator have?
Screenshot generation util
It would be great to be able to script the taking of screenshots so that we can more easily keep product images up-to-date as Floe develops. Perhaps the standalone program could receive CLI arguments to load particular presets and open particular pages on the GUI and then export it as a PNG. This could then be scripted using bash
Add benchmarking system
- Add a CLI interface for running benchmarks of Floe's audio processing
- Use hyprefine and Bencher to continuously benchmark
Support QOI image format
Likely faster decoding than PNG which would be useful for backgrounds/icons. https://github.com/phoboslab/qoi/tree/master
CI report improvements
With the ntfy notifications, it would be good to get a list of failed checks rather than just overall success or failure.
Should all of our CI just save results to json (upload-artifact) and then the final Github Actions workflow job collates all these json files (download-artifact) and uses jq to present the information however we like?
Additionally:
A dev dashboard like TigerBeetle does would be useful for Floe.
https://tigerbeetle.github.io/tigerbeetle/
Currently seeing the results of various checks and tests isn't great on the Actions tag of Github. Additionally, it would be good to graph things like benchmarks, executable size, lines of code, etc.
We could follow Tigerbeetle's template where the data is pushed to a separate github repo and then to github pages.
This is a place to put ideas. The ideas don't have to be fully thought-out at this stage. These ideas can be discarded if they don't turn out helpful.
Add ability to custom split layers to different regions of the keyboard
Options per-layer to map the instrument to a particular keyboard range so different hands can play different instruments
Pie menu
Could pie menus be useful on Floe's GUI instead of linear menus? The precision radial is an interesting idea too.
New minor additions
Add support for other audio file types
We already support FLAC and WAV. Could Wavpack be added too? What about lossy formats: MP3, OGG?
GUI ideas
Presets for effects rack and layers
Add the ability to save and load presets for the entire effects rack and the entire set of layers. This would allow mixing and matching different sets of sound-generators (the layers) with sound-shapers (the effects rack)
Algorithmic legato simulation
Could we take inspiration from FrozenPlain's Arctic Strings Kontakt instrument and algorithmically simulate legato? Legato time effected by play rate and things, and a slider for portamento time - maybe even velocity controlled too
Undo & Redo
Detect type of sound for better tagging
Can we analyse the audio files to determine their character: pluck, sustain, bright, dark, etc. And use this information alongside the manually added tags of an instrument.
Add the ability to parse SFZ/SoundFont/Decent Sampler files as well as our Lua format
Alternatively, could the solution for converting existing library be an external tool like this? https://github.com/git-moss/ConvertWithMoss
Modulation system
Replace our simplistic LFOs with a full modulation system
MIDI workflow enhancements
We currently have 'MIDI learn' but it's not very fleshed out. Could we have an interface for viewing all MIDI mappings and switch between/save profiles.
Macro knobs
A set of knobs that can be assigned to any parameter. Would allow for preset designers to bring to the forefront the key parameters of a sound. Would also be convenient for mapping to MIDI CCs. Could part of this also include XY pads, or a controller like the joystick on a Yamaha TG-33? How does Arturia Pigments use macros.
Arpeggiator
Ability to sequence repeats and patterns. What features does Soundpaint's arpeggiator have?
Screenshot generation util
It would be great to be able to script the taking of screenshots so that we can more easily keep product images up-to-date as Floe develops. Perhaps the standalone program could receive CLI arguments to load particular presets and open particular pages on the GUI and then export it as a PNG. This could then be scripted using bash
Add benchmarking system
Support QOI image format
Likely faster decoding than PNG which would be useful for backgrounds/icons. https://github.com/phoboslab/qoi/tree/master
CI report improvements
With the ntfy notifications, it would be good to get a list of failed checks rather than just overall success or failure.
Should all of our CI just save results to json (upload-artifact) and then the final Github Actions workflow job collates all these json files (download-artifact) and uses jq to present the information however we like?
Additionally:
A dev dashboard like TigerBeetle does would be useful for Floe.
https://tigerbeetle.github.io/tigerbeetle/
Currently seeing the results of various checks and tests isn't great on the Actions tag of Github. Additionally, it would be good to graph things like benchmarks, executable size, lines of code, etc.
We could follow Tigerbeetle's template where the data is pushed to a separate github repo and then to github pages.