Skip to contentSkip to conversation

s/pdif controls

DISCUSSION Paul Davis 4 participants 6 messages Mar 8, 2003 – Mar 11, 2003

lore
Share & tools
lore

Paul Davis

author
#0 lore raw

how are users supposed to set various s/pdif bits?

the existing control formats involve massive bitfields that are totally impenetrenable to almost everyone.

what is the strategy here? if someone wants to turn the pro/consumer bit on/off, what are they supposed to do?

-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com

#1 lore raw

At Sat, 8 Mar 2003 10:00:20 -0500,

Quoted 8 lines · Paul Davis

how are users supposed to set various s/pdif bits?

the existing control formats involve massive bitfields that are totally impenetrenable to almost everyone.

what is the strategy here? if someone wants to turn the pro/consumer bit on/off, what are they supposed to do?

a good question - there has not been much discussions there. the iec958 status bits are passed usually through AESx arguments of iec958 (aka spdif) pcm interface. and i think it's a good way, because it's general and applicable to different cards in a uniform way.

so far, almost only AC3-passthru was the case which needs to change such a configuration, and the status bits are likely known for such. so, there was no big complans about this. but, surely the way above is for end-users.

well, we'll need a kind of iec958-status-bit-composer, which is implemented on envy24control. but i believe it should be a user-land solution, anyway.

Takashi

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

author
#2 lore raw
Quoted 5 lines
Quoted 5 lines

how are users supposed to set various s/pdif bits?

the existing control formats involve massive bitfields that are totally impenetrenable to almost everyone.

Quoted 8 lines
Quoted 2 lines

what is the strategy here? if someone wants to turn the pro/consumer bit on/off, what are they supposed to do?

a good question - there has not been much discussions there. the iec958 status bits are passed usually through AESx arguments of iec958 (aka spdif) pcm interface. and i think it's a good way, because it's general and applicable to different cards in a uniform way.

true, but its totally impenetrable. i wrote a few drivers and even i have absolutely no idea what those bitfields mean.

Quoted 3 lines

well, we'll need a kind of iec958-status-bit-composer, which is implemented on envy24control. but i believe it should be a user-land solution, anyway.

i agree. but why are the status bit fields so long? is this following IEC958 specs?

-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

#3 lore raw
Quoted 2 lines · Paul Davis

i agree. but why are the status bit fields so long? is this following IEC958 specs?

Yes. They are large.

The only full description of the status bitfields I have ever found is in the AD1892 datasheet. I have archived a copy here:
http://bani.anime.net/bookmarkz/AD1892_0.pdf

-Dan

Signature · 9 lines
[-] Omae no subete no kichi wa ore no mono da. [-]



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
#5 lore raw
In reply to Benny Sjostrand
Quoted 3 lines · Benny Sjostrand

Another spec. from Cirrus that explains all the IEC958 bitfields, I guess this one is well known. I got a copy on
http://www.cucumelo.org/~gorm/an22.pdf

It doesn't explain all the subcodes though...

-Dan

Signature · 9 lines
[-] Omae no subete no kichi wa ore no mono da. [-]



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
#4 lore raw
In reply to Dan Hollis
Quoted 7 lines
Quoted 6 lines

i agree. but why are the status bit fields so long? is this following IEC958 specs?

Quoted 7 lines

Yes. They are large.

The only full description of the status bitfields I have ever found is in the AD1892 datasheet. I have archived a copy here:
http://bani.anime.net/bookmarkz/AD1892_0.pdf

-Dan

Another spec. from Cirrus that explains all the IEC958 bitfields, I guess this one is well known. I got a copy on http://www.cucumelo.org/~gorm/an22.pdf

/Benny

-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en