search

brummer10 / Fluida.lv2

Fluidsynth as LV2 plugin
GNU General Public License v2.0
34 stars 4 forks source link

[Feature Request] Adding a separate patch window that can stay open #40

Closed audio2000 closed 1 day ago

audio2000 commented 1 week ago

Unfortunately my "Using Fluida as an instrument" post did not seem to fly, so I will go to my second use.

In Fluida there is a "Channel Matrix" which opens up as a separate window. If you keep that window open and you open or drag & drop soundfonts into the GUI, this "Channel Matrix" updates the channel drop downs based on the patches offered by that new soundfont.

Would it be considered to offer a very similar window to what is mentioned above, but have it be a "Bank/Patch" window? It would function in the same way where this window can stay open and also would update the list based on if different soundfonts are added while this window is still open during that file opening. Would be activated in GUI with an icon that toggles show/hide window exactly how the Channel Matrix button functions.

If interested in this idea, here are some more properties for this window. -Could have a filter field at top or bottom (See #38 for ideas regarding this) -Window could be resized -Window size and placement saves/remembers (if possible) -Patches could appear in a "List View" or "Details View" like file managers offer with columns: patch # / name can be clicked on to change sort. Or if not, maybe can use "Compact View" instead where if the windows width is increased then shows two or more columns of the list continuing to the next column. -Hotkeys Allow Home / End / PageUp / PageDown / ArrowUp / ArrowDown to all be able to navigate through the list. Would be a highlight cursor selecting files like a file manager does. -The cursor highlight would either automatically load this patch into Fluida.

Because soundfonts can contain so many patches inside of them, this just allows user to be able to see more of what they contain. Gives a visual because many times you open a soundfont and have no clue if it contains 1 patch or hundreds. This also allows you to be able to go through patches more efficiently because you can be testing them with a MIDI keyboard as you move the cursor through the patch list.

Anyways I do not think this is going to probably be considered either but just feel that this could be helpful if anyone is interested. There are really no programs/plugins in Linux that allow for testing out soundfonts in this way.

Thank you to anyone who reads this.

brummer10 commented 1 week ago

It's just that I'm running out of time. I've currently no time left by my day job.

audio2000 commented 6 days ago

I understand. I was just mentioning/making feature requests because you said you were open to them. Obviously you do not have to do any of them, but on occassion I might still mention some things here and there if that is okay with you? Maybe other contributors may be interested in adde them in the future. Thank you for responding.