All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000572]: spdif hw entry fails to work in multi
Date: Fri,  8 Oct 2004 12:13:29 +0200 (CEST)	[thread overview]
Message-ID: <20041008101329.BF13649052@server.perex-int.cz> (raw)


A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000572
======================================================================
Reported By:                ramendik
Assigned To:                
======================================================================
Project:                    ALSA - driver
Bug ID:                     572
Category:                   PCI - intel8x0
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               RH-based
Kernel Version:             2.6.8.1, with alsa 1.0.7rc1 plus patches from bug 0000505
======================================================================
Date Submitted:             10-08-2004 02:27 CEST
Last Modified:              10-08-2004 12:13 CEST
======================================================================
Summary:                    spdif hw entry fails to work in multi
Description: 
After bug 0000505 was fixed, hw:0,0 only plays to analog devices, and
hw:0,4 to spdif. As one needs output in both, I tried to use .asoundrc ,
and therefore needed to use the "multi" pcm type in order to unite these
two (and then route). This is what I put in .asoundrc

pcm.whole {
    type multi
    slaves.a.pcm "hw:0,0"
    slaves.a.channels 2
    slaves.b.pcm "hw:0,4"
    slaves.b.channels 2
    bindings.0.slave a
    bindings.0.channel 0
    bindings.1.slave a
    bindings.1.channel 1
    bindings.2.slave b
    bindings.2.channel 0
    bindings.3.slave b
    bindings.3.channel 1
}

pcm.rt {
    type route
    slave.pcm "whole"
    ttable.0.0 1
    ttable.1.1 1
    ttable.0.2 1
    ttable.1.3 1
}

The ttable may be wrong - I could not find a sane description anywhere -
but I tried many variants, and besides, playing to "whole" bypasses this.

So here's what I get when playing to "rt" OR to "whole" via alsaplayer :

$ alsaplayer -d whole test.wav 
error on set_channels (2)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 64
CHANNELS: 4
RATE: 44100
PERIOD_TIME: (181 371520)
PERIOD_SIZE: [8 16384]
PERIOD_BYTES: [64 131072]
PERIODS: [1 1024]
BUFFER_TIME: (181 371520)
BUFFER_SIZE: [8 16384]
BUFFER_BYTES: [64 131072]
TICK_TIME: 1000
error on set_channels (2)
Unavailable hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 64
CHANNELS: 4
RATE: 44100
PERIOD_TIME: (181 371520)
PERIOD_SIZE: [8 16384]
PERIOD_BYTES: [64 131072]
PERIODS: [1 1024]
BUFFER_TIME: (181 371520)
BUFFER_SIZE: [8 16384]
BUFFER_BYTES: [64 131072]
TICK_TIME: 1000
failed to configure output device...trying OSS

then alsaplayer hangs until interrupted.

When I comment out everything related to slave b, "whole" seems to work
(without spdif output, of course). So this seems like a bug in the spdif
device.
======================================================================

----------------------------------------------------------------------
 tiwai - 10-08-2004 12:13 CEST 
----------------------------------------------------------------------
Use this:

pcm.rt {
    type route
    slave.pcm whole
    slave.channels 4
    ttable.0.0 1
    ttable.1.1 1
    ttable.0.2 1
    ttable.1.3 1
}

and run with -d rt .

Bug History
Date Modified  Username       Field                    Change              
======================================================================
10-08-04 02:27 ramendik       New Bug                                      
10-08-04 02:27 ramendik       Distribution              => RH-based        
10-08-04 02:27 ramendik       Kernel Version            => 2.6.8.1, with alsa 1.0.7rc1 plus patches from bug 0000505
10-08-04 02:31 ramendik       Bug Monitored: ramendik                      
10-08-04 12:13 tiwai          Bugnote Added: 0002045                       
======================================================================


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

             reply	other threads:[~2004-10-08 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 10:13 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-08  8:38 [ALSA - driver 0000572]: spdif hw entry fails to work in multi bugtrack
2005-04-09 14:19 bugtrack
2004-10-14 10:37 bugtrack
2004-10-13 15:31 bugtrack
2004-10-13  8:49 bugtrack
2004-10-13  4:43 bugtrack
2004-10-11 13:39 bugtrack
2004-10-08 10:42 bugtrack
2004-10-08 10:29 bugtrack
2004-10-08  0:27 bugtrack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041008101329.BF13649052@server.perex-int.cz \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.