Skip to main content

deepomatic-command-line-interface

Deepomatic Command Line Interface.

This command line interface has been made to help you interact with our services via the command line.

Build Status

CLI Documentation

Find the complete documentation at docs.deepomatic.com/deepomatic-cli/

Installation

pip install deepomatic-cli

If you need rpc support, prefer:

# requires deeomatic-rpc package to be installed
pip install deepomatic-cli[rpc]

Autocompletion

To activate the autocompletion the easiest way is to add the following line to your shell config file:

eval "$(register-python-argcomplete deepo)"

For example if you use bash:

cat <<"EOF" >> ~/.bashrc

# activate deepomatic-cli autocomplete
eval "$(register-python-argcomplete deepo)"
EOF

(If it slows down your shell startup too much, you can pre-generate the completion into a static file then source it in your .bashrc: that doesn't change when deepo-cli is updated (except when updating argcomplete itself).)

For more information, checkout the documentation of argcomplete

FAQ

opencv-python (-headless) installation takes forever

Depending on your pip version, it might rebuild it from source. 19.3 is the minimum supported version

  • Check version with pip -V
  • Update with pip install 'pip>=19.3'

Window output doesn't work. I get a cv2.error.

deepomatic-cli ships with opencv-python-headless as most of the features don't need a GUI. This also avoids requiring libGL on the system (it is for example usually not there in docker containers). If you want to use the GUI features, we recommend installing opencv-python after installing deepomatic-cli:

pip install deepomatic-cli
opencv_install=$(pip3 freeze | grep opencv-python-headless | sed 's/-headless//g')
pip uninstall opencv-python-headless
pip install $opencv_install

About the output video codec

The CLI makes heavy use of OpenCV which does not provide the ability to configure the video encoder settings. We can choose the codec to use (FourCC), but we can't choose the bitrate, quality, number of pass, profile or any other settings. The quality chosen by OpenCV remains a small mystery, it seems to vary depending on the codec.

If for some reason the output video encoding does not suit you (too heavy, bad quality), here are our options:

Changing the FourCC

Set the --fourcc option of the CLI. The opencv-python package only provide the codecs which have a free license. This means you will not be able to choose avc1 or hevc. We provide a dockerfile and an installation script to rebuild opencv-python with x264 encoder (corresponding to acv1 FourCC). The readme can be found here. Please makes sure you can use it (it is patented and not free).

If you are on windows, there is an alternative using openh264:

  • Download the library (should work with openh264-1.7.0-win64.dll.bz2)
  • Extract the archive in C:\Windows\System32 or in the same directory where the CLI command is launched

Piping to ffmpeg or cvlc

If you want more freedom on the encoding settings, we suggest piping the CLI to ffmpeg or cvlc by using the option -o stdout (working with infer, draw, blur and noop commands). In both case you need to tell ffmpeg or cvlc about the resolution, framerate and color space of the input stream. You can use ffprobe or mediainfo to get the resolution and framerate of your input video. The color space (chroma) does not depend on your input video but on our CLI which by default output BGR color space.

Again, make sure you can legally use the codec specified in the command.

Example using ffmpeg

deepo platform model draw -i $input_video_path -o stdout -r $model_id | ffmpeg -f rawvideo -pixel_format bgr24 -video_size 1280x720 -framerate 15 -i - -c:v $codec $output_video_path

Example using cvlc

BGR color space is not supported by cvlc, so we have to convert the stream to RGB.

deepo platform model draw -i $input_video_path -o stdout -r $model_id --output_color_space RGB | cvlc --demux=rawvideo --rawvid-fps=15 --rawvid-width=1280 --rawvid-height=720 --rawvid-chroma=RV24 - --sout "#transcode{vcodec=$codec}:std{access=file,dst=$output_video_path}" vlc://quit

Bugs

Please send bug reports to support@deepomatic.com

Metadata

Release files for deepomatic-cli 0.7.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deepomatic-cli 0.7.7
File Size Uploaded Provenance Actions
deepomatic-cli-0.7.7.tar.gz 49.4 kB Without provenance Details for deepomatic-cli-0.7.7.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for deepomatic-cli 0.7.7
File Interpreter ABI Platform Actions
deepomatic_cli-0.7.7-py2.py3-none-any.whl Python 2, Python 3 none any Details for deepomatic_cli-0.7.7-py2.py3-none-any.whl

Total release size: 124.9 kB

Release files / deepomatic-cli-0.7.7.tar.gz

Download URL deepomatic-cli-0.7.7.tar.gz
Size 49.4 kB
Tags Source
SHA-256 checksum
How to use checksums
e35167b29c469cc909e5097484d65850d955cb16c8d23d1bf022a1a15f831e3f
BLAKE2b-256 checksum
How to use checksums
561aa85eeda8a518e1deb8cb187ecfe04110272cad020dc9d1b65ea1f15e674e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.10

Release files / deepomatic_cli-0.7.7-py2.py3-none-any.whl

Download URL deepomatic_cli-0.7.7-py2.py3-none-any.whl
Size 75.6 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
b28e5fed7bc7a94e590e49fcabca46ead36c5808cdeb8908726510c96032bcdc
BLAKE2b-256 checksum
How to use checksums
c12000e7ee6770b93acdd38e55628f8c84d8d01c7cebb18d7c0bf6d82165fb09
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.10

Security for deepomatic-cli 0.7.7

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page