[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] File output with FluidSynth API

From: David Henningsson
Subject: Re: [fluid-dev] File output with FluidSynth API
Date: Thu, 04 Mar 2010 09:21:10 +0100
User-agent: Thunderbird (X11/20090817)

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/backtrace. I committed a fix (to trunk) that fixes
>> the crash I found, and I think that it will fix your issue as well.
>> The fix is here:
>> http://fluidsynth.resonance.org/trac/changeset/284/trunk/fluidsynth/src/fluid_midi.c
> Thanks for your effort. I checked out revision 284 and compiled it,
> but the problem is still the same. As I didn't have any crashes with 1.1.1,
> I don't notice any change of behaviour with the new code.

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.

> I should mention that I usually don't load midi files, but work with
> noteon / noteoff from the API, and tried playing midi files just for
> debugging. So it's unlikely that my problem lies in fluid_midi.

Hmm. Since I don't really know how to reproduce that issue here, can you
do some debugging for me? The file driver should create a thread that
calls fluid_synth_one_block every few milliseconds (via
fluid_file_renderer_process_block). This is not working for some reason.

Can you see if the thread is created correctly, and whether
fluid_file_audio_run_s16 (in fluid_aufile.c) calls
fluid_file_renderer_process_block periodically?

// David

reply via email to

[Prev in Thread] Current Thread [Next in Thread]