Bugreport
Hi :)
MusE seems to have many interesting functions, very near to Cubase. I don't know Cakewalk myself, I just heard of it and MusE might be orientated at Cakewalk, maybe it's not very different to Cubase. The bug(s) for MusE are less important, it's more important that this is the kind of bug I get with any setup. I can't get a sound done by MusE, resp. fluidsynth. I resumed the settings for MusE at the end of this mail. After a while, when saving the project again (I did it several times before) I got an error. Similar to the errors I got when using Rosegarden. "Jack shutdown! Jack has detected a performance problem which has lead to MusE being disconnected. This could happen to a number of reasons: - a performance issue with your particular setup. - a bug in MusE (or possible in another connected software). - a random hiccup which might never occur again. - jack was valuntary stopped by you or someone else - jack crashed If there is a persisting problem you are much welcome to discuss it on MusE mailinglist. (there is information about joining the mailinglist on MusE homepage which is available through the help menu) To proceed check the status of Jack and try to restart it and then click on the Restart button." I closed MusE. QJackCtl seems to be fine, but after running MusE again and loading the started project, MusE crashed and disappeared. I could start MusE and load the project after closing QJackCtl. I could start MusE after QJackCtl was running, but it crashes again and disappeared after I tried to load the project. In the past I could run QSampler with my other 64 Studio and it also crashed when trying to load a GIG. It seems to be that Jack isn't fine with my Suse 11.0, 64 Studio Lenny and 64 Studio default. I tried another session, but the bug was still there. I restarted the computer and after launching jack I got: "18:40:34.561 Patchbay deactivated. 18:40:34.572 Statistics reset. 18:40:34.619 Startup script... 18:40:34.619 artsshell -q terminate JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] 18:40:34.625 MIDI connection graph change. can't create mcop directory Link points to "/tmp/ksocket-spinymouse" 18:40:35.172 Startup script terminated with exit status=256. 18:40:35.172 JACK is starting... 18:40:35.172 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p128 -n2 18:40:35.174 JACK was started with PID=4530 (0x11b2). jackd 0.103.0 Copyright 2001-2005 Paul Davis 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 JACK compiled with System V SHM support. loading driver .. Enhanced3DNow! detected SSE2 detected apparent rate = 48000 creating alsa driver ... hw:0|hw:0|128|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa no message buffer overruns 18:40:35.323 JACK was stopped successfully. 18:40:35.323 Post-shutdown script... 18:40:35.323 killall jackd jackd: no process killed 18:40:35.375 MIDI connection change. 18:40:35.544 Post-shutdown script terminated with exit status=256. 18:40:37.389 Could not connect to JACK server as client. Please check the messages window for more info. JACK tmpdir identified as [/dev/shm]" Also something I know very well. I shutdown the computer and turned it on again. Running QJackCtl was fine, but there was still the bug for MusE. Without running QJackCtl MusE was fine again. QJackCtl + QSampler and a loaded GIG + Rosegarden and a loaded project with lots of Fluidsynth DSSIs seems to be fine, I didn't tested audio (mixer and amp were not turned on), but there were no crashes after loading and playing Rosegarden. Independent if there is ab bug for MusE, this behavior is something that will happen with any setup. Can the on-board graphic, the shipset or soundcard cause this troubles? Cheers, Ralf JACK Control > Setup... Frames/Period: 128 Sample Rate: 48000 Periodes/Buffer:2 Audio and MIDI was connected MusE > Settings > Global Settings > MIDI RTC Resolution (Ticks/Sec) 1024 Displayed resolution (Ticks/Quaternote) 384 > Settings > Metronome Audio Beep disabled MIDI Click disabled > Settings > MIDI Ports / Soft Synth > Soft Synthesizer > fluidsynth > Add Instance = *Inst for fluidsynth 2 (I added one instance and removed it before, it should be 1 instead of 2) Port 1, Instrument fluidsynth-1, Device Name fluidsynth-1, State OK Load: /mnt/music_sata/mix_vol_1.sf2/Acoustic drum set.SF2 Ctrl+J (Add MIDI Track) pencil to create segment (called "part") Mixer: Out 1 mono, iR: fluidsynth-1, oR: playback_1, playback_2 fluidsynth-1: oR: Out 1 MIDI Track 1: *1 (fluidsynth-1), OCh:1, *input ports all, input channels all Nothing is filtered for MIDI, all faders and fluidsynth gain have a value, nothing is muted Save: /home/spinymouse/Desktop/Test/MusE_Test.med The only other application also running, was AbiWord*and maybe for a short time Iceweasel. _______________________________________________ 64studio-users mailing list 64studio-users@64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users |
Bugreport
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Two things. First, are you sure that jack is trying to use the correct sound device? This line seems to indicate that either you are using the incorrect device or you have an application that is blocking jack: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa Second, you may have your timings set too aggressively for your hardware. I have seen this error many times before and it has always been a configuration error on my part. Hth, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIwDknwRXgH3rKGfMRAnmYAJ9bZg0fzo4ernT8mPSFdM n+B9f0lQCfcELP 65LNS1c7GvZdzhrXht8Ksds= =VhnI -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list 64studio-users@64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users |
Bugreport
Gustin Johnson wrote:
> Two things. > > First, are you sure that jack is trying to use the correct sound device? > This line seems to indicate that either you are using the incorrect > device or you have an application that is blocking jack: > > ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to > capture-only mode > cannot load driver module alsa Okay, this is the message that often comes after rebooting after something crashed. After a reboot there can't be any application block jackd. Or can there be an application after startup doing this? I'll set /etc/modprobe.d/alsa-base to give the devices consistent numbers. I'll set it to # Fix indexes for the spymo DAW alias snd-card-0 snd-ice1712 options snd-ice1712 index=0 alias snd-card-1 snd-usb-audio options snd-usb-audio index=1 After booting, when there was no crash before, the Envy24 card will always be hw:0 and the USB MIDI IO will always be hw:1, but it might be more safe to fix the indexes. I'm not sure if the USB device was hw:0, instead of the TerraTec, that should be hw:0. > Second, you may have your timings set too aggressively for your hardware. > > I have seen this error many times before and it has always been a > configuration error on my part. The error above or the error for the crash with MusE? Are Envy24 cards not fine with Linux? I often read that latencies should be better with Linux as with Windows. I set it to 128 / 2 @ 48000Hz because of the sync problems and MIDI jitter, only set to this the sync and jitter is okay. I can increase it, I'm fine with higher latency and sync and jitter might be fine with increased values after installing a NVidia, I'm still using the on-board ATI. If I'll increase the values at the moment, I'll have to bad sync and to much MIDI jitter. MIDI jitter seems to collaborate somehow with the audio settings. Anyway, I'll try to increase it and will live with jitter for the moment. I never run into trouble when Rosegarden is playing some Fluidsynth DSSIs and QSampler. Crashes for Rosegarden or QSampler only will happen, if I'm editing with the mouse or playing events by the USB MIDI in. I can't say much about MusE. What settings should I try for jackd? 256 / 2, 128 / 3 or much higher settings? I've got no XRUNS or unwanted noise when set to 128 / 2. Everything seems to be fine with lower settings, but I won't get lower, because this is suspect. Okay, I'll set the values higher, but can this really be the reason for the crashes I get? Shouldn't there be XRUNS and destroyed sound before crashes? Thank you, Ralf _______________________________________________ 64studio-users mailing list 64studio-users@64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users |
Bugreport
Hi :)
I tested my DAW from 02:02 o'clock 09/11/2008 to 00:32 o'clock 09/12/2008. I checked the BIOS hardware monitoring and run Memtest from 02:02 09/11/2008 to 11:25. Everything was fine. At 21:46 I started playing a loop until 00:30 09/12/2008, without getting any XRUNS for the whole time, before doing this all applications where ready to play, but they nearly had nothing to do, than to stand by. Still everything was fine. After 00:30 I set a new loop and tried to record. Rosegarden crashed within the first events. The computer didn't crash for more than 22 hours, from 02:02 09/11/2008 to 00:30 09/12/2008, but when trying to record MIDI events it crashed without respite. I'll send a detailed report with the next mail. It's a long AbiWord.abw including a screenshot.png, so the server might block this mail until an administrator will unblock it. Cheers, Ralf _______________________________________________ 64studio-users mailing list 64studio-users@64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users |
Bugreport
Hi Ralf,
> I'll send a detailed report with the next mail. It's a long AbiWord.abw > including a screenshot.png, so the server might block this mail until an > administrator will unblock it. It's a bit large for the mailing list, but I've downloaded it here. Thanks for the tests! Daniel _______________________________________________ 64studio-users mailing list 64studio-users@64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users |
Bugreport
Daniel James wrote:
> Hi Ralf, > >> I'll send a detailed report with the next mail. It's a long >> AbiWord.abw including a screenshot.png, so the server might block >> this mail until an administrator will unblock it. > > It's a bit large for the mailing list, but I've downloaded it here. > > Thanks for the tests! > > Daniel Hi Daniel :) I guess this test wasn't a help for me or anybody else, but I wished to know what will happen, if the computer has audio applications opened for a long time, when they are not under use and if there are any needful messages. Yesterday I tried to make a demo. A Band is looking for a singer, because their singer won't do the tour. I was getting a cold - today I've got a cold ;) - so I was in a hurry with canceling the vocals of the original singer from the CD tracks and recoding my vocals. Rosegarden might not be the best chose for HD recording, but because I'm familiar with it, I started with Rosegarden. First I used Rosegarden 1.7.1 and the 2.6.24 rt kernel, than I reinstalled the 64 Studio default Rosegarden and tested it with the 2.6.24 and the 2.6.21 kernels, after this I changed from 64 Studio to Suse, it was always the same. When ready with recording or exporting an audio track Rosegarden crashed with a segmentation fault. I tried Ardour with Suse (2.6.25) and it was fine, I changed back to 64 Studio and go on with Ardour and kernel 2.6.24 and it was fine. I don't know how to use Ardour, so I made mistakes, I was getting a cold, so I made mistakes, but Ardour, DJ EQ, Jack, JAMin and Audacity where fine, no crashes and good latencies. Just splitting regions for Ardour didn't work and I had no time to read a manual. Anyway, HD recording with Ardour is stable, with my chipset and while using the on-board graphics. Only one time Ardour said, there was a problem with the HDD, so it didn't started to record. recording after closing this message was fine and I didn't get any error or warning again. Just MIDI applications like Rosegarden become more worse. Some time ago I could record some MIDI events and audio tracks, with to much crashes, but recording was possible. The only thing I changed was the BIOS and it's protected against downgrades :D, so I can't restore the old BIOS. It's not so bad, because the old BIOS won't be really a solution. Even if I use Rosegarden just as HD recorder, without any MIDI clients connected it crashes. I wonder why everything is fine, Ardour, Gimp, Icedove etc. and only MIDI applications like Rosegarden, Muse, QSynth make troubles. It was good that I was forced to use Ardour. Ardour and Jack didn't crash. If Jack crashes when in use with Rosegarden, than it seems not to be the blame of Jack. Cheers, Ralf _______________________________________________ 64studio-users mailing list 64studio-users@64studio.com http://lists.64studio.com/mailman/listinfo/64studio-users |
bugreport
(I)*** x.org loaded video driver of...
(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so (II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so (II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so (II) Unloading /usr/lib/xorg/modules/drivers//fbdev_drv.so (II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so (--) Depth 24 pixmap format is 32 bpp (III)* Desktop is: GNOME (IV)** openoffice.org-kde version is: package openoffice.org-kde is not installed (V)*** libgcj version is: libgcj-4.3.2-7-i386 (VI)** kernel is: Linux 2.6.27.7-134.fc10.i686 #1 SMP Mon Dec 1 22:42:50 EST 2008 i686 i686 i386 (VII)* OpenOffice.org core rpm version is: openoffice.org-core-3.0.0-9.10.fc10-i386 (VIII) accessibility is: false (IX)** fedora release is: Fedora release 10 (Cambridge) (X)*** LANG is: zh_CN.UTF-8 ...start free space details ... 文件系统************** 1K-块******* 已用**** 可用 已用% 挂载点 /dev/sda7************ 45856324** 4462128* 39064776* 11% / /dev/sda7************ 45856324** 4462128* 39064776* 11% / ...end free space details ... ...start (default) java details ... java version "1.6.0_0" IcedTea6 1.4 (fedora-7.b12.fc10-i386) Runtime Environment (build 1.6.0_0-b12) OpenJDK Client VM (build 10.0-b19, mixed mode) ...end (default) java details ... ...start sestatus details ... SELinux status:**************** enabled SELinuxfs mount:*************** /selinux Current mode:****************** enforcing Mode from config file:********* enforcing Policy version:**************** 23 Policy from config file:******* targeted ...end sestatus details ... ...start stackreport details ... 0x45c6c4: 0x1b4a38: /usr/lib/openoffice.org3/program/../basis-link/ure-link/lib/libuno_sal.so.3 + 0x256c4 0x45cfff: 0x1b4a38: /usr/lib/openoffice.org3/program/../basis-link/ure-link/lib/libuno_sal.so.3 + 0x25fff 0x110400: 0x0:* + 0x400 (__kernel_sigreturn + 0x0) 0x2c4e28: 0x16fd7c: /lib/libc.so.6 + 0x2ce28 (abort + 0x188) 0x2bc40e: 0x16fd7c: /lib/libc.so.6 + 0x2440e (__assert_fail + 0xee) 0x14a25ab: 0xfd268: /usr/lib/libX11.so.6 + 0x425ab 0x1897121: 0x82020: /usr/lib/libGL.so.1 + 0x50121 ...end stackreport details ... ...start sample ldd details ... *** linux-gate.so.1 =>* (0x00110000) *** libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00296000) *** libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00158000) *** libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x001ed000) *** libgio-2.0.so.0 => /lib/libgio-2.0.so.0 (0x0067c000) *** libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x0020a000) *** libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00234000) *** libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00251000) *** libcairo.so.2 => /usr/lib/libcairo.so.2 (0x006ef000) *** libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00767000) *** libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x007ad000) *** libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00840000) *** libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x0025c000) *** libgthread-2.0.so.0 => /lib/libgthread-2.0.so.0 (0x00260000) *** librt.so.1 => /lib/librt.so.1 (0x00265000) *** libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x0086f000) *** libdbus-1.so.3 => /lib/libdbus-1.so.3 (0x0088d000) *** libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x008ce000) *** libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x0090f000) *** libvclplug_genli.so => /usr/lib/openoffice.org/basis3.0/program/libvclplug_genli.so (0x009f2000) *** libvclli.so => /usr/lib/openoffice.org/basis3.0/program/libvclli.so (0x00a5f000) *** libpspli.so => /usr/lib/openoffice.org/basis3.0/program/libpspli.so (0xb8021000) *** libsotli.so => /usr/lib/openoffice.org/basis3.0/program/libsotli.so (0xb7fd3000) *** libutlli.so => /usr/lib/openoffice.org/basis3.0/program/libutlli.so (0xb7f64000) *** libtlli.so => /usr/lib/openoffice.org/basis3.0/program/libtlli.so (0xb7ee2000) *** libcomphelp4gcc3.so => /usr/lib/openoffice.org/basis3.0/program/libcomphelp4gcc3.so (0xb7df7000) *** libucbhelper4gcc3.so => /usr/lib/openoffice.org/basis3.0/program/libucbhelper4gcc3.so (0xb7d9d000) *** libuno_cppuhelpergcc3.so.3 => /usr/lib/openoffice.org/basis3.0/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3 (0xb7d25000) *** libuno_cppu.so.3 => /usr/lib/openoffice.org/basis3.0/program/../ure-link/lib/libuno_cppu.so.3 (0x00d53000) *** libvos3gcc3.so => /usr/lib/openoffice.org/basis3.0/program/libvos3gcc3.so (0xb7d03000) *** libuno_sal.so.3 => /usr/lib/openoffice.org/basis3.0/program/../ure-link/lib/libuno_sal.so.3 (0xb7b47000) *** libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00d80000) *** libX11.so.6 => /usr/lib/libX11.so.6 (0xb7a46000) *** libXext.so.6 => /usr/lib/libXext.so.6 (0x00d87000) *** libdl.so.2 => /lib/libdl.so.2 (0x00d97000) *** libpthread.so.0 => /lib/libpthread.so.0 (0xb7a2c000) *** libstlport_gcc.so => /usr/lib/openoffice.org/basis3.0/program/../ure-link/lib/libstlport_gcc.so (0xb7961000) *** libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb786f000) *** libm.so.6 => /lib/libm.so.6 (0xb7846000) *** libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7838000) *** libc.so.6 => /lib/libc.so.6 (0xb76c4000) *** libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x0026f000) *** libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb76c0000) *** libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb76bb000) *** libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb7693000) *** libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb768a000) *** libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb7686000) *** libXi.so.6 => /usr/lib/libXi.so.6 (0xb767d000) *** libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb7673000) *** libselinux.so.1 => /lib/libselinux.so.1 (0xb7657000) *** libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb7610000) *** libz.so.1 => /lib/libz.so.1 (0xb75fb000) *** libexpat.so.1 => /lib/libexpat.so.1 (0xb75d4000) *** /lib/ld-linux.so.2 (0x00273000) *** libnsl.so.1 => /lib/libnsl.so.1 (0xb75ba000) *** libcap.so.2 => /lib/libcap.so.2 (0xb75b5000) *** libSM.so.6 => /usr/lib/libSM.so.6 (0xb75ad000) *** libICE.so.6 => /usr/lib/libICE.so.6 (0xb7592000) *** libi18nisolang1gcc3.so => /usr/lib/openoffice.org/basis3.0/program/libi18nisolang1gcc3.so (0xb758d000) *** libbasegfxli.so => /usr/lib/openoffice.org/basis3.0/program/libbasegfxli.so (0xb753c000) *** libicuuc.so.40 => /usr/lib/libicuuc.so.40 (0xb73fe000) *** libicule.so.40 => /usr/lib/libicule.so.40 (0xb73c8000) *** libjvmaccessgcc3.so.3 => /usr/lib/openoffice.org/basis3.0/program/../ure-link/lib/libjvmaccessgcc3.so.3 (0xb73c0000) *** libuno_salhelpergcc3.so.3 => /usr/lib/openoffice.org/basis3.0/program/../ure-link/lib/libuno_salhelpergcc3.so.3 (0xb73bc000) *** libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7389000) *** libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0xb7386000) *** libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb736a000) *** libXau.so.6 => /usr/lib/libXau.so.6 (0xb7367000) *** libuuid.so.1 => /lib/libuuid.so.1 (0xb7363000) *** libicudata.so.40 => /usr/lib/libicudata.so.40 (0xb661d000) *** libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6617000) ...end sample ldd details ... * -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
| All times are GMT. The time now is 07:38 PM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.