Crates.io | ta1394-avc-audio |
lib.rs | ta1394-avc-audio |
version | 0.2.0 |
source | src |
created_at | 2022-07-29 10:46:41.355271 |
updated_at | 2023-04-18 11:26:08.222309 |
description | A pure-Rust implementation of AV/C commands for audio subunit defined by 1394 Trading Association |
homepage | https://alsa-project.github.io/gobject-introspection-docs/ |
repository | https://github.com/alsa-project/snd-firewire-ctl-services |
max_upload_size | |
id | 634936 |
size | 58,557 |
The crate includes Rust elements for the part of protocol defined by 1394 Trading Association (1394 TA).
The protocol is documented in:
1394 TA was formed 1994 and decided to close its official operation 2015. As of 2021, it has been
dissolved and close its web site under URL http://1394ta.org
in the end of year.
The document is itself available at Internet Archive service when seeking
URL http://1394ta.org/specifications/
with enough care of cached date.
Add the following line to your Cargo.toml file:
[dependencies]
ta1394-avc-audio = "0.2"
The crate consists of two parts; some AV/C commands and FDF format of A/M packet.
Some documented AV/C commands are available:
AudioSelector
(clause "10.2 Selector function block")AudioFeature
(clause "10.3 Feature function block")AudioProcessing
(clause "10.4 Processing function block")The commands should be given to implementation of Ta1394Avc
trait provided in
ta1394-avc-general crate to perform AV/C operation.
The AmdtpFdf
structure is provided to build and parse &[u8] for some events of Audio and Music
Data Transmission protocol.
The crate is released under MIT license.
If finding issue, please file it in https://github.com/alsa-project/snd-firewire-ctl-services/.
If intending for code contribution, I would like the user and developer to take care of some points before working.
It's well-known that the association promoted by several vendors tends to publishes specifications and documentations with over-engineering for several reasons; e.g. rat race in business or market. Beside the risk to include bug is exponentially increased when the code base is larger and larger. It's not preferable for your work just to fulfill whole the specifications and documentations.
The point is that there is actual requirement for the new code. For example, the crate includes some AV/C commands to satisfy requirement of snd-firewire-ctl-services project. It's preferable for you to have actual application using the new code.