From: Pieter B. <pi...@re...> - 2010-05-09 22:00:53
|
Hi Tim and Robert, Thanks for your replies. Robert, I just installed a RT kernel on my Ubuntu system (Karmic, 9.10). The kernel version is 2.6.31.9-rt, I can choose it in GRUB when I boot. I can start QJackCTL and Muse, but when I try to open the "FluidR3_GM.sf2" for FluidSynth, the terminal in which I started MusE says: fluidsynth sampleRate 44100 JACK ERROR: zombified - calling shutdown handler Audio::shutdown() Panic! no _client! Panic! no _client! It does so every time. However, QJackCTL doesn't have any "xruns" until that point - then it shows: Jack msg: **** alsa_pcm: xrun of at least 0.557 msecs 23:35:20.627 XRUN callback (1). 23:35:20.751 JACK connection change. So unfortunately I cannot use MusE with this kernel right now...? ----------------------------------------------------------------------- When I use the "normal kernel", QJackCTL reports several xruns before I even open MusE properly. When I choose the MIDI connector in MusE and play something on my keyboard, there are quite a few xruns in the QJackCTL messages: 23:40:08.437 Server configuration saved to "/home/pieter/.jackdrc". 23:40:08.438 Statistics reset. 23:40:08.990 Client activated. 23:40:08.991 JACK connection change. 23:40:08.993 JACK connection graph change. 23:40:13.107 ALSA connection graph change. 23:40:13.195 ALSA connection change. **** alsa_pcm: xrun of at least 12.313 msecs 23:40:13.246 XRUN callback (1). 23:40:13.842 JACK connection graph change. 23:40:13.997 JACK connection change. subgraph starting at qjackctl timed out (subgraph_wait_fd=9, status = 0, state = Triggered, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.431 msecs **** alsa_pcm: xrun of at least 13.057 msecs 23:40:14.297 JACK connection graph change. **** alsa_pcm: xrun of at least 8.522 msecs subgraph starting at MusE-1 timed out (subgraph_wait_fd=21, status = 0, state = Triggered, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.434 msecs subgraph starting at MusE-1 timed out (subgraph_wait_fd=21, status = 0, state = Triggered, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.454 msecs **** alsa_pcm: xrun of at least 3.934 msecs 23:40:14.770 ALSA connection graph change. **** alsa_pcm: xrun of at least 7.971 msecs **** alsa_pcm: xrun of at least 13.115 msecs **** alsa_pcm: xrun of at least 14.862 msecs 23:40:14.999 XRUN callback (9 skipped). **** alsa_pcm: xrun of at least 2.160 msecs **** alsa_pcm: xrun of at least 6.420 msecs 23:40:19.023 XRUN callback (12). **** alsa_pcm: xrun of at least 16.696 msecs 23:40:23.247 XRUN callback (13). **** alsa_pcm: xrun of at least 11.982 msecs 23:40:54.635 XRUN callback (14). **** alsa_pcm: xrun of at least 10.084 msecs **** alsa_pcm: xrun of at least 11.580 msecs **** alsa_pcm: xrun of at least 8.151 msecs **** alsa_pcm: xrun of at least 14.414 msecs 23:40:55.160 XRUN callback (4 skipped). 23:41:01.319 ALSA connection graph change. **** alsa_pcm: xrun of at least 1.874 msecs 23:41:03.239 XRUN callback (19). **** alsa_pcm: xrun of at least 9.733 msecs 23:41:33.243 XRUN callback (20). **** alsa_pcm: xrun of at least 5.551 msecs 23:41:56.980 XRUN callback (21). **** alsa_pcm: xrun of at least 8.550 msecs **** alsa_pcm: xrun of at least 14.267 msecs **** alsa_pcm: xrun of at least 7.669 msecs 23:41:59.220 XRUN callback (24). 23:41:59.300 XRUN callback (2 skipped). **** alsa_pcm: xrun of at least 14.459 msecs 23:42:03.243 XRUN callback (25). subgraph starting at MusE-1 timed out (subgraph_wait_fd=21, status = 0, state = Triggered, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.505 msecs 23:43:14.811 XRUN callback (26). **** alsa_pcm: xrun of at least 6.838 msecs **** alsa_pcm: xrun of at least 13.045 msecs 23:43:15.431 XRUN callback (2 skipped). **** alsa_pcm: xrun of at least 9.398 msecs **** alsa_pcm: xrun of at least 5.808 msecs 23:43:19.475 XRUN callback (30). **** alsa_pcm: xrun of at least 3.878 msecs 23:44:33.427 XRUN callback (31). subgraph starting at MusE-1 timed out (subgraph_wait_fd=21, status = 0, state = Triggered, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.486 msecs 23:44:43.657 XRUN callback (32). **** alsa_pcm: xrun of at least 180.147 msecs 23:44:43.977 XRUN callback (1 skipped). **** alsa_pcm: xrun of at least 6.508 msecs 23:44:54.076 XRUN callback (34). **** alsa_pcm: xrun of at least 9.086 msecs **** alsa_pcm: xrun of at least 10.462 msecs **** alsa_pcm: xrun of at least 8.737 msecs **** alsa_pcm: xrun of at least 6.844 msecs **** alsa_pcm: xrun of at least 9.734 msecs 23:44:56.019 XRUN callback (5 skipped). When there are multiple xruns in a row, it sounds like the "major glitch" from my video. By the way, I chose Priority 50, Input Device "USB MS1x1 MIDI Interface" and Out Device "AD198x Analog". Something else, I looked how QJackCTL starts Jackd. This is the text in the Message window when I start it: 23:32:54.682 Patchbay deactivated. 23:32:54.685 Statistics reset. 23:32:54.717 ALSA connection graph change. 23:32:54.915 ALSA connection change. 23:33:19.588 Startup script... 23:33:19.590 artsshell -q terminate sh: artsshell: not found 23:33:19.992 Startup script terminated with exit status=32512. 23:33:19.992 JACK is starting... 23:33:19.993 /usr/bin/jackd -P50 -p512 -dalsa -r44100 -p512 -n2 -D -Chw:1 -Phw:0,0 23:33:19.996 JACK was started with PID=2929. jackd 0.118.0 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns JACK compiled with System V SHM support. loading driver .. apparent rate = 44100 creating alsa driver ... hw:0,0|hw:1|512|2|44100|0|0|nomon|swmeter|-| 32bit control device hw:0 ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 2 periods ALSA: final selected sample format for playback: 16bit little-endian ALSA: use 2 periods for playback 23:33:22.124 Server configuration saved to "/home/pieter/.jackdrc". ----------------------------------------------------------------------- That's it, I hope you have an idea how I can fix this. Thanks :) Pieter On Sat, 2010-05-08 at 14:40 -0400, Tim E. Real wrote: > On May 8, 2010 07:26:22 am Pieter Barendrecht wrote: > > Hi, I just started working with MusE. Great sequencer :). > > > > The first thing I tried to do was record some MIDI with my Yamaha > > keyboard. This works, although when I immediately use the FluidSynth > > samples there is some latency. > > > > However, sometimes during recording or when I later playback the > > recording (using the FluidSynth samples), the sound glitches. I just > > made a small video of what I mean, it is on YouTube (quality not very > > good): http://www.youtube.com/watch?v=9Sn6qDLSuNE > > > > I use MusE 1.01, my QJackCTL is version 0.3.6. The QJackCTL settings > > are: > > Realtime, Frames/Period 512, Sample Rate 44100, Periods/Buffer 2, Port > > Maximum 512, Timeout 500. Latency is 23.2 ms. > > I don't know much about these parameters, so they could be entirely > > wrong for my situation ;) > > > > --- > > > > There is something else: when I record (without playback), sometimes the > > sequencer skips a beat or something. This is rather annoying, how should > > I fix this? I read something about the -R parameter, but this doesn't > > exist anymore. I guess I have to use -P now, but I have to type a number > > and I don't know the meaning of this number (i.e. sudo muse -P 50). > > > > --- > > > > Thanks in advance for an answer, I really hope it is possible to fix > > these issues and use MusE to record entire songs. > > > > Pieter > > > > PS: I use Ubuntu 9.10, Karmic Koala. My Laptop is a Lenovo Thinkpad T60. > > Hi Pieter! > > I think the problem is that in QJackCtl, you need to select an Input Device > and Output Device other than 'default', which is not the best. > Click the arrows next to them, and choose an appropriate device > labelled HW:xx. These are the good HardWare interfaces. > > (If you had been seeing 'XRuns' in QJackCtl's window (the red numbers) > then you know that all is not well, those cause the glitches.) > > Also, set QjackCtl's Priority setting to something other than 'default', > say 50 or so. > > You should not need to run run MusE as root with sudo, or worry about > MusE command line switches for now. > > Sometimes it helps to be sure of how QJackCtl is actually starting Jack. > If you turn on 'verbose messages' and 'capture standard output' > and read the messages, you'll see the command line used to start Jack. > There should be a '-R' (realtime) somewhere in that line. > Watch for other warnings or errors. > Feel free to post the messages if unsure. > > Try that and let me know. > Tim. > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |