From: Mark K. <mar...@gm...> - 2005-07-13 18:58:15
|
Hi, What's the trick to running Muse when Jack is running with realtime enabled? Everytime I try, whether as a user with realtime-lsm or anytime as root, I just get this message: flash ~ $ museseq /usr/kde/3.4/bin/konqueror starting with default template WatchDog: fatal error, realtime task timeout (0,0-3) - stopping all services flash ~ $ Other Jack apps run fine. I'm currently running alsaplayer with Jack at 64/2 and no xruns, but cannot figure out how to get beyond this issue. I took a quick look through the Muse Wiki but didn't spot anything. Hopefully I'm not missing something obvious. I don't see any sort of -R options in Muse's command line help. Thanks, Mark |
From: Robert J. <rj...@sp...> - 2005-07-13 19:12:34
|
Hi Mark, On Wednesday 13 Jul 2005 20:58, Mark Knecht wrote: > Hi, > What's the trick to running Muse when Jack is running with realtime > enabled? Everytime I try, whether as a user with realtime-lsm or > anytime as root, I just get this message: > > flash ~ $ museseq > /usr/kde/3.4/bin/konqueror > starting with default template > WatchDog: fatal error, realtime task timeout > (0,0-3) - stopping all services > > flash ~ $ > > Other Jack apps run fine. I'm currently running alsaplayer with > Jack at 64/2 and no xruns, but cannot figure out how to get beyond > this issue. > > I took a quick look through the Muse Wiki but didn't spot anything. > Hopefully I'm not missing something obvious. I don't see any sort of > -R options in Muse's command line help. Correct, MusE asks jack if it should run with realtime priority. Please try the latest release (0.7.2pre2) , there was a bug fixed with the watchdog handler that triggered a similar behaviour, I think gentoo was hit quite hard on this one (as I think you are using gentoo). Though I might add that your experiences using MusE at 64/2 may or may not be the best, the load-song trouble, that is apparent with small period sizes, has not really been resolved. Someone mentioned better success with a (very) recent kernel, which may indicate it is a kernel problem. Regards, Robert > > Thanks, > Mark > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest > in dual core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit > http://www.hp.com/go/dualwebinar > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user -- http://spamatica.se/musicsite/ |
From: Mark K. <mar...@gm...> - 2005-07-13 20:27:23
|
On 7/13/05, Robert Jonsson <rj...@sp...> wrote: > Hi Mark, >=20 <SNIP> > > Other Jack apps run fine. I'm currently running alsaplayer with > > Jack at 64/2 and no xruns, but cannot figure out how to get beyond > > this issue. > > > > I took a quick look through the Muse Wiki but didn't spot anything. > > Hopefully I'm not missing something obvious. I don't see any sort of > > -R options in Muse's command line help. >=20 > Correct, MusE asks jack if it should run with realtime priority. >=20 > Please try the latest release (0.7.2pre2) , there was a bug fixed with th= e > watchdog handler that triggered a similar behaviour, I think gentoo was h= it > quite hard on this one (as I think you are using gentoo). Humm...no ebuild for 0.7.2xxx et. I'll have to build from CVS. >=20 > Though I might add that your experiences using MusE at 64/2 may or may no= t be > the best, the load-song trouble, that is apparent with small period sizes= , > has not really been resolved. Sorry for the confusion. I don't care about latency too much. I was only pointing out that the kernel & machine are usable down past 64/2. I can actually run many applications on this machine, at least under light load, with Jack settings of 16/2, but most of the time I run 256/2 or 512/2. Note that these numbers are just a straight Gentoo kernel - No additional patches, such as -mm, etc., are necessary. > Someone mentioned better success with a (very) recent kernel, which may > indicate it is a kernel problem. This is at least a pretty recent kernel - 2.6.12-gentoo-r3, but not bleeding edge 2..13 stuff. Off to get some code. Cheers, Mark |
From: Mark K. <mar...@gm...> - 2005-07-13 21:03:05
|
On 7/13/05, Mark Knecht <mar...@gm...> wrote: >=20 > Off to get some code. >=20 > Cheers, > Mark >=20 Hi - mostly good news - but one question at the end a few comments about the build: OK, building 0.7.2_pre2: During the ./autogen.sh step I see this: flash muse-0.7.2pre2 $ ./autogen.sh automake version: head: `-1' option is obsolete; use `-n 1' since this will be removed in the future 1.7.9 (ok) autoconf version: head: `-1' option is obsolete; use `-n 1' since this will be removed in the future 2.59 (ok) libtool version: head: `-1' option is obsolete; use `-n 1' since this will be removed in the future 1.5.16 (ok) For configure I used this: flash muse-0.7.2pre2 $ ./configure --enable-rtcap --prefix=3D/usr Was the --enable-rtcap appropriate??? I got this result: MusE configured using rtcap: yes LADCCA support: no setuid root install: no setuid root build: no fluidsynth softsynth: yes VST/win support: no jade: openjade doxygen: /usr/bin/doxygen graphviz: /usr/bin/dot perl: /usr/bin/perl treeviews in doxygen html output: yes C++ compiler: g++ optimizing: no debug: no optimise for arch: none installation prefix: /usr flash muse-0.7.2pre2 $ When I run Muse it comes up fine but I see this message: flash ~ $ muse mjsucaps: capsetp: Operation not permitted /usr/kde/3.4/bin/konqueror starting with default template so maybe I should not have used --enable-rtcap? Anyway, the best news so far is that Muse is up. No testing yet but soon. thanks, Mark |
From: Robert J. <rj...@sp...> - 2005-07-13 21:15:03
|
Hi, On Wednesday 13 Jul 2005 23:02, Mark Knecht wrote: > On 7/13/05, Mark Knecht <mar...@gm...> wrote: > > Off to get some code. > > > > Cheers, > > Mark > > Hi - mostly good news - but one question at the end a few comments > about the build: > > OK, building 0.7.2_pre2: > > During the ./autogen.sh step I see this: > > flash muse-0.7.2pre2 $ ./autogen.sh > automake version: head: `-1' option is obsolete; use `-n 1' since this > will be removed in the future > 1.7.9 (ok) > autoconf version: head: `-1' option is obsolete; use `-n 1' since this > will be removed in the future > 2.59 (ok) > libtool version: head: `-1' option is obsolete; use `-n 1' since this > will be removed in the future > 1.5.16 (ok) Ok, that's a new one to me... not that I know alot about automake. Thanks for the info. > > For configure I used this: > > flash muse-0.7.2pre2 $ ./configure --enable-rtcap --prefix=/usr > > Was the --enable-rtcap appropriate??? I got this result: > > MusE configured > > using rtcap: yes > LADCCA support: no > setuid root install: no > setuid root build: no > fluidsynth softsynth: yes > VST/win support: no > > jade: openjade > doxygen: /usr/bin/doxygen > graphviz: /usr/bin/dot > perl: /usr/bin/perl > treeviews in doxygen > html output: yes > > C++ compiler: g++ > optimizing: no > debug: no > optimise for arch: none > > installation prefix: /usr > > > flash muse-0.7.2pre2 $ > > When I run Muse it comes up fine but I see this message: > > flash ~ $ muse > mjsucaps: capsetp: Operation not permitted > /usr/kde/3.4/bin/konqueror > starting with default template > > so maybe I should not have used --enable-rtcap? Correct. The rtcap support is for the (now old) givertcap that Tommi Ilmonen provided. Regards, Robert > > Anyway, the best news so far is that Muse is up. No testing yet but soon. > > thanks, > Mark -- http://spamatica.se/musicsite/ |
From: Robert J. <rj...@sp...> - 2005-07-13 21:18:07
|
Just a short addition. > > flash ~ $ muse > > mjsucaps: capsetp: Operation not permitted > > /usr/kde/3.4/bin/konqueror > > starting with default template > > > > so maybe I should not have used --enable-rtcap? > > Correct. > The rtcap support is for the (now old) givertcap that Tommi Ilmonen > provided. To answer the obvious question, I don't think it hurts anything. You get an error message in the console, don't think anything else will happen. > > Regards, > Robert > > > Anyway, the best news so far is that Muse is up. No testing yet but soon. Great! /Robert > > > > thanks, > > Mark -- http://spamatica.se/musicsite/ |
From: Mark K. <mar...@gm...> - 2005-07-13 21:53:19
|
On 7/13/05, Robert Jonsson <rj...@sp...> wrote: > Just a short addition. >=20 > > > flash ~ $ muse > > > mjsucaps: capsetp: Operation not permitted > > > /usr/kde/3.4/bin/konqueror > > > starting with default template > > > > > > so maybe I should not have used --enable-rtcap? > > > > Correct. > > The rtcap support is for the (now old) givertcap that Tommi Ilmonen > > provided. >=20 > To answer the obvious question, I don't think it hurts anything. You get = an > error message in the console, don't think anything else will happen. Well, by the time I noticed this message I had already kicked off a new build. No harm. The new version comes up fine with Jack running realtime at 256/2. Everything looks fie so far. >=20 > > > > Regards, > > Robert > > > > > Anyway, the best news so far is that Muse is up. No testing yet but s= oon. >=20 > Great! >=20 > /Robert I see the new 'Import Part' feature. I'll have to give that a try. Cheers, Mark |