Re: [Openvortex-dev] New CVS update to come SPDIF

[Erik Gustavsson]

On Sat, 2003-09-20 at 02:20, Manuel Jander wrote:
> Hi Erik,
> 
> On Fri, 2003-09-19 at 19:16, Erik Gustavsson wrote:
> > Doesn't work that well for me. Using the normal adb device doesn't
> > generate any audio on the spdif (I assume this is by design, although
> > not how I'd like it). Using the spdif device caused this:
> > 
> 
> Of course you wont get SPDIF output using that device. The adb device is
> for AC97 codec output. Maybe we could rename it.
> 

Well, personally I'd like to have the SPDIF output behave like in the
windows drivers when using the adb device. That is, the SPDIF output is
pretty much a copy of the AC97 codec output, at a fixed sample rate.
This is perfect for general use, when the SPDIF output is simply used
instead of the analog output.

> The SPDIF output device uses a SampleRate converter to change any
> samplerate into the SPDIF output rate. I'm working on a mixer control to
> select either 32000, 44100 or 48000Hz for SPDIF output.
> 

And if possible, when opening the special "spdif" device I'd like the
sample rate of the SPDIF port to be changed to match the audio and the
data to be sent straight from the application to the SPDIF output
without any resampling or mixing. The SPDIF port should be switched off
if muted and when the device is closed. This would be perfect for
transfering MP3 to minidisc (with trackmarks), sending AC3 audio to an
external decoder, or just getting bit-perfect audio from the computer to
an external DAC.

I was thinking of trying to implement this behavior myself, but I don't
even know if the hardware can do it.

> > Vortex: hardware init.... <6>done.
> > SDAC detected divide error: 0000
> > CPU:    0
> > EIP:    0010:[<e1afebf4>]    Tainted: PF
> > EFLAGS: 00010046
> > eax: 56220000   ebx: 00000000   ecx: 56220000   edx: 00000000
> > esi: cae98000   edi: cae98074   ebp: 00000001   esp: d0ea5ecc
> > ds: 0018   es: 0018   ss: 0018
> > Process xmms (pid: 5620, stackpage=d0ea5000)
> > Stack: dd35d580 cae98000 0000ac44 00000001 e1aff961 cae98000 00000001
> > 0000ac44 
> >        00000001 cae98000 dd35d580 00000000 dd35d580 e1af95d0 e1aefa2c
> > dd35d580 
> >        00000000 e1aef502 dd35d580 00000000 e1af95d0 00000000 dd35d580
> > e1af1a30 
> > Call Trace:    [<e1aff961>] [<e1af95d0>] [<e1aefa2c>] [<e1aef502>]
> > [<e1af95d0>]
> >   [<e1af1a30>] [<e1aef57f>] [<e1af95d0>] [<e1aefa91>] [<e1af95d0>]
> > [<e1af14d8>]
> >   [<c018d8b9>] [<e1af1a30>] [<c01d1140>] [<c01876d7>]
> > 
> > Code: f7 f3 8d 70 01 d1 ee 31 db 8d 76 00 b8 01 00 00 00 88 d9 d3 
> > 
> > 
> > On Sat, 2003-09-20 at 00:25, Manuel Jander wrote:
> 
> Well, this is just what i wanted to know about. I'll try to find out why
> this happened. Would be nice to know what card you are using. Looks like
> a AU8830 Quad ?
> 

MX300 with a DIY SPDIF adapter, so yes...

/cyr