|Subject:||Re: [fluid-dev] libinstpatch integration?|
|Date:||Fri, 6 Jun 2014 18:07:15 -0600|
Hey there,I recently tried Swami again for the first time in a few years and was really happy to see how far it's come and how stable it is!
Backstory: I found this beautiful 1.8 GB sf2 library called Evanessense (here: http://www.synthfont.com/punbb/viewtopic.php?id=167 ). Needless to say, the Calf Fluidsynth player wants to load the entire file into RAM and that's not working so well. Same goes for Qsynth, the DSSI fluidsynth plugin, etc. LinuxSampler refuses to load it due to some errors I didn't quite understand. I'm not super interested in using LinuxSampler anyway at this point in time. The whole single host/daemon thing is confusing to me right now.Well low and behold, Swami is the only way I was able to check this library out. It worked very well. There is a slight delay between switching patches, but that's way better than the whole computer locking up while 1.8 GB of unused samples are loaded into memory!
P.S. Here's a totally off the wall idea... to make an LV2 plugin based on Swami. That's kind of intriguing to me for some reason! But would probably be a good amount of work.So after investigating I realize that Swami is doing this using libinstpatch, and that there are plans from a while back to integrate libinstpatch into fluidsynth. Very exciting! What's the scoop on these plans? I'm tempted to try and hack libinstpatch support into the calf fluidsynth LV2 plugin or something just so I can use this Evanessense library. But if that would come automatically in a future fluidsynth release, it'd be an unnecessary effort.So anyhow, I'm curious about this. Right now I can't even have multiple instances of a 300 MB soundfont without really taking up lots of unnecessary memory. It'd be nice to change that.
|[Prev in Thread]||Current Thread||[Next in Thread]|