On Thu, Oct 17, 2019 at 3:20 PM Urs Liska <li...@openlilylib.org> wrote:

> 17. Oktober 2019 22:19, "Saul Tobin" <saul.james.to...@gmail.com> schrieb:
>
> > The biggest killer-feature for me would be the ability to playback
> multiple midi files
> > simultaneously in sync (to work around the 16 track limitation).
>
> Sounds cool, but that's obviously not on the table. I think this is the
> domain of DAWs.
>

Totally understand it's not on the table or what you're working on. I don't
agree it's the domain of DAWs, however. I'm not talking about high quality
tweakable MIDI sequencing. Literally just a quick and dirty preview, like
starting multiple instances of pmidi at the same time.

>
> >
> > Audio format-wise, I think mp3 is fine. I doubt anyone particularly
> cares about lossless quality
> > for their general midi soundfont playback.
>
> Fair point. But two comments:
> - To get mp3 the MIDI is first converted to a lossless format anyway.
> - I think many people who want audio files want them to *share* them,
> either on some sort of sharing platform or to hand them over to some
> partner for whatever purpose. And for that there may be specific
> requirements.
>
> But your comment reinforces my gut-feeling that the proper approach is not
> to provide too many formats but rather a nice, well-defined selection.
>
> Urs
>
> >
> > On Thu, Oct 17, 2019, 10:34 AM Guy Stalnaker <jimmyg...@gmail.com>
> wrote:
> >
> >> Urs,
> >>
> >> I'm thinking you mean here "Frescobaldi on Linux" right (since you also
> >> say fluidsynth)? I use Frescobaldi primarily on Windows. And though one
> >> can use Cygwin, etc. to install an app like timidity, Frescobaldi does
> >> not "see" it. But I can, and to, have lame installed because I can use
> >> VirtualMidiSyth to manually convert midi to mp3.
> >>
> >> Just putting this out there so you know.
> >>
> >> Regards!
> >>
> >> On 10/17/2019 9:19 AM, Urs Liska wrote:
> >>> Hi all,
> >>>
> >>> I've just started looking into how Frescobaldi provides support for
> >>> "exporting" scores to audio.
> >>>
> >>> Until now this was hardcoded to use TiMidity (and had to be activated
> as
> >>> "experimental feature").
> >>>
> >>> I have so far created functionality that
> >>>
> >>> * checks whether timidity, fluidsynth and lame are available
> >>> * populates the filter of the file dialog with all registered file
> >>> formats for the available converters (=> if (and only if) Lame is
> >>> installed the .mp3 filter will be added). You can see a screenshot
> >>> at
> >>>
> https://github.com/frescobaldi/frescobaldi/pull/1205#issuecomment-543155209
> >>>
> >>> After clicking the Save button there will be a configuration dialog
> like
> >>> we already have for the file *import* functionality. Depending on the
> >>> chosen converter/exporter tool it will be possible to configure
> selected
> >>> settings like for example audio quality, alternative soundfont (in
> >>> fluidsynth), effects.
> >>>
> >>> However, since that's not my area of expertise I'd like to ask for
> >>> suggestions (possibly with the corresponding command line invocations)
> about
> >>>
> >>> * which audio formats Frescobaldi should support (I don't think it's
> >>> good to clutter the interface with stuff that noone needs)
> >>> * which options we should make configurable for the three converter
> tools
> >>> * if there are other converters we should consider supporting
> >>>
> >>> Best
> >>> Urs
> >>>
> >>>
> >>> _______________________________________________
> >>> lilypond-user mailing list
> >>> lilypond-user@gnu.org
> >>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> >>>
> >>
> >> --
> >> “Happiness is the meaning and the purpose of life, the whole aim and end
> >> of human existence.”
> >> ― Aristotle
> >>
> >> _______________________________________________
> >> lilypond-user mailing list
> >> lilypond-user@gnu.org
> >> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to