[haiku-bugs] Re: [Haiku] #9920: BSynth upgrade
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Wed, 24 Sep 2014 07:45:33 -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 bonefish):
Replying to [comment:38 Pete]:
> But the way I read it, this is not what's being suggested. The link
being set is just a standard name in the same /boot/system/data/synth
directory to point to the ''one'' soundfont in that directory. There is
essentially no point in having more than one font there, because that's
just the ultimate default. I see the only use for that directory is as a
fallback if no user selection has been made. There might eventually be a
choice of packaged system soundfonts from the repository, but the user
would just replace the one with another, and the link would get replaced,
too.
I was under the impression that there are (or can be) applications that
work with multiple sound fonts or there's at least a use case that a user
may switch between multiple installed sound fonts on a somewhat regular
basis. If that is not the case and having only a single sound font
installed is the only thing that makes sense, I would already declare that
as conflicts at the package level, so that installing a sound fount would
automatically uninstall the previous one. In that case a symlink with a
well-known name in data/synth is an option. Or the sound font file could
simply be named like this in the first place.
Replying to [comment:40 jackburton]:
> IMHO an "Import SoundFont" Button which creates a link would create some
really bad user experience.
[...]
> At that point, I'd avoid putting the "Import Soundfont" button and leave
the user on his own, if it could create these kinds of issues.
Agreed, creating a symlink as the import action isn't a good solution. The
file should simply be moved, if an import action was implemented at all.
There was a recent discussion about how to deal with importing fonts. I
don't recall the outcome, but I think we should handle both similarly.
--
Ticket URL: <https://dev.haiku-os.org/ticket/9920#comment:41>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
