Hello Joshua,
As you mentioned in your other email, there is no MIDI output ports from
FluidSynth. When you say "midi out on another channel" what MIDI driver
are you using? If it was the ALSA sequencer or JACK MIDI, you could
just have your MIDI source be a MIDI output port which gets connected
Hello David,
First off I'd like to say, thanks for your work in this area of
FluidSynth. Its been a long time wish of mine to be able to render MIDI
files to audio, in a faster than realtime fashion and with the same
output every time. This patch looks like the right direction to realize
this.
David Henningsson wrote:
> > * file output driver (fluid_aufile.c) uses another timer instance. This
> > should be fixed as well, to solve ticket #15.
>
> Agreed.
Please take into account that the file output can be used also without
rendering a MIDI file, when FluidSynth is used as a real time M
- -- wrote:
> Hello,
>
> I'm
> using fluidsynth with a cheap midi keyboard that has velocity but no
> way of turning it off. Can I get fluidsynth to ignore the velocity data
> with a midi router rule? I would like to keep velocity at a steady 127.
>
> Thanks!
>
> Ville Viitanen
Yes.
router_clear
Pedro Lopez-Cabanillas skrev:
> I'm not saying that it is trivial, but I think that it is possible and would
> be a very welcomed improvement. Issues of the current implementation that
> must be addressed:
Thanks for reviewing the patch!
> * file output driver (fluid_aufile.c) uses another time
I think Pedro answered you very well about the concurrency issue (which
is actually solved by removing one thread), and the midi resolution (64
samples).
As for the real problem, try to play a tune with "-o
audio.period-size=8192". I assume you can hear how terrible that sounds,
but if you don't t
Hello,
I'm
using fluidsynth with a cheap midi keyboard that has velocity but no
way of turning it off. Can I get fluidsynth to ignore the velocity data
with a midi router rule? I would like to keep velocity at a steady 127.
Thanks!
Ville Viitanen
aww man theres no midi out anyway
--
joshua higgins
>>--
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Hi,
I'm writing a custom control surface program for a touch screen which is
basically a wrapper that sends cc events to the running fluidsynth. This is
how I plan to have it set up:
control wrapper ---> fluidsynth ---> jack connected to ---> wineasio running
a FM7 vst
My question is how to get
Bernat Arlandis i Mañó wrote:
> Pedro Lopez-Cabanillas escrigué:
> >> perhaps the below implementation is better than the one in
> >> the patch posted earlier, but still bad, as it quits before all samples
> >> have reached the soundcard.
> >
> > Your former patch implements a "slave" timer, using
David Henningsson wrote:
> When you say option, do you mean as an #ifdef, or as an
> fluid_settings_xxx option?
Whatever you prefer.
> few days, would you (and the other developers) think that would make
> 1.0.9 wait for that patch or would you rather release 1.0.9 as quick as
> possible?
I thi
Pedro Lopez-Cabanillas escrigué:
perhaps the below implementation is better than the one in
the patch posted earlier, but still bad, as it quits before all samples
have reached the soundcard.
Your former patch implements a "slave" timer, using the frame counter from the
synthesizer itsel
Pedro Lopez-Cabanillas wrote:
> Your former patch implements a "slave" timer, using the frame counter from
> the
> synthesizer itself as a time source. I think it may be a right way to go.
>
> About the implementation, I would prefer to do it as an option, and not a
> replacement of the former
Hi,
David Henningsson wrote:
> If "fluidsynth -i" is supposed to wait for a MIDI file to finish and
> then quit,
The option "-i" (or "--no-shell") orders the FluidSynth CLI program that it
shouldn't read commands from the shell. When it is used *together with an
input MIDI file* as another pro
14 matches
Mail list logo
