Summary: | Cannot load the second instrument (gig::Engine error: Failed to load instrument) | ||
---|---|---|---|
Product: | LinuxSampler | Reporter: | zehnan |
Component: | gig::Engine | Assignee: | Christian Schoenebeck <cuse> |
Status: | CLOSED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | SVN Trunk | ||
Hardware: | Other | ||
OS: | Linux |
Description
zehnan
2007-03-14 08:30:28 CET
It seems like this exception occurs while trying to cache the sample starts. You are using latest CVS version of libgig, linuxsampler, liblscp and qsampler, right? What is the audio fragment size you are using in this scenarion? You can check that in the "devices" dialog of qsampler. Does raising the audio fragment size avoid the problem? (In reply to comment #1) > You are using latest CVS version of libgig, linuxsampler, liblscp and > qsampler, right? I just picked the latest one to be sure. > What is the audio fragment size you are using in this scenarion? You can check > that in the "devices" dialog of qsampler. Normally I'd use jack with 64 frames, but I also tested everything with ALSA with both 128 and 256 fragment size. I just did some more testing and found out that I don't need to load two instruments, the error can happen using only one. Loading only PMI Bosendorfer 290 piano and its first instrument 'Wet B290 8-layer + sustain' I also get the same error. I do remeber this instrument working in previous versions of linuxsampler. On the other hand there is no problem loading lots of smaller gigs. It seems like the error comes up when using big gig files. My system is x86_64 if that's of any significance. Ok, so it's not the fragment size. Would you please check if you can use the command line tools 'gigdump' and 'gigextract' on that Gigasampler files and tell me whether it caused some errors or not? Those two tools usually come with libgig. Of course it could also be a x64 problem. I think none of the LS developers have a 64 bit box yet. So if you could test the same scenario on a 32 bit box, that might be helpful as well. I found the source of the problem and this is how I solved it. I raised my memlock in /etc/security/limits.conf from 250000 to 500000: @audio - memlock 500000 So, ulimit -l now reports 500000 and linuxsampler happily loads the big instruments that previously failed with the unknown exeption. Thanks, Marko |