Probably lacks an FPU, which means rather slow floating point emulation. The CPU just can't keep up in real-time. FluidSynth uses floating point math heavily.
Best regards, Element Green On Oct 12, 2012 11:06 AM, "Simon Eigeldinger" <simon.eigeldin...@vol.at> wrote: > Hi all, > > I am new to fluidsynth and i tried it to run it on my raspberry pi > computer. > its a small ARM board with a 700 mhz processor and 256 mb ram. > > When i tried it it played the file for a few seconds and then it strated > to kind of grind or hum. sounded like a saw wave tone got quite low but > went up and down the scale. > > here's the output of the console: > > $ fluidsynth -a alsa /usr/share/sounds/sf2/FluidR3_**GM.sf2 10.mid > > FluidSynth version 1.1.5 > Copyright (C) 2000-2011 Peter Hanappe and others. > Distributed under the LGPL license. > SoundFont(R) is a registered trademark of E-mu Systems, Inc. > > fluidsynth: warning: Failed to pin the sample data to RAM; swapping is > possible. > > Parameter '10.mid' not a SoundFont or MIDI file or error occurred > identifying it > . > fluidsynth: warning: Requested a period size of 64, got 256 instead > Type 'help' for help topics. > > fluidsynth: warning: Failed to set thread to high priority > fluidsynth: warning: Failed to set thread to high priority > > > > > Anyone knows thats wrong? > I also tried timidity but the annoying thing with it is that you have to > create a channels configuration file first before you are able to use the > soundfont. > > Any help appreciated. > Greetings, > Simon > > > ______________________________**_________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/**mailman/listinfo/fluid-dev<https://lists.nongnu.org/mailman/listinfo/fluid-dev> >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
