R Dicaire wrote: > On Tue, Dec 30, 2008 at 3:42 PM, Adam Sampson <ats@xxxxxxxxx> wrote: > > >> This looks like the 2.6.26 MIDI sequencer problem -- MIDI doesn't work, >> and after jackd has opened the sequencer device for the first time, >> it'll hang trying to close it. Future attempts to open the sequencer >> device then fail because it's in use. >> > > Ahhhhhhhh, I was never aware there was a midi issue...jackd could be > killed when I didn't use -X, excellent. > Thank you VERY much. > hallo, i am not sure if it has anything to do with your issue, but as you say, it happens only when you start jackd with -Xseq, it could be that this is the root of the problem. i discovered a trouble in ardour, when running jackd with -Xseq explicitly. you may have a look here: http://tracker.ardour.org/view.php?id=2497 in this case, the issue for me is reproducible very easy, but only if running with -Xseq. ardour2.7.1, jackd0.116.1, alsa1.0.17, Linux 2.6.25.4-rt5 #2 PREEMPT RT know that this does not save your problem, but perhaps it is interesting. cheers, doc > Now here's another situation. I've built alsa and jack. I installed > them into custom locations. In my users .asoundrc > I have a pcm device that calls the jack plugin. How would I get calls > to this plugin to use my custom built > /usr/local/alsa/lib/alsa-lib/libasound_module_pcm_jack.so instead of > the system one in /usr/lib/alsa-lib ? > > _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
