ta1394-avc-ccm

Crates.iota1394-avc-ccm
lib.rsta1394-avc-ccm
version0.2.0
sourcesrc
created_at2022-07-29 10:48:23.758334
updated_at2023-04-18 11:30:57.858499
descriptionA pure-Rust implementation of AV/C commands for connection and compatibility management defined by 1394 Trading Association
homepagehttps://alsa-project.github.io/gobject-introspection-docs/
repositoryhttps://github.com/alsa-project/snd-firewire-ctl-services
max_upload_size
id634939
size12,478
GObject Introspection (github:alsa-project:gobject-introspection)

documentation

https://docs.rs/ta1394-avc-ccm/

README

The crate includes Rust elements for the part of protocol defined by 1394 Trading Association (1394 TA).

Protocol documentation

The protocol is documented in:

  • AV/C Connection and Compatibility Management Specification 1.1 (Mar. 19, 2003, 1394 Trading Association, TA Document 2002010)

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.

Usage

Add the following line to your Cargo.toml file:

[dependencies]
ta1394-avc-ccm = "0.2"

Some documented AV/C commands are available:

  • SignalSource (clause "7.1 SIGNAL SOURCE command")

The commands should be given to implementation of Ta1394Avc trait provided in ta1394-avc-general crate to perform AV/C operation.

License

The crate is released under MIT license.

Support

If finding issue, please file it in https://github.com/alsa-project/snd-firewire-ctl-services/.

Contribution

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.

Commit count: 2656

cargo fmt