Search found 20 matches
- Mon Jun 22, 2009 5:22 am
- Forum: Newbies & Support
- Topic: Gigedit freezes on save
- Replies: 2
- Views: 2350
Re: Gigedit freezes on save
I had this exact same problem until recently when I reinstalled gigedit from the latest source on the CVS. I'm using Debian Lenny and Gigedit 0.1.1. Now it doesn't freeze when I save and there are fewer problems loading the files in qsampler. It's been my experience that it isn't worth the trouble t...
- Sat Mar 21, 2009 9:03 pm
- Forum: Newbies & Support
- Topic: LSCP memory problem, can't mlockall() warnings
- Replies: 5
- Views: 5153
Re: LSCP memory problem, can't mlockall() warnings
update: I got realtime scheduling to work and eliminated the realtime schedule warning, but I still get the "unable to cache sample" warning, the "some channel settings could not be set" dialog when I load the instrument, and the "could not remove channel" dialog and crash when I remove instruments....
- Sat Mar 21, 2009 8:27 pm
- Forum: Newbies & Support
- Topic: LSCP memory problem, can't mlockall() warnings
- Replies: 5
- Views: 5153
Re: LSCP memory problem, can't mlockall() warnings
Thanks for your response! The mlockall() warnings were in fact related to ulimits. I made my max memory lock unlimited and that got rid of the warnings. I still can't figure out how to give myself realtime priority (I'm in the audio group, and I added the line "@audio hard rtprio 99" to /etc/securit...
- Sat Mar 21, 2009 6:01 am
- Forum: Newbies & Support
- Topic: MIDI port connect failed
- Replies: 3
- Views: 3829
Re: MIDI port connect failed
Not sure about windows, but have you connected your keyboard to linuxsampler with ALSA MIDI in ubuntu? You can use qjackctl or aconnect to connect the keyboard and Rosegarden's MIDI output to linuxsampler's input.
- Sat Mar 21, 2009 5:51 am
- Forum: Newbies & Support
- Topic: LSCP memory problem, can't mlockall() warnings
- Replies: 5
- Views: 5153
LSCP memory problem, can't mlockall() warnings
Hi everyone, I've been having a weird problem with linuxsampler allocating memory for new samples. I compiled from the latest source on the CVS using dpkg-buildfile and the default config settings, running on a pentium 3 dell with debian testing. When I start qsampler, I get the following message: 0...
- Sun Mar 15, 2009 7:39 pm
- Forum: Newbies & Support
- Topic: Can linuxsampler run on libgig6
- Replies: 3
- Views: 2917
Re: Can linuxsampler run on libgig6
This is explained here.
- Sun Mar 15, 2009 6:20 pm
- Forum: Newbies & Support
- Topic: [solved] configure file can't find Jack or ALSA [debian]
- Replies: 3
- Views: 15581
Re: configure file can't find Jack or ALSA [debian]
That worked! Good looking out, grishata. Although I though dpkg-buildpackage was supposed to automatically tell you if there's unmet dependencies?
-B
-B
- Sun Mar 15, 2009 6:03 pm
- Forum: Newbies & Support
- Topic: Can linuxsampler run on libgig6
- Replies: 3
- Views: 2917
Re: Can linuxsampler run on libgig6
I got rid of libgig6 on my debian system by entering (as root): apt-get purge libgig6 This removes all of the libgig6 files, including configuration files. Then I was able to locally install linuxsampler's libgig package. Also, you should use synaptic/aptitude to hold your linuxsampler packages at t...
- Sat Mar 14, 2009 11:19 pm
- Forum: Newbies & Support
- Topic: [solved] configure file can't find Jack or ALSA [debian]
- Replies: 3
- Views: 15581
[solved] configure file can't find Jack or ALSA [debian]
Hello, I've been trying to get a working build of linuxsampler on my debian system. I'm using debian testing on a pentium 3 dell. Using the latest binary debian packages from linuxsampler I was unable to get gigedit to work (it would crash whenever I tried to save a file!), so I decided to build the...
- Sat Mar 14, 2009 12:42 am
- Forum: Newbies & Support
- Topic: Can not configure libgig
- Replies: 1
- Views: 2396
Re: Can not configure libgig
Did you obtain the source code through the cvs or did you download it from the website? If you didn't use the cvs, there won't be a Makefile.cvs file. I was getting similar errors until I switched to using the code from the cvs repository, since its the most up-to-date. Try compiling with the source...