On Thursday 14 April 2011, Sven Meier wrote:
> 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 th
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 worked the last time ;).
>
> I had to add an include to fluid_coreaudio.c or the build would have
> complained about an undeclared 'ComponentDescrip
On Apr 14, 2011, at 4:25 PM, Sven Meier wrote:
BTW why is it that the resulting shared library is named
"Fluidsynth"? Wouldn't libfluidsynth.dylib be more appropriate?
Sven
Many thanks for your testing earlier.
If you build with the enable-framework option you will build an OS X
framewor
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
On Apr 13, 2011, at 5:25 PM, Pedro Lopez-Cabanillas wrote:I've attached a document containing the terminal output and the qsynth console output when lauching qsynth with the following commands:$ export DYLD_PRINT_LIBRARIES=1$ open qsynth.appPedroThe Terminal.app outputs from both your setup and min
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:
