All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Sjostrand <gorm@cucumelo.org>
To: Gregoire Favre <greg@ulima.unil.ch>
Cc: "Dr. Werner Fink" <werner@suse.de>,
	Peter Heatwole <peter599@gotnet.net>,
	alsa-devel@lists.sourceforge.net
Subject: Re: SPDIF and cs46xx ?
Date: Fri, 04 Apr 2003 20:01:37 +0200	[thread overview]
Message-ID: <3E8DC881.2070401@cucumelo.org> (raw)
In-Reply-To: 20030404114623.GB9836@ulima.unil.ch

>
>
>sorry to ask again :-(
>I have just installed latest alsa CVS of drivers,lib and utils and still
>get a:
>
>pr  4 13:37:43 localhost vdr[20035]: S/P-DIF: Period size not available: Invalid argument
>Apr  4 13:37:43 localhost vdr[20035]: S/P-DIF: unable to establish BitStreamOut for none audio PCM 
>Apr  4 13:37:43 localhost vdr[20035]: REPLAY: can't open spdif interface
>
>Should I change anything anywhere?
>Or buy a card with cmipci? (Well I like the Digifire 7.1 I have now,
>which has also an integrated Firewire...).
>  
>
I would like to get to the bottom of this problem.
Let's try figure out exactly which lines of code produces thoose 
messages: "S/P-DIF: Period size not available: Invalid argument" and 
"S/P-DIF: unable to establish BitStreamOut for none audio PCM"

/Benny



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

  reply	other threads:[~2003-04-04 18:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-16 21:31 SPDIF and cs46xx ? Peter Heatwole
2003-03-16 23:23 ` Benny Sjostrand
2003-03-29 14:20   ` Gregoire Favre
2003-03-30  1:11     ` Benny Sjostrand
2003-03-30 14:46       ` Gregoire Favre
2003-03-30 19:35         ` Benny Sjostrand
2003-03-30 18:42           ` Gregoire Favre
     [not found]           ` <20030331115057.GB3187@wotan.suse.de>
2003-03-31 13:58             ` Benny Sjostrand
     [not found]         ` <20030331114752.GA3187@wotan.suse.de>
2003-04-04 11:46           ` Gregoire Favre
2003-04-04 18:01             ` Benny Sjostrand [this message]
2003-04-04 17:25               ` Gregoire Favre
2003-04-05 18:46                 ` Benny Sjostrand
2003-04-05 18:29                   ` Gregoire Favre
2003-04-05 21:48                     ` Benny Sjostrand
     [not found]             ` <20030407091749.GA7661@wotan.suse.de>
2003-04-07 16:45               ` Gregoire Favre
  -- strict thread matches above, loose matches on Subject: below --
2003-03-16 23:11 Peter Heatwole
2003-03-16 22:56 Peter Heatwole
2003-03-17  0:10 ` Benny Sjostrand
     [not found] <20030313132536.GB11388@ulima.unil.ch>
2003-03-14 10:55 ` Ronny V. Vindenes
2003-03-14 21:29   ` Benny Sjostrand
2003-03-14 22:04     ` Christian Esken
2003-03-08 14:41 Gregoire Favre
2003-03-08 17:28 ` Benny Sjostrand
2003-03-08 17:52   ` Gregoire Favre
2003-03-10 14:42     ` Takashi Iwai
2003-03-10 14:46       ` Gregoire Favre
2003-03-10 14:52         ` Takashi Iwai
2003-03-10 15:34           ` Gregoire Favre
2003-03-10 21:15           ` Gregoire Favre
2003-03-11 16:54             ` Takashi Iwai
2003-03-11 23:35               ` Gregoire Favre
2003-03-12 11:08                 ` Ronny V. Vindenes
2003-03-12 11:50                   ` Gregoire Favre

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=3E8DC881.2070401@cucumelo.org \
    --to=gorm@cucumelo.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=greg@ulima.unil.ch \
    --cc=peter599@gotnet.net \
    --cc=werner@suse.de \
    /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.