Dolby.io REST APIs Client for Python - CLI
Command Line Interface utility for the dolby.io REST Communications and Media APIs.
Install this project
Check the dolbyio-rest-apis-cli package on PyPI. To install the latest stable python package run the following command:
python3 -m pip install dolbyio-rest-apis-cli
Upgrade your package to the latest version:
python3 -m pip install --upgrade dolbyio-rest-apis-cli
Communications Commands
Display the help and version of the command line:
communications --help
communications --version
Authentication
Get your app key and secret from the dolby.io dashboard and run the following command to get the access token as a json payload:
communications auth -k "APP_KEY" -s "APP_SECRET" --output json
Add the flag --api to get an access token that you can use to query the REST APIs.
Change the output to --output text to get a text format for the output.
Use --output access_token to retrieve only the access token so you can easily assign it to a variable:
ACCESS_TOKEN=$(communications auth -k "APP_KEY" -s "APP_SECRET" --api --output access_token 2> /dev/null)
Remix
Using the access token you've retrieved using the auth command, you can start a remix for a specific conference:
communications remix \
--access_token "ACCESS_TOKEN" \
--cid "00000000-0000-0000-0000-000000000000" \
--start \
--output json
Or simply check the status of a remix:
communications remix \
--access_token "ACCESS_TOKEN" \
--cid "00000000-0000-0000-0000-000000000000" \
--output json
Streaming
Start the streaming to an RTMP endpoint for a specific conference:
communications streaming \
--access_token "ACCESS_TOKEN" \
--cid "00000000-0000-0000-0000-000000000000" \
--action start \
--target rtmp \
--output json \
--urls "rtmp://a.rtmp.youtube.com/live2/{streaming_key}"
Stop the RTMP streaming for a specific conference:
communications streaming \
--access_token "ACCESS_TOKEN" \
--cid "00000000-0000-0000-0000-000000000000" \
--action stop \
--target rtmp \
--output json
Media Commands
Display the help and version of the command line:
media --help
media --version
Authentication
Get your app key and secret from the dolby.io dashboard and run the following command to get the access token as a json payload:
media auth -k "APP_KEY" -s "APP_SECRET" --output json
Change the output to --output text to get a text format for the output.
Use --output access_token to retrieve only the access token so you can easily assign it to a variable:
ACCESS_TOKEN=$(media auth -k "APP_KEY" -s "APP_SECRET" --output access_token 2> /dev/null)
Input / Output
Upload a file to Dolby.io temporary storage:
media io \
--access_token "<ACCESS_TOKEN>" \
--dlb_url "dlb://in/file.mp4" \
--file "/path/to/file.mp4" \
upload
Download a file from Dolby.io temporary storage:
media io \
--access_token "<ACCESS_TOKEN>" \
--dlb_url "dlb://out/processed_file.mp4" \
--file "/path/to/processed_file.mp4" \
download
Enhance
Start enhancing a media:
media enhance
--access_token "<ACCESS_TOKEN>" \
start \
--file "/path/to/job_description.json"
The result is the job identifier.
Get the result from a enhancement job:
media enhance
--access_token "<ACCESS_TOKEN>" \
result \
--job_id "00000000-0000-0000-0000-000000000000"
Music Mastering
Start mastering a music:
media mastering
--access_token "<ACCESS_TOKEN>" \
start \
--file "/path/to/job_description.json"
The result is the job identifier.
Get the result from a music mastering job:
media mastering
--access_token "<ACCESS_TOKEN>" \
result \
--job_id "00000000-0000-0000-0000-000000000000"
Metadata
Release files for dolbyio-rest-apis-cli 3.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dolbyio-rest-apis-cli-3.6.2.tar.gz | 56.4 kB | Without provenance | Details for dolbyio-rest-apis-cli-3.6.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dolbyio_rest_apis_cli-3.6.2-py3-none-any.whl | Python 3 | none | any | Details for dolbyio_rest_apis_cli-3.6.2-py3-none-any.whl |
Total release size: 127.8 kB
Release files / dolbyio-rest-apis-cli-3.6.2.tar.gz
| Download URL | dolbyio-rest-apis-cli-3.6.2.tar.gz |
|---|---|
| Size | 56.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4360e1fa90cd60650a089d21c6f50916df0d356f2e6ab5ed2fb3f6c37b1e951c
|
|
BLAKE2b-256 checksum How to use checksums |
2bc1f4960769565685049b08c5a2e0bd629d83ad8bf34b7e67a450d177e04434
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Release files / dolbyio_rest_apis_cli-3.6.2-py3-none-any.whl
| Download URL | dolbyio_rest_apis_cli-3.6.2-py3-none-any.whl |
|---|---|
| Size | 71.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ddbd33181331fd1d124a1f2d7e7892f6f9ad185ea79c8c21288ec85887be042
|
|
BLAKE2b-256 checksum How to use checksums |
f6d5e8858d659eab78098f73b72d59622edc75fd7c398c577d2f4508e16a3bfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Security for dolbyio-rest-apis-cli 3.6.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.