Hi,
I'm running fluidsynth on my RPi4:
$ nohup fluidsynth --server --audio-driver=alsa -c 4 -z 64 -r 19200
soundfont.sf2 &
And it creates a MIDI input port as expected:
$ aconnect -l
client 128: 'FLUID Synth (5344)' [type=User,pid=5344]
0 'Synth input port (5344:0)'
Have fun
Sven
On 0
Hi,
jOrgan is calling fluid_synth_set_chorus() and
fluid_synth_set_chorus_on(), in that order, both defined in synth.h
Best regards
Sven
On 02/25/2013 10:39 AM, David Henningsson wrote:
On 02/25/2013 10:06 AM, BCA wrote:
Hello David,
yes, we have those elements in jOrgan already, but when
you need anyway.
Best Regards
Sven
On 09/06/2012 01:01 AM, David Henningsson wrote:
On 09/05/2012 12:27 PM, Sven Meier wrote:
Hi David,
the new Fluidsynth version is now distributed as part of jOrgan 3.17
for Windows and OS X.
Many thanks to all developers.
Good to hear! Btw, have you starte
Hi David,
the new Fluidsynth version is now distributed as part of jOrgan 3.17 for
Windows and OS X.
Many thanks to all developers.
Sven
David Henningsson schrieb:
>FluidSynth 1.1.6 contains a few bug fixes, such as better MIDI
>End-of-track handling, broken sounds after voice overflow, and
Hi all,
Fluidsynth 1.1.6-rc1 is now under test by our jOrgan users:
http://sourceforge.net/projects/jorgan/files/jorgan-installer/3.17/
For those interested, the Fluidsynth 32bit dll is available separately too.
Best regards
Sven
___
fluid-dev maili
M, S. Christian Collins wrote:
Not to start volunteering people, but perhaps the jorgan guy (is his
name Sven Meier?) would be willing to test some things as well. I know
there are a few times his project has been hit by changes or bugs that
have become an issue for him. If he would be willing
Hi Pedro,
>a program should ... let the user know the problem and suggest the
possible solutions,
>like choosing another device, or restarting / reopening the audio
after connecting the old device
this is exactly how jOrgan is doing it.
So it would be great if fluidsynth could make sure that
Hi,
for jOrgan I use homebrew to build Fluidsynth on OS X:
http://sourceforge.net/apps/trac/fluidsynth/wiki/BuildingWithCMake#BuildingonOSX
I then use install_name_tool to tweak the loader_path of all
dependencies. This allows me to bundle all required libraries into my
application.
H
Hi David,
no complaints so far, seems 1.1.4 runs rock solid :).
Sven
On 07/30/2011 08:38 AM, David Henningsson wrote:
On 2011-07-20 19:37, Sven Meier wrote:
> a "release candidate" tarball, send it out for testing ... you would
be willing to help out with?
Sure, we have enough
Hi David,
> As a side note, I composed the wedding march myself ... using jOrgan,
FluidSynth
that sounds interesting. Any chance to get hands on your creation? Midi
file, recording or Youtube video?
> a "release candidate" tarball, send it out for testing ... you would
be willing to help o
Hi David,
thanks for your presentation.
It was interesting to learn the reasons behind the recent threading changes.
Best regards
Sven
On 05/13/2011 10:02 AM, David Henningsson wrote:
When I held my LAC presentation, I got some feedback saying that
FluidSynth is a well working program that wa
ed? I wonder how you were able to build
fluidsynth without the include.
Regards
Sven
On 04/14/2011 10:59 PM, Pedro Lopez-Cabanillas wrote:
On Thursday 14 April 2011, Sven Meier wrote:
Hi all,
I've just built fluidsynth on OS X but it seems I've forgotten some details on
how it worke
Hi Pedro,
my Mac has an Intel processor.
>Try with larger values like 256x2 (=512).
That did the trick, thanks. Now everything works as expected.
Regards
Sven
On 04/14/2011 11:15 PM, Pedro Lopez-Cabanillas wrote:
On Thursday 14 April 2011, Sven Meier wrote:
Hi,
> The other Mac
Hi all,
I've just built fluidsynth on OS X but it seems I've forgotten some details on
how it worked the last time ;).
I had to add an include to fluid_coreaudio.c or the build would have complained
about an undeclared 'ComponentDescription’:
#include
Any idea what might have required
Hi,
> The other Mac users on this list are also urged to report their
> experiences :-)
here's my report:
Fluidsynth starts and is loading the Soundfont correctly. Connecting
VMPK with Fluidsynth, the Midi indicator flashes and the messages dialog
is filled with fluidsynth:noteoff/fluidsynth:
Hi all,
in fluid_synth.c the documentation for fluid_synth_set_chorus() states
the following:
* @param level Chorus level (0.0-1.0)
However in synth.h I find the following:
#define FLUID_CHORUS_DEFAULT_LEVEL 2.0f /**<
Default chorus level */
Which one is wrong?
T
If you're just working with different tunings and don't really produce
atonal music, I'd recommend Fluidsynth's tuning support, see
fluid_synth_create_octave_tuning().
We're using it with jOrgan to define organ tunings (selectable via RPN
3) and it works like a charm.
Best regards
Sven
On 03
Hi Pedro and David,
I'm not sure whether the PulseAudio ALSA plugin is installed, it's a
standard Ubuntu 10.10 installation. Neither "asound-pulse.conf" nor
"asound.conf" are present.
Note that I'm not using Jack personally. I'm investigating the issue for
users of jOrgan, who use different
wrote:
On Tuesday 02 November 2010, Sven Meier wrote:
Hi all,
I'm experiencing a strange freeze in delete_fluid_alsa_audio_driver():
0x9da58ae5fluid_thread_join + 0x1d
0x9da4d388delete_fluid_alsa_audio_driver + 0x47
0x9da81c74delete_fluid_audio_driver + 0x59
The attempt t
Hi all,
I'm experiencing a strange freeze in delete_fluid_alsa_audio_driver():
0x9da58ae5fluid_thread_join + 0x1d
0x9da4d388delete_fluid_alsa_audio_driver + 0x47
0x9da81c74delete_fluid_audio_driver + 0x59
The attempt to join the (synthesizer?) thread never returns (line #332):
de
Hi,
I've tried to improve the wiki page 'BuildingWithCMake', so building
with MinGW should now be easier to follow.
Regards
Sven
Am 27.10.2010 19:50, schrieb Pedro Lopez-Cabanillas:
On Wednesday 27 October 2010, Dan Dietzer wrote:
Can someone give me an idea of what I am missing trying to
Hi David,
thanks for your interest. Our usage of fluidsynth is rather unusual, as
Bernds questions indicate. But it's great how everything works together.
In the next days I'll work on the debian package to sort out current
issues on Maverick.
Regards
Sven
On 10/01/2010 09:25 AM, David He
gelog is at:
https://sourceforge.net/apps/trac/fluidsynth/wiki/ChangeLog1_1_2
For this release, I would like to give a big thanks to:
* Pedro Lopez-Cabanillas, for the new build system, and a lot of bug
fixes
* The jOrgan community (Sven Meier, Bernd Casper, and others) who
have been
Hi David,
+1 on releasing 1.1.2 soon.
Thanks
Sven
On 08/28/2010 02:55 PM, David Henningsson wrote:
A few more weeks have passed and I've had a lot to do (both work-wise
and family-wise), but I've updated the documentation, and I don't think
we have any critical bugs at the moment.
So, am I m
So if we were to remove the winbuild directory altogether ... does that sound
fair enough to everyone?
Yes please, this directory should be removed.
Sven
On 07/16/2010 07:35 PM, David Henningsson wrote:
2010-07-16 17:29, Pedro Lopez-Cabanillas skrev:
On Friday, July 16, 2010, Elimar Gre
Hi Pedro,
yes, I'm building fluidsynth on Windows with CMake and mingw.
I don't really care about the library name, it should just stay
consistent for the next releases.
Sven
On 07/15/2010 10:06 AM, Pedro Lopez-Cabanillas wrote:
On Wednesday, July 14, 2010, Sven Meier wrote:
Hi David,
building fluidsynth with MinGW results in "libfluidsynth.dll",
previously the library was named "libfluidsynth-1.dll". Is this change
intended?
Regards
Sven
Am 14.07.2010 11:34, schrieb David Henningsson:
Okay, so the new architecture is in place and seems to work well so far
(at
Hi David,
I've just tested your changes here and can confirm that the reordering
issues are fixed.
I'm testing synth.threadsafe-api now to see whether it makes a noticable
difference.
BTW does the new cmake based build work on Windows already?
Thanks for your efforts.
Sven
On 07/01/2010 0
Hi David,
> Any objections to me organizing the source files in subdirectories?
+1, sounds good to me.
Sven
On 06/20/2010 01:15 PM, David Henningsson wrote:
So my thoughts about the voice renderer and the state machine continues
- what I think now is the correct way to fix Sven's and everybod
ssues no longer exist. Hopefully in the
next month or two.
Best regards,
Elimar
On Sat, Jun 5, 2010 at 7:45 AM, Sven Meier mailto:s...@meiers.net>> wrote:
Hi Elimar,
first let me thank you for your efforts on Fluidsynth, especially
for the recent migration to Sourceforge.
ll try and get around to reviewing this soon. Perhaps there was
some mailing list traffic around revision 277 that would clarify
why the queuing got reverted.
Regards,
Elimar
On Fri, Jun 4, 2010 at 2:01 PM, Graham Goode http://ggoode.sa>@gmail.com <http://gmail.com&g
David Henningsson wrote:
Sven Meier wrote:
Hi all,
I'm tinkering with FluidSynth's support for Midi Tuning Standard, my
code is calling fluid_synth_create_octave_tuning() and so far it works
great.
But now my question:
As soon as I send a "Reset all controllers" (12
Hi all,
I'm tinkering with FluidSynth's support for Midi Tuning Standard, my
code is calling fluid_synth_create_ocate_tuning() and so far it works great.
But now my question:
As soon as I send a "Reset all controllers" (121) controller change,
FluidSynth seems to ignore my tuning configurati
33 matches
Mail list logo
