Is this supposed to work? I don’t ever get a listening port on the latest Mac
(10.14.3), either with defaults or with -o shell.port set to a custom value.
I’m happy to take a closer look at fixing/adding this, but first wanted to see
if I’m missing something simple.
I have success with this o
quent conversion from wav to mp3 (using
the lame cmd binary) to be quicker, to avoid the lambda timing out.
Thanks!
Justin
On Sat, Dec 29, 2018 at 5:55 AM Tom M. wrote:
> > fluidsynth: error: Device does not exists
>
> For some reason fluidsynth starts the OSS audio driver rather
l ec2 instance, since I did no configuring of the audio driver there.
Thanks so much!
Justin
On Thu, Dec 27, 2018 at 8:41 AM Marcus Weseloh wrote:
> Hi Justin,
>
> Am Di., 25. Dez. 2018 um 02:36 Uhr schrieb Justin :
>
>> Cool, thanks! I've now set up a virtual EC2 instanc
I also
attempted to compile fluidsynth statically linked by running on the VM:
make SHARED=0 CC='gcc -static'
but using the executable made from this (in the src folder) failed as well
in the same way. I don't think that my attempt to compile the executable as
statically-linked act
especially uncertain
about doing this cross compilation, since it'll need to rely on libsndfile,
which presumably is built for mac osx on my machine.
Thanks,
Justin
On Sun, Dec 23, 2018 at 7:09 PM Marcus Weseloh wrote:
> Hi Justin,
>
> you probably compiled Fluidsynth without libsndfile
give me some advice for
how to figure out how to get this working? Or is there a better way for me
to get fluidsynth to work on AWS lambda?
Thanks!
Justin
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
