Re: Frescobaldi, improve support for audio export
Am 21. Oktober 2019 18:52:29 MESZ schrieb Saul Tobin : >Would the bundled VLC be redundant to an existing system install of >VLC? >Would it be usable instead of a system install? Would the bundled VLC >get >updates? As I've said several times in this thread *bundling* anything with Frescobaldi is not what we are talking about here. Urs > >I normally have VLC installed anyway, but I'd rather not have to keep a >separate copy on disk just for Frescobaldi. > > >On Sun, Oct 20, 2019, 10:33 PM Federico Bruni >wrote: > >> Il giorno ven 18 ott 2019 alle 23:14, J Martin Rushton via >> lilypond-user ha scritto: >> > There is a VLC available through flatpack, but I've not used it (so >> > therefore cannot comment), but have seen warnings that it will pull >in >> > up to 1.2 GiB of other packages including the complete KDE >> > implementation. >> >> $ flatpak info org.videolan.VLC | grep 'Installed' >>Installed: 77,7 MB >> >> $ flatpak info org.kde.Platform//5.13 | grep Installed >>Installed: 910,3 MB >> >> The KDE runtime may be used by other Qt applications installed in >your >> system. >> >> You may want to read this post by the author of Flatpak: >> >> >https://blogs.gnome.org/alexl/2017/10/02/on-application-sizes-and-bloat-in-flatpak/ >> >> In a nutshell: Flatpak is a bundling system and as such it requires >> more disk space, but the benefits (of shipping a self-contained and >> independent application) may offset the cost for some people, >> especially today (as large disks are smaller and cheaper). The >article >> explains how ostree helps in reducing the duplication between similar >> runtimes. >> >> >> >> ___ >> lilypond-user mailing list >> lilypond-user@gnu.org >> https://lists.gnu.org/mailman/listinfo/lilypond-user >> -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
Would the bundled VLC be redundant to an existing system install of VLC? Would it be usable instead of a system install? Would the bundled VLC get updates? I normally have VLC installed anyway, but I'd rather not have to keep a separate copy on disk just for Frescobaldi. On Sun, Oct 20, 2019, 10:33 PM Federico Bruni wrote: > Il giorno ven 18 ott 2019 alle 23:14, J Martin Rushton via > lilypond-user ha scritto: > > There is a VLC available through flatpack, but I've not used it (so > > therefore cannot comment), but have seen warnings that it will pull in > > up to 1.2 GiB of other packages including the complete KDE > > implementation. > > $ flatpak info org.videolan.VLC | grep 'Installed' >Installed: 77,7 MB > > $ flatpak info org.kde.Platform//5.13 | grep Installed >Installed: 910,3 MB > > The KDE runtime may be used by other Qt applications installed in your > system. > > You may want to read this post by the author of Flatpak: > > https://blogs.gnome.org/alexl/2017/10/02/on-application-sizes-and-bloat-in-flatpak/ > > In a nutshell: Flatpak is a bundling system and as such it requires > more disk space, but the benefits (of shipping a self-contained and > independent application) may offset the cost for some people, > especially today (as large disks are smaller and cheaper). The article > explains how ostree helps in reducing the duplication between similar > runtimes. > > > > ___ > 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
Re: Frescobaldi, improve support for audio export
Il giorno ven 18 ott 2019 alle 23:14, J Martin Rushton via lilypond-user ha scritto: There is a VLC available through flatpack, but I've not used it (so therefore cannot comment), but have seen warnings that it will pull in up to 1.2 GiB of other packages including the complete KDE implementation. $ flatpak info org.videolan.VLC | grep 'Installed' Installed: 77,7 MB $ flatpak info org.kde.Platform//5.13 | grep Installed Installed: 910,3 MB The KDE runtime may be used by other Qt applications installed in your system. You may want to read this post by the author of Flatpak: https://blogs.gnome.org/alexl/2017/10/02/on-application-sizes-and-bloat-in-flatpak/ In a nutshell: Flatpak is a bundling system and as such it requires more disk space, but the benefits (of shipping a self-contained and independent application) may offset the cost for some people, especially today (as large disks are smaller and cheaper). The article explains how ostree helps in reducing the duplication between similar runtimes. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
Am 19.10.19 um 18:08 schrieb David Wright: On Fri 18 Oct 2019 at 23:14:30 (+0100), Lilypond-User wrote: On 18/10/2019 22:06, Urs Liska wrote: Am 18. Oktober 2019 22:45:28 MESZ schrieb Karlin High : On 10/18/2019 3:17 PM, Guy Stalnaker wrote: So, it looks like VLC with the right syntax may be able to use FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or other codecs - or - output WAV file as input to lame It's a complicated commandline but I've seen (and created) worse LOL Complicated is not an issue - that's what Frescobaldi can manage. It has to be reliable and ideally cross-platform Anyone planning on using VLC on Fedora, RHEL or CentOS needs to check out the current situation. For RHEL/CentOS AIUI: 7.7 VLC from the usual sources does not work (in fact crashes some updates). 8.0 VLC is not available. There is a VLC available through flatpack, but I've not used it (so therefore cannot comment), but have seen warnings that it will pull in up to 1.2 GiB of other packages including the complete KDE implementation. Perhaps much of this is because VL stands for Video-LAN, neither of which has much to do with MIDI→MP3. Quite honestly, I'm not sure I see the wisdom of bundling in any or all of VLC into Frescobaldi. The hiatus in support of MIDI by Windows versions 2.1.0 up gives an example of the kind of problems that can ensue. Nobody whats to *bundle* any tools with Frescobaldi ... I would have thought that people who convert their MIDI files would (a) have access to platform-appropriate tools already, (b) perhaps want to use different soundfonts from those supplied, and (c) want to use such tools on MIDI files that don't originate from F~ and LP. ... the idea is to provide a direct way to trigger the toolchain from Frescobaldi. For example we have an "Import MusicXML" command although everyone who wants to do it already has musicxml2ly installed as part of LilyPond. Or, to make the point even clearer: we also "bundle" LilyPond with Frescobaldi although people could use the command line for compiling their scores. Currently this function uses a hard-coded "timidity" invocation, and my plan is to support a selection of external tools and a selection of target audio formats to choose from - when the external tool is available on the system. Urs Cheers, David. ___ 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
Re: Frescobaldi, improve support for audio export
On Fri 18 Oct 2019 at 23:14:30 (+0100), Lilypond-User wrote: > On 18/10/2019 22:06, Urs Liska wrote: > > Am 18. Oktober 2019 22:45:28 MESZ schrieb Karlin High > > : > >> On 10/18/2019 3:17 PM, Guy Stalnaker wrote: > >>> So, it looks like VLC with the right syntax may be able to use > >>> FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or other > >>> codecs - or - output WAV file as input to lame > >>> > >>> It's a complicated commandline but I've seen (and created) worse LOL > > > > Complicated is not an issue - that's what Frescobaldi can manage. It has to > > be reliable and ideally cross-platform > > > Anyone planning on using VLC on Fedora, RHEL or CentOS needs to check > out the current situation. For RHEL/CentOS AIUI: > > 7.7 VLC from the usual sources does not work (in fact crashes some updates). > 8.0 VLC is not available. > > There is a VLC available through flatpack, but I've not used it (so > therefore cannot comment), but have seen warnings that it will pull in > up to 1.2 GiB of other packages including the complete KDE implementation. Perhaps much of this is because VL stands for Video-LAN, neither of which has much to do with MIDI→MP3. Quite honestly, I'm not sure I see the wisdom of bundling in any or all of VLC into Frescobaldi. The hiatus in support of MIDI by Windows versions 2.1.0 up gives an example of the kind of problems that can ensue. I would have thought that people who convert their MIDI files would (a) have access to platform-appropriate tools already, (b) perhaps want to use different soundfonts from those supplied, and (c) want to use such tools on MIDI files that don't originate from F~ and LP. Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
On 18/10/2019 22:06, Urs Liska wrote: > > > Am 18. Oktober 2019 22:45:28 MESZ schrieb Karlin High : >> On 10/18/2019 3:17 PM, Guy Stalnaker wrote: >>> So, it looks like VLC with the right syntax may be able to use >>> FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or >> other >>> codecs - or - output WAV file as input to lame >>> >>> It's a complicated commandline but I've seen (and created) worse LOL >> > > Complicated is not an issue - that's what Frescobaldi can manage. It has to > be reliable and ideally cross-platform > >> Actually, VLC on Windows can encode MIDI to MP3 without using the >> command line at all. That's what I use. > > The point *is* to have a command line to be able to use it from Frescobaldi. > > Urs > > Anyone planning on using VLC on Fedora, RHEL or CentOS needs to check out the current situation. For RHEL/CentOS AIUI: 7.7 VLC from the usual sources does not work (in fact crashes some updates). 8.0 VLC is not available. There is a VLC available through flatpack, but I've not used it (so therefore cannot comment), but have seen warnings that it will pull in up to 1.2 GiB of other packages including the complete KDE implementation. -- J Martin Rushton MBCS signature.asc Description: OpenPGP digital signature ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
Am 18. Oktober 2019 22:45:28 MESZ schrieb Karlin High : >On 10/18/2019 3:17 PM, Guy Stalnaker wrote: >> So, it looks like VLC with the right syntax may be able to use >> FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or >other >> codecs - or - output WAV file as input to lame >> >> It's a complicated commandline but I've seen (and created) worse LOL > Complicated is not an issue - that's what Frescobaldi can manage. It has to be reliable and ideally cross-platform >Actually, VLC on Windows can encode MIDI to MP3 without using the >command line at all. That's what I use. The point *is* to have a command line to be able to use it from Frescobaldi. Urs -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
Karlin, Yes it can. I use VLC all the time to play midi files on the Choral Public Domain Library :-) But Urs was asking for a commandline tool he can wrap in a Frescobaldi function with possible syntax options. Thus my email with VLC commandline options. On 10/18/2019 3:45 PM, Karlin High wrote: On 10/18/2019 3:17 PM, Guy Stalnaker wrote: So, it looks like VLC with the right syntax may be able to use FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or other codecs - or - output WAV file as input to lame It's a complicated commandline but I've seen (and created) worse LOL Actually, VLC on Windows can encode MIDI to MP3 without using the command line at all. That's what I use. -- “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
Re: Frescobaldi, improve support for audio export
On 10/18/2019 3:17 PM, Guy Stalnaker wrote: So, it looks like VLC with the right syntax may be able to use FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or other codecs - or - output WAV file as input to lame It's a complicated commandline but I've seen (and created) worse LOL Actually, VLC on Windows can encode MIDI to MP3 without using the command line at all. That's what I use. -- Karlin High Missouri, USA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
Urs, On 10/17/2019 5:17 PM, Urs Liska wrote: 17. Oktober 2019 18:59, "Guy Stalnaker" schrieb: Urs, I'm thinking you mean here "Frescobaldi on Linux" right (since you also say fluidsynth)? I don't "mean" that but it seems that's what I'm talking about. However, although I don't know much about these things resources like https://github.com/FluidSynth/fluidsynth/wiki/BuildingWithCMake seem to indicate that it *is* possible to have fluidsynth as a real Windows application. While "possible" it is not end-user friendly. Creating the compile environments (four possibilities!) will inhibit most users who are unfamiliar with such things. Even though I am familiar with such things, I'd opt, as I actually did, and pay for a very usable product like VirtualMidiSynth which includes midi-2-mp3/wav capability. I use Frescobaldi primarily on Windows. And though one can use Cygwin, etc. to install an app like timidity, Frescobaldi does not "see" it. OK, then the general question seems to be: are there command line tools that can be used to convert MIDI to audio on Windows in a way that Frescobaldi can use? Now that is a different question. I think the best option is VLC (if only because it's under current development and thus is not moribund as so much open source software is. https://wiki.videolan.org/VLC_command-line_help "FluidSynth MIDI synthesizer (fluidsynth)" VLC will play midi files. FFmpeg audio/video decoder (avcodec) Various audio and video decoders/encoders delivered by the FFmpeg library. This includes (MS)MPEG4, DivX, SV1,H261, H263, H264, WMV, WMA, AAC, AMR, DV, MJPEG and other codecs File audio output (afile) --audiofile-wav, --no-audiofile-wav Add WAVE header (default enabled) Instead of writing a raw file, you can add a WAV header to the file. So, it looks like VLC with the right syntax may be able to use FluidSynth/soundfont to "play" midi and FFMpeg to encode to AAC or other codecs - or - output WAV file as input to lame It's a complicated commandline but I've seen (and created) worse LOL Guy -- “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
Re: Frescobaldi, improve support for audio export
> Am 2019-10-18 um 00:20 schrieb Urs Liska : > > 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. Hi Urs, I agree that probably only a neglectable minority would like to fiddle with a lot of audio options. For a GNU program, Ogg Vorbis makes sense. MP3 because everyone knows it. And a possibility to keep the WAV for further processing, e.g. in DAWs, with video or other encoders. (I use a simple shell script calling timidity and lame for MIDI -> WAV -> MP3.) Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm https://www.fiee.net ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Frescobaldi, improve support for audio export
On Thu, Oct 17, 2019 at 3:20 PM Urs Liska wrote: > 17. Oktober 2019 22:19, "Saul Tobin" 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 > 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
Re: Frescobaldi, improve support for audio export
17. Oktober 2019 22:19, "Saul Tobin" 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. > > 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 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
Re: Frescobaldi, improve support for audio export
17. Oktober 2019 18:59, "Guy Stalnaker" schrieb: > Urs, > > I'm thinking you mean here "Frescobaldi on Linux" right (since you also say > fluidsynth)? I don't "mean" that but it seems that's what I'm talking about. However, although I don't know much about these things resources like https://github.com/FluidSynth/fluidsynth/wiki/BuildingWithCMake seem to indicate that it *is* possible to have fluidsynth as a real Windows application. > I use > Frescobaldi primarily on Windows. And though one can use Cygwin, etc. to > install an app like > timidity, Frescobaldi does not "see" it. OK, then the general question seems to be: are there command line tools that can be used to convert MIDI to audio on Windows in a way that Frescobaldi can use? > But I can, and to, have lame installed because I can use > VirtualMidiSyth to manually convert midi to mp3. OK, a quick glance on the VirtualMidiSynth homepage made it clear that I won't be able to fully digest how things relate here. What would be your setup to "manually convert midi to mp3", is there a possibility to wrap that in a command line invocation? May lack of support for Windows-specific functionality is not ideological (well, mostly ;-) ), but I need specific input to try making it work. > > Just putting this out there so you know. > Thanks Urs > 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
Re: Frescobaldi, improve support for audio export
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). Audio format-wise, I think mp3 is fine. I doubt anyone particularly cares about lossless quality for their general midi soundfont playback. On Thu, Oct 17, 2019, 10:34 AM Guy Stalnaker 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
Re: Frescobaldi, improve support for audio export
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
