Re: [fluid-dev] Parameter Parse questions

2022-05-21 Thread sqweek E.
> On 20 May 2022, at 03:03, 刘家桐 wrote: > > But when I used "fluidsynth -R1nivF/home/parallels/my_music.wav > /home/parallels/FluidR3_GM.sf2 /home/parallels/MIDI_sample.mid" (enable > Reverb module), The program just played the music through my computer's > speaker. > > Then I found that afte

Re: [fluid-dev] Sample Playback Speed

2019-02-28 Thread sqweek
ging the tempo is just a matter of adjusting the timing of the triggers and the samples don't need to be changed at all. I don't know if it's feasible for what you're trying to achieve, but does that make sense? -sqweek ___ fluid-dev ma

Re: [fluid-dev] Bug when calling SDL functions from sequencer callback

2018-11-18 Thread sqweek E.
callback post an event to be handled by some other thread. The details of how to accomplish that vary from platform to platform; for windows PostMessage is a fairly simple way to get an event to the thread responsible for the GUI. SDL might provide something more portable? HTH, -sqweek > On 19

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-09 Thread sqweek
the user organizes his soundfont collection. > > Yes organization soundfont is only the application need. As pointed by > Sqweek E " ...there’s no standard way to do this..". > > I don't think that fluidsynth package is the right place to define good > conventions like

Re: [fluid-dev] Allow soundfonts to be searched from multiple directories

2018-11-01 Thread sqweek E.
like standard search paths and/or configuration files - it would be great if the result could be adopted by other soundfont based software? -sqweek > On 2 Nov 2018, at 03:18, Carlo Bramini wrote: > > Hello, > if I can say my opinion, it would be better to leave that change

Re: [fluid-dev] Again on "Compile time constant lookup tables"

2018-09-21 Thread sqweek E.
avoid, because, again, there is no reason > to do so. Committing the generated code would nicely solve this. It’s a pretty clean way to prevent a build time dependency for users who don’t want to fiddle with the code imo. -sqweek ___ fluid-de

Re: [fluid-dev] Proposal for a new feature: lazy-loading of SoundFonts

2018-04-19 Thread sqweek
On 18 April 2018 at 20:11, Marcus Weseloh wrote: > 2018-04-18 11:10 GMT+02:00 sqweek : > > ie. there's a hard realtime requirement here in some usages - is it > still possible to meet that requirement with the samples being > loaded/unloaded? > > Please understand that

Re: [fluid-dev] Proposal for a new feature: lazy-loading of SoundFonts

2018-04-18 Thread sqweek
rising to a performer who is used to everything being available once the soundfont is loaded. To be clear I love the idea of being able to conserve memory by not loading unneeded samples, I just want to make sure it's not coming at the cost of the realtime use case. Cheers, -sqweek ___

Re: [fluid-dev] Android Support

2018-01-09 Thread sqweek
I chose not to install cmake (I've never had a good experience with it). And I'm biased in the sense that I'd love to see the glib dependency disappear (it's pretty annoying to build on non-linux systems! although it's only done once per platform so not a huge cost overall)

Re: [fluid-dev] fluidsynth and Unity ?

2017-05-23 Thread sqweek
It definitely works, I've built fluidsynth with no audio drivers in the past and used the nwrite_float() interface to generate samples to pass on to the audio layer (in my case portaudio -- which fluidsynth might even have a driver for but I wanted to be in control of the mixing). -sqweek

Re: [fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"

2015-11-05 Thread sqweek
15-September/54.html https://lists.columbia.edu/pipermail/portaudio/2015-October/000125.html -sqweek ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] Fluid_synth_write and sequencer queries

2014-05-02 Thread sqweek
nyone change it. That clears it up nicely. Thanks for your help David! Hope you have a great weekend. -sqweek ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] Fluid_synth_write and sequencer queries

2014-05-01 Thread sqweek
7;t synthesized until fluid_synth_write is called? Is 64 samples just an example number or is there something special about this block size? If so, is that 64 total samples including both channels (ie. 32 frames) or 64 samples per channel? Thanks for the suggestion, I would never have thought

Re: [fluid-dev] Fluid_synth_write and sequencer queries

2014-04-30 Thread sqweek
On 27 April 2014 12:14, sqweek wrote: > Is it reasonable to use the > frame number directly as the sequencer's 'tick' (ie. > fluid_sequencer_set_time_scale(seq, 1.0/44100.0) ) or is that too > fine? Sorry, after a second look at the API docs I see this is answered qui

[fluid-dev] Fluid_synth_write and sequencer queries

2014-04-26 Thread sqweek
fluid_sequencer_set_time_scale(seq, 1.0/44100.0) ) or is that too fine? Cheers, -sqweek ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev