From: Bill A. <ros...@ba...> - 2007-12-30 16:42:31
|
After updating to ubuntu gutsy, I find that rosegarden will no longer load some of my soundfonts. It gives the following messages: LADSPAPluginFactory::discoverPlugins - trace is fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible. fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible. fluidsynth: error: Out of memory fluidsynth: error: Failed to load SoundFont "/ramdisk/home/studio/music/soundfonts/GoldDrums.sf2" fluidsynth: error: Out of memory fluidsynth: error: Failed to load SoundFont "/ramdisk/home/studio/music/soundfonts/1276-Soft Tenor Sax.sf2" This is an AMD 64 system running in 64 bit mode. My system has plenty of free memory (about 500 meg), the GoldDrums font is about 12 meg and the tenor sax is about 5 meg, so that shouldn't be the problem. They have always loaded fine in the past and in fact they load fine when I boot into 64Studio which I usually use for music applications. Since the rt kernels have been supported by Ubuntu, I had hoped to start using it more for music, but without RG it's a no-go. Any ideas on what to look at? Regards, Bill |
From: Bill A. <ros...@ba...> - 2007-12-30 17:05:39
|
Bill Allen wrote: > After updating to ubuntu gutsy, I find that rosegarden will no longer > load some of my soundfonts. It gives the following messages: > > LADSPAPluginFactory::discoverPlugins - trace is fluidsynth: warning: > Failed to pin the sample data to RAM; swapping is possible. > fluidsynth: warning: Failed to pin the sample data to RAM; swapping is > possible. > fluidsynth: error: Out of memory > fluidsynth: error: Failed to load SoundFont > "/ramdisk/home/studio/music/soundfonts/GoldDrums.sf2" > fluidsynth: error: Out of memory > fluidsynth: error: Failed to load SoundFont > "/ramdisk/home/studio/music/soundfonts/1276-Soft Tenor Sax.sf2" > > This is an AMD 64 system running in 64 bit mode. > > My system has plenty of free memory (about 500 meg), the GoldDrums font > is about 12 meg and the tenor sax is about 5 meg, so that shouldn't be > the problem. They have always loaded fine in the past and in fact they > load fine when I boot into 64Studio which I usually use for music > applications. Since the rt kernels have been supported by Ubuntu, I had > hoped to start using it more for music, but without RG it's a no-go. > > Any ideas on what to look at? > > Regards, > Bill > One thing I forgot to point out. The soundfonts load and play perfectly when I use qsynth, so something is up with the fluidsynth plugin in rosegarden it seems. |
From: D. M. M. <mic...@ro...> - 2007-12-30 17:26:41
|
On Sunday 30 December 2007, Bill Allen wrote: > > Any ideas on what to look at? Where can I get the soundfont? I can test on 32-bit Ubuntu Studio anyway. If you have a 64-bit related problem, I'm afraid I can't investigate it from here. I tested the plugin with a gigantic (61 MB; not sure of the largest sample size) soundfont, and with Firefox leaking memory like a sieve, and I didn't get the "couldn't lock memory" errors, and it played fine in spite of the bad memory and CPU hogging environment. That makes me suspect my realtime setup is more robust than yours. Did you install the realtime kernel, and did you put the right bits into /etc/security/limits.conf? > One thing I forgot to point out. The soundfonts load and play perfectly > when I use qsynth, so something is up with the fluidsynth plugin in > rosegarden it seems. It's unlikely to have anything to do with Rosegarden itself, and just to be clear, the plugin isn't in Rosegarden as such. The plugins are installed independently. Separate packages, separate projects. It's just that we are AFAIK the only sequencer that can use the plugins directly, without a host. So let's see what happens when you run the plugin with a host. $ jack-dssi-host fluidsynth-dssi.so Rosegarden should pick that up as "MIDI software device 5" or something (see thread on the devel list where I have started thinking about how stupid this practice is) as you can see for sure by clicking the Manage MIDI Devices icon. Any problems? If no, then it's probably Rosegarden after all, but if the plugin behaves in the same bad way running in a host, then it's something else. What else? That's a good question! -- D. Michael McIntyre |
From: Bill A. <ba...@fa...> - 2008-01-02 03:23:33
|
Thanks for the quick response. Comments in line: D. Michael McIntyre wrote: > On Sunday 30 December 2007, Bill Allen wrote: > >>> Any ideas on what to look at? >>> > > Where can I get the soundfont? I can test on 32-bit Ubuntu Studio anyway. If > you have a 64-bit related problem, I'm afraid I can't investigate it from > here. > I've uploaded one of the files that is having a problem to http://soundfonts.ballen.fastmail.fm/ > I tested the plugin with a gigantic (61 MB; not sure of the largest sample > size) soundfont, and with Firefox leaking memory like a sieve, and I didn't > get the "couldn't lock memory" errors, and it played fine in spite of the bad > memory and CPU hogging environment. > > That makes me suspect my realtime setup is more robust than yours. Did you > install the realtime kernel, and did you put the right bits > into /etc/security/limits.conf? > > I'm using the realtime kernel from ubuntu just using standard apt-get install. I have set the right stuff into security.conf: @audio - rtprio 99 @audio - memlock 250000 @audio - nice -10 >> One thing I forgot to point out. The soundfonts load and play perfectly >> when I use qsynth, so something is up with the fluidsynth plugin in >> rosegarden it seems. >> > > It's unlikely to have anything to do with Rosegarden itself, and just to be > clear, the plugin isn't in Rosegarden as such. The plugins are installed > independently. Separate packages, separate projects. It's just that we are > AFAIK the only sequencer that can use the plugins directly, without a host. > > So let's see what happens when you run the plugin with a host. > > $ jack-dssi-host fluidsynth-dssi.so > > Rosegarden should pick that up as "MIDI software device 5" or something (see > thread on the devel list where I have started thinking about how stupid this > practice is) as you can see for sure by clicking the Manage MIDI Devices icon. > This worked fine. I loaded the soundfont using jack-dssi-host, then set that to be the output device for the track and it played fine. > Any problems? If no, then it's probably Rosegarden after all, but if the > plugin behaves in the same bad way running in a host, then it's something > else. What else? That's a good question! > Regards, Bill |