Pedro Lopez-Cabanillas wrote:
> On Friday, March 12, 2010, Felix Krause wrote:
>> I see the problem; fluid_curtime casts the seconds from glong to an
>> unsigned int, which leads to an overflow - especially when you multiply the
>> seconds with 1000. Are you on a 64bit linux? That might be the reas
On Friday, March 12, 2010, Felix Krause wrote:
> On 11.03.2010, at 21:05, David Henningsson wrote:
> > If the clock_time never advances beyond zero, it definitely looks like
> > some problem with fluid_curtime (or g_get_current_time in glib).
> >
> > Could it be a rounding problem? Please try this
On 11.03.2010, at 21:05, David Henningsson wrote:
>
> If the clock_time never advances beyond zero, it definitely looks like
> some problem with fluid_curtime (or g_get_current_time in glib).
>
> Could it be a rounding problem? Please try this change to fluid_curtime():
>
> unsigned int fluid_c
Felix Krause wrote:
> On 06.03.2010, at 19:09, David Henningsson wrote:
>> A debug print of the delay variable in fluid_timer_run might also be
>> helpful (just before the call to g_usleep).
>
> Here's what I got as debug output when rendering to a wave file with
> libsndfile:
>
> Sample_time =
On 06.03.2010, at 19:09, David Henningsson wrote:
> Felix Krause wrote:
>> On 04.03.2010, at 09:21, David Henningsson wrote:
>>> So the FS command (fluidsynth -a file -i -n -T wav -o
>>> audio.file.name=output.wav soundfont.sf2 midifile.mid) still just
>>> produces a 4 KB file? It works here.
>>
Felix Krause wrote:
> On 04.03.2010, at 09:21, David Henningsson wrote:
>> So the FS command (fluidsynth -a file -i -n -T wav -o
>> audio.file.name=output.wav soundfont.sf2 midifile.mid) still just
>> produces a 4 KB file? It works here.
>
> Yes, I still get a 4KB file.
Does it exit immediately o
On 04.03.2010, at 09:21, David Henningsson wrote:
> Felix Krause wrote:
fluidsynth -a file -i -n -T wav -o audio.file.name=output.wav
soundfont.sf2 midifile.mid
This just creates a 4KB file. Is it possible that this is a FS bug?
>>>
>>> I finally got some time to look at thi
Felix Krause wrote:
>>> fluidsynth -a file -i -n -T wav -o audio.file.name=output.wav
>>> soundfont.sf2 midifile.mid
>>>
>>> This just creates a 4KB file. Is it possible that this is a FS bug?
>>
>> I finally got some time to look at this issue. When I tried to run your
>> command I got a crash/bac
On 28.02.2010, at 11:13, David Henningsson wrote:
Felix Krause wrote:
On 11.02.2010, at 18:56, David Henningsson wrote:
I tested using FluidSynth 1.0.9 with raw output and that works with
my code - however, 1.1.1 does not. I also tested the FS command
line utility:
fluidsynth -F output.wa
Felix Krause wrote:
> On 11.02.2010, at 18:56, David Henningsson wrote:
> I tested using FluidSynth 1.0.9 with raw output and that works with my code -
> however, 1.1.1 does not. I also tested the FS command line utility:
>
> fluidsynth -F output.wav -i -n -T wav soundfont.sf2 midifile.mid
>
> T
On 11.02.2010, at 18:56, David Henningsson wrote:
> Felix Krause wrote:
>> Hi all,
>>
>> I'm trying to save FluidSynth's audio output into a file using the API. My
>> code basically does this:
>>
>> - get settings object with new_fluid_settings
>> - set audio.driver to "file"
>> - set audio.fil
Felix Krause wrote:
> Hi all,
>
> I'm trying to save FluidSynth's audio output into a file using the API. My
> code basically does this:
>
> - get settings object with new_fluid_settings
> - set audio.driver to "file"
> - set audio.file.* settings (tried different output types - raw, aiff, wav)
Hi all,
I'm trying to save FluidSynth's audio output into a file using the API. My code
basically does this:
- get settings object with new_fluid_settings
- set audio.driver to "file"
- set audio.file.* settings (tried different output types - raw, aiff, wav)
- create synth with new_fluid_synth
13 matches
Mail list logo
