#110 Can't use Muse if no Jack - alsa_pcm is found.

closed
nobody
None
5
2005-08-31
2005-07-15
Anonymous
No

I have a m-audio Firewire audio card that I'm using. In jack it
appears as firewire_pcm instead of my internal intel8x0 which
appears as alsa_pcm.

If I just run my firewire card I have no alsa_pcm just
firewire_pcm
and muse refuses to start. Saying that it can't find alsa_pcm.

This setup works fine with for instance, hydrogen, ardour,
rosegarden.
Those programs start up and let me connect my firewire_pcm
and i.e hydrogen_pcm manually.

I would really like for muse to atleast start up so I can patch
jack manually.

Thanks

Discussion

  • Robert Jonsson
    Robert Jonsson
    2005-07-15

    Logged In: YES
    user_id=81832

    Hi,

    Interesting that you are trying a firewire card. Freebob drivers I
    presume.
    I think we need some more info about your problem though.
    That alsa_pcm is not found should not affect if MusE starts, this is only
    a warning message that the default template could not map the
    outputs.

    Which version of MusE is it?
    Does it work ok if you run jack on the intel8x0?
    Any other clues about differences, no other output from MusE? Does
    the GUI show at all?

    A good idea is to subscribe to our mailinglist (lmuse-user, see above).

     
  • Robert Jonsson
    Robert Jonsson
    2005-08-16

    • status: open --> pending
     
  • Robert Jonsson
    Robert Jonsson
    2005-08-16

    Logged In: YES
    user_id=81832

    I have finally gotten around to test this with my own firewire device
    (EDIROL FA-101) and it seems to work just fine.
    The device is differently named so the default template does not make the
    correct connection but that is easily added later.

    Setting bugreport to pending as it probably is not muse related.

     
  • Logged In: NO

    Hi,

    Yes I use the freebob drivers. I was a bit hasty when I
    submitted the bug report. It's not related to not finding
    alsa_pcm.

    When I run muse in a console I see this:
    ---------------------------8<---------------------------
    [13:03:41] xxx@xxx ~ $ muse
    /opt/kde3/bin/konqueror
    no locale <muse_en_US.UTF-8>/</usr/share/muse/locale>
    starting with default template
    name2route: <alsa_pcm:playback_1> not found
    name2route: <alsa_pcm:playback_2> not found
    WatchDog: fatal error, realtime task timeout
    (0,0-3) - stopping all services
    watchdog exit
    ---------------------------8<---------------------------
    So I guess it has something to do with Realtime? If I start with
    -d it loads the gui.

    I'm running Suse 9.3 with a RT patched kernel.

    Thanks.

     
  • Logged In: NO

    Forgot to mention that the muse version is 0.7.1

    Thanks.

     
  • Daniel Kobras
    Daniel Kobras
    2005-08-30

    Logged In: YES
    user_id=7832

    This looks similar to the problem a user reported for the
    0.7.2pre2 Debian package. He's using jack and a realtime-lsm
    enabled kernel. The watchdog triggers right after startup
    because no timer ticks seem to get delivered. See
    http://bugs.debian.org/325064 for the full story. I cannot
    reproduce this problem and would appreciate any input. Maybe
    both reports have a common cause?

     
  • Robert Jonsson
    Robert Jonsson
    2005-08-30

    Logged In: YES
    user_id=81832

    Hi,

    After 0.7.1 Werner fixed a bug with regards to the watchdog that
    might be the problem here. Please try the latest prerelease.
    Also the alsa-timer implementation in 0.7.1 was less than stellar it
    seems, it has been reworked by Jonathan Woithe and seems to
    work much better (no hard proof though), this is however still only
    available in cvs, if anyone wants to try it check out the REL07
    branch.

     
    • status: pending --> closed
     
  • Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).