AlsaProject - User contributions [en]

ALSA firewire stack (since Linux 2.6.39)

2021-12-02T10:49:44Z

Mocchi: not maintained anymore

ALSA firewire stack

2021-12-02T10:45:51Z

Mocchi: unmaintained anymore.

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-05T13:50:27Z

Mocchi: /* Presentation timestamp in IEC 61883-6 */

ALSA firewire stack

2016-05-05T13:50:00Z

Mocchi: /* Current issues */

ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus.

== Already merged ==

<dl>
<dt>snd-firewire-lib</dt>
<dd>A module for helper functions of isochronous packet streaming for IEC 61883-1/6 and AM824 data block processing. (since Linux 2.6.39)</dd>
<dt>snd-isight</dt>
<dd>A driver for audio feature of iSight produced by Apple Inc. (since Linux 3.0)</dd>
<dt>snd-dice</dt>
<dd>A driver for models with DiceII/TCD2210(Dice Mini)/TCD2220(Dice Jr.)/TCD3072-CH ASICs produced by TC Applied Technologies, Inc. (since Linux 3.13)</dd>
<dt>snd-fireworks</dt>
<dd>A driver for models with Fireworks board module produced by Echo Audio Corp. (since Linux 3.16)</dd>
<dt>snd-bebob</dt>
<dd>A driver for models with DM1000/DM1100/DM1500 ASICs and BeBoB firmware produced by ArchWave AG (formerly known as BridgeCo. AG) (since Linux 3.16)</dd>
<dt>snd-oxfw</dt>
<dd>A driver for models with FW970/971 ASICs produced by Oxford Semiconductor (acquired by PLC Technology). (since Linux 3.19)</dd>
<dt>snd-firewire-digi00x</dt>
<dd>A driver for Digi00x series produced by Avid Technology Inc. as a brand of Digidesign. (since Linux 4.4)</dd>
<dt>snd-firewire-tascam</dt>
<dd>A driver for FireWire series produced by TEAC Corp. as a brand of TASCAM. (since Linux 4.4)</dd>
</dl>

== Under development ==

<dl>
<dt>snd-firewire-transceiver<dt>
<dd>A driver to communicate on IEEE 1394 bus between several Linux systems.</dd>
<dt>snd-firewire-motu<dt>
<dd>A driver for models produced by Mark of the unicorn.</dd>
<dt>snd-fireface<dt>
<dd>A driver for Fireface family produced by RME.</dd>
</dl>

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-04T02:01:25Z

Mocchi:

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document (2009013) in [http://1394ta.org/specifications/ a specification page of 1394ta.org] as of 2016/05/03.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:51:59Z

Mocchi: /* Implementation of ALSA firewire stack */

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document (2009013) in [http://1394ta.org/specifications/ a specification page of 1394ta.org] as of 2016/05/03.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000. The
presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of
IEC 61883-6, thus duration of total data blocks in a packet is decisive in this
formula.
1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks) at 44.1/88.2/176.4kHz.
1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks) at 48.0/96.0/192.0kHz.
If presentation timestamp of a prepared packet has over 1 cycle gap to the one of
a previous transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle. Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.

Examples:

<pre>
sec cycle CIP1 CIP2 db tstamp tstamp gap
cycle tick
05 4998 01050008 9002a600 8 5002 1536 -
05 4999 01050010 9002ba00 8 5003 2560 4096
05 5000 01050018 9002ffff 0
05 5001 01050018 9002d200 8 5005 512 4096
05 5002 01050020 9002e600 8 5006 1536 4096
05 5003 01050028 9002fa00 8 5007 2560 4096
05 5004 01050030 9002ffff 0
05 5005 01050030 90021200 8 5009 512 4096
05 5006 01050038 90022600 8 5010 1536 4096
05 5007 01050040 90023a00 8 5011 2560 4096
05 5008 01050048 9002ffff 0
05 5009 01050048 90025200 8 5013 512 4096
05 5010 01050050 90026600 8 5014 1536 4096
05 5011 01050058 90027a00 8 5015 2560 4096
</pre>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.

# Calculated duration for total data blocks in a packet is sometimes different from the value I described. Approximately, plus/minus 1-2 ticks.
# Timing to transmit NODATA/NOINFO packets is independent of gap between presentation timestamps for consecutive two packets.
# The sequence of SYT value in rx/tx packet has no relationships. ALSA dice driver since Linux 3.19 till 4.5 has reused parameters of incoming packets for outgoing packets. However, the outgoing sequence is not expected by the models and causes periodical noises.

Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to [http://mailman.alsa-project.org/pipermail/alsa-devel/2016-April/106950.html alsa-devel].

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:50:44Z

Mocchi: /* Dice quirks */

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document (2009013) in [http://1394ta.org/specifications/ a specification page of 1394ta.org] as of 2016/05/03.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000. The
presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of
IEC 61883-6, thus duration of total data blocks in a packet is decisive in this
formula.
1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks) at 44.1/88.2/176.4kHz.
1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks) at 48.0/96.0/192.0kHz.
If presentation timestamp of a prepared packet has over 1 cycle gap to the one of
a previous transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle. Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.

# Calculated duration for total data blocks in a packet is sometimes different from the value I described. Approximately, plus/minus 1-2 ticks.
# Timing to transmit NODATA/NOINFO packets is independent of gap between presentation timestamps for consecutive two packets.
# The sequence of SYT value in rx/tx packet has no relationships. ALSA dice driver since Linux 3.19 till 4.5 has reused parameters of incoming packets for outgoing packets. However, the outgoing sequence is not expected by the models and causes periodical noises.

Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to [http://mailman.alsa-project.org/pipermail/alsa-devel/2016-April/106950.html alsa-devel].

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:32:58Z

Mocchi:

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document (2009013) in [http://1394ta.org/specifications/ a specification page of 1394ta.org] as of 2016/05/03.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000. The
presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of
IEC 61883-6, thus duration of total data blocks in a packet is decisive in this
formula.
1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks) at 44.1/88.2/176.4kHz.
1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks) at 48.0/96.0/192.0kHz.
If presentation timestamp of a prepared packet has over 1 cycle gap to the one of
a previous transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle. Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
<ul>
<li>Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.</li>
<li>Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.</li>
<li>The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.</li>
</ul>
Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to [http://mailman.alsa-project.org/pipermail/alsa-devel/2016-April/106950.html alsa-devel].

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:31:43Z

Mocchi: /* Dice quirks */

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document (2009013) in [http://1394ta.org/specifications/ a specification page of 1394ta.org.]

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000. The
presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of
IEC 61883-6, thus duration of total data blocks in a packet is decisive in this
formula.
1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks) at 44.1/88.2/176.4kHz.
1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks) at 48.0/96.0/192.0kHz.
If presentation timestamp of a prepared packet has over 1 cycle gap to the one of
a previous transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle. Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
<ul>
<li>Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.</li>
<li>Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.</li>
<li>The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.</li>
</ul>
Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to alsa-devel.

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:30:15Z

Mocchi: /* Presentation timestamp in IEC 61883-6 */

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document (2009013) in [http://1394ta.org/specifications/ a specification page of 1394ta.org.]

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000. The
presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of
IEC 61883-6, thus duration of total data blocks in a packet is decisive in this
formula.
1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks) at 44.1/88.2/176.4kHz.
1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks) at 48.0/96.0/192.0kHz.
If presentation timestamp of a prepared packet has over 1 cycle gap to the one of
a previous transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle. Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.
Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.
The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.
Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to alsa-devel.

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:26:24Z

Mocchi: /* Presentation timestamp in IEC 61883-6 */

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document in 1394ta.org.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000. The
presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of
IEC 61883-6, thus duration of total data blocks in a packet is decisive in this
formula.
1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks) at 44.1/88.2/176.4kHz.
1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks) at 48.0/96.0/192.0kHz.
If presentation timestamp of a prepared packet has over 1 cycle gap to the one of
a previous transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle. Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.
Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.
The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.
Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to alsa-devel.

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:23:11Z

Mocchi: /* Background */

== Presentation timestamp in IEC 61883-6 ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document in 1394ta.org.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000.
The presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of IEC 61883-6,
thus duration of total data blocks in a packet is decisive.
<dl>
<dt>At 44.1/88.2/176.4kHz</dt>
<dd>1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks)</dd>
<dt>At 48.0/96.0/192.0kHz</dt>
<dd>1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks)</dd>
</dl>
If presentation timestamp of a prepared packet has over 1 cycle gap to
a transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle.
Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.
Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.
The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.
Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to alsa-devel.

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:20:03Z

Mocchi:

== Background ==
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document in 1394ta.org.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000.
The presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of IEC 61883-6,
thus duration of total data blocks in a packet is decisive.
<dl>
<dt>At 44.1/88.2/176.4kHz</dt>
<dd>1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks)</dd>
<dt>At 48.0/96.0/192.0kHz</dt>
<dd>1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks)</dd>
</dl>
If presentation timestamp of a prepared packet has over 1 cycle gap to
a transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle.
Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

== Implementation of ALSA firewire stack ==
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

== Dice quirks ==
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.
Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.
The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.
Examples:

== Solution ==
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to alsa-devel.

ALSA firewire stack

2016-05-03T13:19:22Z

Mocchi:

Dice packet sequence quirk and ALSA firewire stack in Linux 4.6

2016-05-03T13:13:42Z

Mocchi: Created page with "<h2>Background</h2> IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394 bus. This specification is originally documented as 'Audio and Music Data T..."

<h2>Background</h2>
IEC 61883-6 is a specification to transfer Audio and Music data on IEEE 1394
bus. This specification is originally documented as 'Audio and Music Data
Transmission Protocol' by 1394 Trading Association in 1997. You can see
updated document in 1394ta.org.

IEC 61883-6 defines 'presentation timestamp'. This timestamp represents
playback timing of PCM frames transmitted in isochronous packets. The
transmitter can indicate the timing to receivers in a shape of lower 16 bits
of CYCLE_TIMER format in IEEE 1394. The 16 bit value is in SYT field of CIP
header in IEC 61883-1. The receivers can calculate the presentation timestamp
with the value of SYT field in received CIP, compensated by timestamp in
'cycle start' packet broadcasted by isochronous cycle master each isochronous
cycle.

Here, I describe items about blocking transmission of IEC 61883-6:2000.
The presentation timestamp in a packet corresponds to first data block in the packet.
The number of data blocks in a packet is decided according to SYT_INTERVAL of IEC 61883-6,
thus duration of total data blocks in a packet is decisive.
<dl>
<dt>At 44.1/88.2/176.4kHz</dt>
<dd>1/44100 * 8 (sec) = 1/44100 * 8 * 8000 * 3072 (ticks)</dd>
<dt>At 48.0/96.0/192.0kHz</dt>
<dd>1/48000 * 8 (sec) = 1/48000 * 8 * 8000 * 3072 (ticks)</dd>
</dl>
If presentation timestamp of a prepared packet has over 1 cycle gap to
a transmitted packet, transmission of the packet is postponed to next
isochronous cycle and an empty packet (NODATA/NOINFO) is transmitted in
this cycle.
Additionally, the value of SYT includes DEFAULT_TRANSFER_DELAY(354.17 micro
second) and delay of one packet.

<h2>Implementation of ALSA firewire stack</h2>
Compliant to IEC 61883-6.
<li>Examples:</li>
</ul>

<h2>Dice quirks</h2>
Dice ASICs and firmwares process the presentation timestamp to generate
sound, however they are not compliant to IEC 61883-6.
Calculated duration for total data blocks in a packet is sometimes different
from the value I described. Approximately, plus/minus 1-2 ticks.
Timing to transmit NODATA/NOINFO packets is independent of gap between
presentation timestamps for consecutive two packets.
The sequence of SYT value in rx/tx packet has no relationships. ALSA dice
driver since Linux 3.19 till 4.5 has reused parameters of incoming packets
for outgoing packets. However, the outgoing sequence is not expected by
the models and causes periodical noises.
Examples:

<h2>Solution</h2>
ALSA firewire stack require timestamp generator and data block calculator
specific for Dice-based models. At least, three functions and one structure
should be changed; amdtp_stream_start(), calculate_data_blocks(),
calculate_syt() and struct amdtp_stream.
This result comes from a fewer models which I use. It's better to gather
more samples from users. For this purpose, tracepoints should be added to
ALSA firewire stack in Linux 4.7. Patchset for the purpose was already
proposed to alsa-devel.

ALSA firewire stack

2016-05-03T13:03:18Z

Mocchi:

ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus.

<h2>Already merged</h2>

<dl>
<dt>snd-firewire-lib</dt>
<dd>A module for helper functions of isochronous packet streaming for IEC 61883-1/6 and AM824 data block processing. (since Linux 2.6.39)</dd>
<dt>snd-isight</dt>
<dd>A driver for audio feature of iSight produced by Apple Inc. (since Linux 3.0)</dd>
<dt>snd-dice</dt>
<dd>A driver for models with DiceII/TCD2210(Dice Mini)/TCD2220(Dice Jr.)/TCD3072-CH ASICs produced by TC Applied Technologies, Inc. (since Linux 3.13)</dd>
<dt>snd-fireworks</dt>
<dd>A driver for models with Fireworks board module produced by Echo Audio Corp. (since Linux 3.16)</dd>
<dt>snd-bebob</dt>
<dd>A driver for models with DM1000/DM1100/DM1500 ASICs and BeBoB firmware produced by ArchWave AG (formerly known as BridgeCo. AG) (since Linux 3.16)</dd>
<dt>snd-oxfw</dt>
<dd>A driver for models with FW970/971 ASICs produced by Oxford Semiconductor (acquired by PLC Technology). (since Linux 3.19)</dd>
<dt>snd-firewire-digi00x</dt>
<dd>A driver for Digi00x series produced by Avid Technology Inc. as a brand of Digidesign. (since Linux 4.4)</dd>
<dt>snd-firewire-tascam</dt>
<dd>A driver for FireWire series produced by TEAC Corp. as a brand of TASCAM. (since Linux 4.4)</dd>
</dl>

<h2>Under development</h2>

<dl>
<dt>snd-firewire-transceiver<dt>
<dd>A driver to communicate on IEEE 1394 bus between several Linux systems.</dd>
<dt>snd-firewire-motu<dt>
<dd>A driver for models produced by Mark of the unicorn.</dd>
<dt>snd-fireface<dt>
<dd>A driver for Fireface family produced by RME.</dd>
</dl>

<h2>Current issues</h2>

<ul>
<li>[[Dice packet sequence quirk and ALSA firewire stack in Linux 4.6]]</li>
</ul>

ALSA firewire stack

2016-05-03T13:00:57Z

Mocchi:

<h2>ALSA firewire stack</h2>

ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus.

<h3>Already merged.</h3>

<dl>
<dt>snd-firewire-lib</dt>
<dd>A module for helper functions of isochronous packet streaming for IEC 61883-1/6 and AM824 data block processing. (since Linux 2.6.39)</dd>
<dt>snd-isight</dt>
<dd>A driver for audio feature of iSight produced by Apple Inc. (since Linux 3.0)</dd>
<dt>snd-dice</dt>
<dd>A driver for models with DiceII/TCD2210(Dice Mini)/TCD2220(Dice Jr.)/TCD3072-CH ASICs produced by TC Applied Technologies, Inc. (since Linux 3.13)</dd>
<dt>snd-fireworks</dt>
<dd>A driver for models with Fireworks board module produced by Echo Audio Corp. (since Linux 3.16)</dd>
<dt>snd-bebob</dt>
<dd>A driver for models with DM1000/DM1100/DM1500 ASICs and BeBoB firmware produced by ArchWave AG (formerly known as BridgeCo. AG) (since Linux 3.16)</dd>
<dt>snd-oxfw</dt>
<dd>A driver for models with FW970/971 ASICs produced by Oxford Semiconductor (acquired by PLC Technology). (since Linux 3.19)</dd>
<dt>snd-firewire-digi00x</dt>
<dd>A driver for Digi00x series produced by Avid Technology Inc. as a brand of Digidesign. (since Linux 4.4)</dd>
<dt>snd-firewire-tascam</dt>
<dd>A driver for FireWire series produced by TEAC Corp. as a brand of TASCAM. (since Linux 4.4)</dd>
</dl>

<h3>Under development</h3>

<dl>
<dt>snd-firewire-transceiver<dt>
<dd>A driver to communicate on IEEE 1394 bus between several Linux systems.</dd>
<dt>snd-firewire-motu<dt>
<dd>A driver for models produced by Mark of the unicorn.</dd>
<dt>snd-fireface<dt>
<dd>A driver for Fireface family produced by RME.</dd>
</dl>

<h3>Current issues</h3>

<dl>
<dt>Dice packet sequence quirk and ALSA firewire stack in Linux 4.6</dt>
<dd>aaa</dd>
</dl>

ALSA firewire stack

2016-05-03T12:56:18Z

Mocchi:

<h2>ALSA firewire stack</h2>

ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus.

<dl>
<dt>snd-firewire-lib</dt>
<dd>A module for helper functions of isochronous packet streaming for IEC 61883-1/6 and AM824 data block processing. (since Linux 2.6.39)</dd>
<dt>snd-isight</dt>
<dd>A driver for audio feature of iSight produced by Apple Inc. (since Linux 3.0)</dd>
<dt>snd-dice</dt>
<dd>A driver for models with DiceII/TCD2210(Dice Mini)/TCD2220(Dice Jr.)/TCD3072-CH ASICs produced by TC Applied Technologies, Inc. (since Linux 3.13)</dd>
<dt>snd-fireworks</dt>
<dd>A driver for models with Fireworks board module produced by Echo Audio Corp. (since Linux 3.16)</dd>
<dt>snd-bebob</dt>
<dd>A driver for models with DM1000/DM1100/DM1500 ASICs and BeBoB firmware produced by ArchWave AG (formerly known as BridgeCo. AG) (since Linux 3.16)</dd>
<dt>snd-oxfw</dt>
<dd>A driver for models with FW970/971 ASICs produced by Oxford Semiconductor (acquired by PLC Technology). (since Linux 3.19)</dd>
<dt>snd-firewire-digi00x</dt>
<dd>A driver for Digi00x series produced by Avid Technology Inc. as a brand of Digidesign. (since Linux 4.4)</dd>
<dt>snd-firewire-tascam</dt>
<dd>A driver for FireWire series produced by TEAC Corp. as a brand of TASCAM. (since Linux 4.4)</dd>
</dl>

<h3>Current issues</h3>

<dl>
<dt>Dice packet sequence quirk and ALSA firewire stack in Linux 4.6</dt>
<dd>aaa</dd>
</dl>

Documentation

2016-05-03T12:54:39Z

Mocchi: /* Developer Info */

{| align="right"
| __TOC__
|}

== User Info ==

*[[ALSA User Info]]
*Hardware Recommendations
*[http://lau.linuxaudio.org/ Linux Audio Users Guide]
*[[Low latency howto]]

== System Maintainers Info ==

*[[System Maintainers documentation]]

*[[Matrix:Main|Sound Card Matrix & INSTALL documentation]]
*[http://alsa.opensrc.org/ The Unofficial ALSA Wiki]
*[http://www.volkerschatz.com/noise/alsa.html A close look at ALSA] an extensive coverage of major aspects by Volker Schatz
*The latest [http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/alsa/alsa-driver/INSTALL INSTALL] file
*kerndriv Updating ALSA Kernel drivers
*olddocs Older documents
*[[asoundrc]]
*Kernel Module overview(snd, virmidi, etc..)

== Tools ==

*alsactl
*amixer, alsamixer
*aplay/arecord
*aconnect, aseqnet
*envy24control
*hdsploader, hdspmixer
*vxloader

== Developer Info ==

*[[ALSA Library API]]
*[[ALSA Driver Documentation]]
*[[Tutorials and Presentations]]
*[[ALSA 0.9.x Developer documentation]]
*[http://hg-mirror.alsa-project.org/ HG (Mercurial) Repositories]
*[[ALSA contributors]]
*[[ALSA firewire stack]]

== Hardware Manufacturers ==

*[[ALSA Soundcard Vendor Information|Getting support for your hardware.]]

ALSA firewire stack (since Linux 2.6.39)

2016-05-03T12:54:18Z

Mocchi: Mocchi moved page ALSA firewire stack (since Linux 2.6.39) to ALSA firewire stack

#REDIRECT [[ALSA firewire stack]]

ALSA firewire stack

2016-05-03T12:54:18Z

Mocchi: Mocchi moved page ALSA firewire stack (since Linux 2.6.39) to ALSA firewire stack

ALSA firewire stack

2016-05-03T12:53:57Z

Mocchi:

ALSA firewire stack

2016-05-03T12:50:45Z

Mocchi:

<h2>ALSA firewire stack</h2>

ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus.

<dl>
<dt>snd-firewire-lib</dt>
<dd>A module for helper functions of isochronous packet streaming for IEC 61883-1/6 and AM824 data block processing. (since Linux 2.6.39)</dd>
<dt>snd-isight</dt>
<dd>A driver for audio feature of iSight produced by Apple Inc.</dd>
<dt>snd-fireworks</dt>
<dd>A driver for models with Fireworks board module produced by Echo Audio Corp.</dd>
<dt>snd-bebob</dt>
<dd>A driver for models with DM1000/DM1100/DM1500 ASICs and BeBoB firmware produced by ArchWave AG (formerly known as BridgeCo. AG)</dd>
<dt>snd-oxfw</dt>
<dd>A driver for models with FW970/971 ASICs produced by Oxford Semiconductor (acquired by PLC Technology).</dd>
<dt>snd-dice</dt>
<dd>A driver for models with DiceII/TCD2210(Dice Mini)/TCD2220(Dice Jr.)/TCD3072-CH ASICs produced by TC Applied Technologies, Inc.</dd>
<dt>snd-firewire-digi00x</dt>
<dd>A driver for Digi00x series produced by Avid Technology Inc. as a brand of Digidesign.</dd>
<dt>snd-firewire-tascam</dt>
<dd>A driver for FireWire series produced by TEAC Corp. as a brand of TASCAM.</dd>
</dl>

<h3></h3>

ALSA firewire stack

2016-05-03T12:45:20Z

Mocchi: Created page with "<h2>ALSA firewire stack</h2> ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus. <dl> <dt>snd-fir..."

<h2>ALSA firewire stack</h2>

ALSA firewire stack includes isochronous packet streaming engine and drivers for audio and music units on IEEE 1394 bus.

<dl>
<dt>snd-firewire-lib</dt>
<dd>A module for helper functions of isochronous packet streaming for IEC 61883-1/6 and AM824 data block processing. (since Linux 2.6.39)</dd>
<dt>snd-fireworks</dt>
<dd>A driver for models with Fireworks board module produced by Echo Audio Corp.</dd>
<dt>snd-bebob</dt>
<dd>A driver for models with DM1000/DM1100/DM1500 ASICs and BeBoB firmware produced by ArchWave AG (formerly known as BridgeCo. AG)</dd>
<dt>snd-oxfw</dt>
<dd>A driver for models with FW970/971 ASICs produced by Oxford Semiconductor (acquired by PLC Technology).</dd>
<dt>snd-dice</dt>
<dd>A driver for models with DiceII/TCD2210(Dice Mini)/TCD2220(Dice Jr.)/TCD3072-CH ASICs produced by TC Applied Technologies, Inc.</dd>
<dt>snd-firewire-digi00x</dt>
<dd>A driver for Digi00x series produced by Avid Technology Inc. as a brand of Digidesign.</dd>
<dt>snd-firewire-tascam</dt>
<dd>A driver for FireWire series produced by TEAC Corp. as a brand of TASCAM.</dd>
</dl>

<h3></h3>

Documentation

2016-05-03T12:21:52Z

Mocchi: Add a page about ALSA firewire stack.

{| align="right"
| __TOC__
|}

== User Info ==

*[[ALSA User Info]]
*Hardware Recommendations
*[http://lau.linuxaudio.org/ Linux Audio Users Guide]
*[[Low latency howto]]

== System Maintainers Info ==

*[[System Maintainers documentation]]

*[[Matrix:Main|Sound Card Matrix & INSTALL documentation]]
*[http://alsa.opensrc.org/ The Unofficial ALSA Wiki]
*[http://www.volkerschatz.com/noise/alsa.html A close look at ALSA] an extensive coverage of major aspects by Volker Schatz
*The latest [http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/alsa/alsa-driver/INSTALL INSTALL] file
*kerndriv Updating ALSA Kernel drivers
*olddocs Older documents
*[[asoundrc]]
*Kernel Module overview(snd, virmidi, etc..)

== Tools ==

*alsactl
*amixer, alsamixer
*aplay/arecord
*aconnect, aseqnet
*envy24control
*hdsploader, hdspmixer
*vxloader

== Developer Info ==

*[[ALSA Library API]]
*[[ALSA Driver Documentation]]
*[[Tutorials and Presentations]]
*[[ALSA 0.9.x Developer documentation]]
*[http://hg-mirror.alsa-project.org/ HG (Mercurial) Repositories]
*[[ALSA contributors]]
*[[ALSA firewire stack (since Linux 2.6.39)]]

== Hardware Manufacturers ==

*[[ALSA Soundcard Vendor Information|Getting support for your hardware.]]

Matrix:Vendor-Creative Labs

2011-09-02T14:55:31Z

Mocchi: /* Soundcard List for [http://www.creative.com Creative Labs] */ Add EMU 0404 USB support

{{Matrix:VendorBegin}}

For developer information on the [http://www.emu.com E-Mu]' line, see https://bugtrack.alsa-project.org/wiki/wikka.php?wakka=emu&show_comments=1

==Soundcard List for [http://www.creative.com Creative Labs]==

{| class="MatrixTable"
! Product
! Chipset(s)
! Driver & Docs
! Tags, Notes
|-
|
{| class="MatrixTableInner"
| Prodikeys PC-MIDI
|-
|}
|
{| class="MatrixTableInner"
| ?
|-
|}
| [[Matrix:Module-usb-audio|Details]]
| [[Matrix:Tag-USB|[USB]]] [[Matrix:Tag-MIDIio|[MIDIi]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster 1.0
|-
| Sound Blaster 1.5
|-
| Sound Blaster 2.0
|-
| Sound Blaster Pro
|-
|}
|
{| class="MatrixTableInner"
| sb8
|-
|}
| [[Matrix:Module-sb8|Details]]
| [[Matrix:Tag-ISA|[ISA]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-Sample8bit|[Sample8bit]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster 16
|-
| Sound Blaster 16 ASP
|-
| Sound Blaster 16 PnP
|-
| Sound Blaster Vibra16C
|-
| Sound Blaster Vibra16CL
|-
| Sound Blaster Vibra16S
|-
| Sound Blaster Vibra16X
|-
|}
|
{| class="MatrixTableInner"
| sb16
|-
|}
| [[Matrix:Module-sb16|Details]]
| [[Matrix:Tag-ISA|[ISA]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [CSP supported]
|-
|
{| class="MatrixTableInner"
| Sound Blaster 32 AWE
|-
| Sound Blaster 32 AWE PnP
|-
| Sound Blaster 64 Gold
|-
| Sound Blaster 64 Value
|-
|}
|
{| class="MatrixTableInner"
| sb16
|-
| emu8000
|-
|}
| [[Matrix:Module-sbawe|Details]]
| [[Matrix:Tag-ISA|[ISA]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-Wavetable|[Wavetable]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster PCI64 (earlier model)
|-
| Sound Blaster PCI128 (earlier model CT4700)
|-
|}
|
{| class="MatrixTableInner"
| ES1370
|-
|}
| [[Matrix:Module-ens1370|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster 16 PCI
|-
| Sound Blaster PCI64 (newer model)
|-
| Sound Blaster PCI128 (newer model)
|-
| Sound Blaster PCI128 (CT5880)
|-
| Sound Blaster Ensoniq AudioPCI
|-
|}
|
{| class="MatrixTableInner"
| ES1371
|-
|}
| [[Matrix:Module-ens1371|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster PCI 512
|-
| Sound Blaster Live
|-
| Sound Blaster Live Platinum
|-
| Sound Blaster Live Value
|-
| Sound Blaster Live 5.1
|-
|}
|
{| class="MatrixTableInner"
| emu10k1
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster Audigy Platinum
|-
| Sound Blaster Audigy Digital Entertainment
|-
| Sound Blaster Audigy Gamer
|-
| Sound Blaster Audigy ES
|-
|}
|
{| class="MatrixTableInner"
| emu10k2
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]]
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/Audigy2ZS_platinum_pro/ Sound Blaster Audigy2 ZS Platinum Pro]
|-
|}
|
{| class="MatrixTableInner"
| emu10k2
|-
| CA0151/P16V
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]]
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/Audigy4pro/ Sound Blaster Audigy4 Pro]
|-
|}
|
{| class="MatrixTableInner"
| emu10k2
|-
| CA0151/P16V
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]] Same features supported as Audigy2 ZS Platinum Pro.
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/Audigy4pro/ Sound Blaster Audigy4 (Non Pro)]
|-
|}
|
{| class="MatrixTableInner"
| emu10k2
|-
| CA0151/P16V
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]] Mixed reports, so might not work for you.
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/audigy2NX/ Sound Blaster Audigy2 NX]
|-
|}
|
{| class="MatrixTableInner"
| CA0186
|-
| EP7309
|-
|}
| [[Matrix:Module-usb-audio|Details]]
| [[Matrix:Tag-USB|[USB]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] SPDIF output does not function.
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/Audigy2zs_notebook/ Sound Blaster Audigy 2 ZS Notebook PCMCIA]
|-
|}
|
{| class="MatrixTableInner"
| Tina2
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCMCIA|[PCMCIA]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]] Digital/Analog input/output working. Bit accurate digital features (AC3/DTS) not implemented yet. Needs more development work.
|-
|
{| class="MatrixTableInner"
| [http://creative.com/products/product.asp?category=1%26subcategory=204%26product=11226 Sound Blaster Audigy 2 ZS Video Editor USB]
|-
|}
|
{| class="MatrixTableInner"
| UNKNOWN
|-
|}
|
| [[Matrix:Tag-Unsupported|[Unsupported]]] [[Matrix:Tag-USB|[USB]]] Card delivered to developers. No support yet.=> Works in Stereo (spdif/jack) at least.
|-
|
{| class="MatrixTableInner"
| [http://creative.com/products/welcome.asp?category=1 Sound Blaster X-Fi]
|-
| X-Fi Elite Pro
|-
| X-Fi Fatal1ty
|-
| X-Fi Platinum
|-
| X-Fi XtremeMusic
|-
| X-Fi XtremeGamer
|}
|
{| class="MatrixTableInner"
| emu20k1
|-
|}
| [[Matrix:Module-snd-ctxfi|Details]]
| [[Matrix:Tag-PCI|[PCI]]] Partially supported on 1.0.21; EAX and Advanced sound options like crystalizer not available
|-
|
{| class="MatrixTableInner"
| X-Fi Titanium
|-
| X-Fi Titanium Fatal1ty Champion
|-
| X-Fi Titanium Fatal1ty Professional
|-
| X-Fi Titanium Professional Audio
|-
|}
|
{| class="MatrixTableInner"
| emu20k2
|-
|}
| [[Matrix:Module-snd-ctxfi|Details]]
| [[Matrix:Tag-PCI|[PCI]]] Partially supported on 1.0.21; EAX and Advanced sound options like crystalizer not available
|-
|
{| class="MatrixTableInner"
| X-Fi Titanium HD
|}
|
{| class="MatrixTableInner"
| emu20k2
|-
|}
|
| [[Matrix:Tag-PCIE|[PCIE]]] does not work
|-
|
{| class="MatrixTableInner"
| X-Fi Xtreme Audio (PCI)
|}
|
{| class="MatrixTableInner"
| CA0106
|-
|}
|
| [[Matrix:Tag-PCI|[PCI]]] unknown
|-
|
{| class="MatrixTableInner"
| X-Fi Xtreme Audio (PCIe)
|}
|
{| class="MatrixTableInner"
| CA0110
|-
|}
|
| [[Matrix:Tag-PCIE|[PCIE]]] does not work
|-
|
{| class="MatrixTableInner"
| X-Fi Surround 5.1
|}
|
{| class="MatrixTableInner"
| ?
|-
|}
|
[[Matrix:Module-usb-audio|Details]]
| [[Matrix:Tag-USB|[USB]]] volume knob works via LIRC: [http://alsa.opensrc.org/Usb-audio#Creative_USB_X-Fi_Surround_5.1 instructions on setting it up]
|-
|
{| class="MatrixTableInner"
| X-Fi HD
|}
|
{| class="MatrixTableInner"
| ?
|-
|}
|
[[Matrix:Module-usb-audio|Details]]
| [[Matrix:Tag-USB|[USB]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-TOSio|[TOSio]]] as of 1.0.24: no support for 96 kHz, SPDIF not tested. Volume knob works via LIRC: [http://alsa.opensrc.org/Usb-audio#Creative_USB_X-Fi_HD instructions on setting it up]
|-
|
{| class="MatrixTableInner"
| [http://creative.com/products/product.asp?category=1%26subcategory=205%26product=14257 Sound Blaster Audigy SE]
|-
| [http://creative.com/products/product.asp?category=1&subcategory=205&product=14189 Sound Blaster Audigy Value]
|-
| Sound Blaster 5.1 VX
|-
|}
|
{| class="MatrixTableInner"
| CA0106
|-
|}
| [[Matrix:Module-ca0106|Details]]
| [[Matrix:Tag-PCI|[PCI]]] Not all features on all models supported. On the VX, white noise on playback unless initialized in Windows first. One quirky (but permanent) workaround is to enable the old oss modules, specifically the 100% sound blaster compatible module (sb). You don't have to load the oss modules. The alsa module snd-ca0106 works fine somehow if the old sb module is compiled in the kernel as a module (no white noise).
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/audigy2value/ Sound Blaster Audigy2 ZS Value]
|-
|}
|
{| class="MatrixTableInner"
| CA0108
|-
|}
| [[Matrix:Module-emu10k1|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-48kHz|[48kHz]]] [[Matrix:Tag-Wavetable|[Wavetable]]] [[Matrix:Tag-HWMIX|[HWMIX]]] No 96khz 24Bit support.
|-
|
{| class="MatrixTableInner"
| Sound Blaster PCI X (Dell OEM)
|-
|}
|
{| class="MatrixTableInner"
| SB0200
|-
|}
| [[Matrix:Module-emu10k1x|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]]
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/audigyls/ Sound Blaster LS]
|-
|}
|
{| class="MatrixTableInner"
| SB0310
|-
| P17
|-
|}
| [[Matrix:Module-ca0106|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster Live 24bit
|-
| Sound Blaster Live 7.1
|-
|}
|
{| class="MatrixTableInner"
| SB0410
|-
| P17
|-
|}
| [[Matrix:Module-ca0106|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-MIDIio|[MIDIio]]]
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/extigy/ Sound Blaster Extigy]
|-
|}
|
{| class="MatrixTableInner"
| Extigy
|-
|}
| [[Matrix:Module-usb-audio|Details]]
| [[Matrix:Tag-USB|[USB]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [no 96kHz support, no support for 24-bit samples]
|-
|
{| class="MatrixTableInner"
| [http://www.soundblaster.com/products/mp3+/ Sound Blaster MP3+]
|-
|}
|
{| class="MatrixTableInner"
| MP3+
|-
|}
| [[Matrix:Module-usb-audio|Details]]
| [[Matrix:Tag-USB|[USB]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]]
|-
|
{| class="MatrixTableInner"
| Sound Blaster Connect (USB)
|-
|}
|
|
| [[Matrix:Tag-USB|[USB]]] [[Matrix:Tag-Unknown|[Unknown]]]
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505%26subcategory=491%26product=9872 E-MU 1212m]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.14
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=9872 E-MU 1212m PCI ver2]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.15
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=19169 E-MU 1212m PCIe]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
|
| [[Matrix:Tag-PCIE|[PCIE]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-Unknown|[Unknown]]]
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505%26subcategory=491%26product=9871 E-MU 1820m]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.14
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=13552 E-MU 1616m notebook]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.15
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=13552 E-MU 1616 notebook]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.15
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=13552 E-MU 1616m PCI]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.15
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=19007 E-MU 1616m PCIe]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCIE|[PCIE]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] [[Matrix:Tag-MIDIio|[MIDIio]]] [[Matrix:Tag-Unknown|[Unknown]]]
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=13554 E-MU 1616 PCI]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.15
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=505&subcategory=491&product=10447 E-MU 0404 PCI]
|-
|}
|
{| class="MatrixTableInner"
| CA0102, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-PCI|[PCI]]] [[Matrix:Tag-ANALOGio|[ANALOGio]]] [[Matrix:Tag-RCAio|[RCAio]]] [[Matrix:Tag-TOSio|[TOSio]]] [[Matrix:Tag-ADATio|[ADATio]]] Support arriving in 1.0.15 [MIDIio functional, but only @ 48kHz]
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=610&subcategory=611&product=15185 E-MU 0404 USB]
|-
|}
|
{| class="MatrixTableInner"
| CA0188, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-USB|[USB]]] Fully supported by ALSA 1.0.23 and later.
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=610&subcategory=611&product=15186 E-MU 0202 USB]
|-
|}
|
{| class="MatrixTableInner"
| CA0188, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-USB|[USB]]][[Matrix:Tag-ANALOGio|[ANALOGio]]] 44/16 playback and recording works on Ubuntu 10.10 with ALSA 1.0.23
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=610&subcategory=611&product=15187 E-MU Xmidi2x2 USB]
|-
|}
|
{| class="MatrixTableInner"
| CA????, FPGA
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-USB|[USB]]] NOT SUPPORTED. Developer has not yet asked for to be supplied with a hardware sample and datasheets.
|-
|
{| class="MatrixTableInner"
| [http://www.emu.com/products/product.asp?category=610&subcategory=611&product=17511 E-MU Tracker Pre]
|-
|}
|
{| class="MatrixTableInner"
| ?
|-
|}
| [[Matrix:Module-emu10k1-fpga|Details]]
| [[Matrix:Tag-USB|[USB]]][[Matrix:Tag-ANALOGio|[ANALOGio]]] Partially supported (only 44.1kHz 16bit, no volume control) in sound-2.6.git

|}
{{Matrix:VendorEnd}}