> 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. >
Resp. It seems to be the kind of bug I get most often. > 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.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
