[haiku-bugs] Re: [Haiku] #9920: BSynth upgrade
- From: "Pete" <trac@xxxxxxxxxxxx>
- Date: Tue, 23 Sep 2014 06:02:34 -0000
#9920: BSynth upgrade
-----------------------------+-------------------------
Reporter: Pete | Owner: korli
Type: enhancement | Status: new
Priority: normal | Milestone: R1
Component: Kits/Midi Kit | Version: R1/alpha4.1
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 1 | Platform: All
-----------------------------+-------------------------
Comment (by Pete):
Replying to [comment:31 jackburton]:
> Replying to [comment:29 Pete]:
> Doesn't look like a so useful function then :-)
> Seriously... the only use we have for it in the tree (for now) is the
MIDI Player scope ?
Pretty much... (:-/) I can't prove it, but I think it works pretty much
like the BeOS version did. The BeBook says: "This function is designed to
feed waveform displays (and the like); it isn't intended to be used as a
"sound spigot" that you can pipe to a file (for example)." I gather the
idea was just to give some indication of the data flowing through. That's
why I don't want it to be more processing-intensive than necessary.
>
> > BTW, could you [just for me...(:-)] add a B_SYSTEM_SETTINGS_DIRECTORY
check after the B_USER_SETTINGS_DIRECTORY one, and also check for
synth.sf2 in B_SYNTH_DIRECTORY just before finally devolving to
big_synth.sy.
>
> Done in hrev47897
Many thanks.
>
> Ok. I have another question. Let's say we drop big_synth.sy, and prepare
a set of packages containing different soundfonts, and the user picks and
installs one of them, or more than one. How would you select the "default"
soundfont in that case ? Meaning before the user has configured its
preferred soundfont via symlink or via the not-yet-done midi preflet ?
Should we just pick a random one ?
Good question... I don't think anybody has thought about this very hard!
Actually I've never been particularly keen on the idea of a "system" synth
directory. Seems to me its only use is if you have a ''single'' system
soundfont. If you want to give the user a choice, there is very little
point to it at all; if you provide a way of letting the synth know where
it is (via a link in /boot/system/settings/synth) or whatever) the font
can be anywhere.
If you are going to have a system directory with several fonts in it, I
would assume the last font loaded would change the synth.sf2 link (in that
folder) to point to it. If the user wants another, they would change the
link in /boot/system/settings/synth. (If you look at the hpkg I made, it
sets the boot/system/settings/synth, but with the keep-old flag, so that
it doesn't mess with user preference.)
As I mentioned previously. probably the only current app that might make
use of it is MidiSynth, which builds a menu from everything in
B_SYNTH_DIRECTORY/synth, so you can pick. OTOH if your font ''is''
anywhere else, it can't get to it. In my MusicWeaver Synth module I just
let the user drag whatever font he wants into the control panel (or find
it via FIlePanel).
--
Ticket URL: <https://dev.haiku-os.org/ticket/9920#comment:32>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
