path: root/python-deepomatic-cli.spec

%global _empty_manifest_terminate_build 0
Name:		python-deepomatic-cli
Version:	0.7.7
Release:	1
Summary:	Deepomatic CLI
License:	MIT License
URL:		https://github.com/Deepomatic/deepocli
Source0:	https://mirrors.aliyun.com/pypi/web/packages/56/1a/a85eeda8a518e1deb8cb187ecfe04110272cad020dc9d1b65ea1f15e674e/deepomatic-cli-0.7.7.tar.gz
BuildArch:	noarch

Requires:	python3-opencv-python-headless
Requires:	python3-tqdm
Requires:	python3-requests
Requires:	python3-text-unidecode
Requires:	python3-greenlet
Requires:	python3-gevent
Requires:	python3-jsonschema
Requires:	python3-deepomatic-api
Requires:	python3-PyYAML
Requires:	python3-GitPython
Requires:	python3-argcomplete
Requires:	python3-deepomatic-rpc

%description
# deepomatic-command-line-interface

[Deepomatic](https://www.deepomatic.com) Command Line Interface.

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

[![Build Status](https://travis-ci.com/Deepomatic/deepocli.svg?branch=master)](https://travis-ci.com/Deepomatic/deepocli)

# CLI Documentation

Find the complete documentation at [docs.deepomatic.com/deepomatic-cli/](https://docs.deepomatic.com/deepomatic-cli/)

# Installation

```bash
pip install deepomatic-cli
```

If you need rpc support, prefer:
```bash
# 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:

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

For example if you use bash:

```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](https://github.com/kislyuk/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`:
```bash
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](docker/README.md). Please makes sure you can use it (it is patented and not free).

If you are on windows, there is an alternative using [openh264](https://github.com/cisco/openh264):
- Download the [library](https://github.com/cisco/openh264/releases) (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`

```bash
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`.

```bash
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




%package -n python3-deepomatic-cli
Summary:	Deepomatic CLI
Provides:	python-deepomatic-cli
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-deepomatic-cli
# deepomatic-command-line-interface

[Deepomatic](https://www.deepomatic.com) Command Line Interface.

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

[![Build Status](https://travis-ci.com/Deepomatic/deepocli.svg?branch=master)](https://travis-ci.com/Deepomatic/deepocli)

# CLI Documentation

Find the complete documentation at [docs.deepomatic.com/deepomatic-cli/](https://docs.deepomatic.com/deepomatic-cli/)

# Installation

```bash
pip install deepomatic-cli
```

If you need rpc support, prefer:
```bash
# 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:

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

For example if you use bash:

```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](https://github.com/kislyuk/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`:
```bash
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](docker/README.md). Please makes sure you can use it (it is patented and not free).

If you are on windows, there is an alternative using [openh264](https://github.com/cisco/openh264):
- Download the [library](https://github.com/cisco/openh264/releases) (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`

```bash
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`.

```bash
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




%package help
Summary:	Development documents and examples for deepomatic-cli
Provides:	python3-deepomatic-cli-doc
%description help
# deepomatic-command-line-interface

[Deepomatic](https://www.deepomatic.com) Command Line Interface.

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

[![Build Status](https://travis-ci.com/Deepomatic/deepocli.svg?branch=master)](https://travis-ci.com/Deepomatic/deepocli)

# CLI Documentation

Find the complete documentation at [docs.deepomatic.com/deepomatic-cli/](https://docs.deepomatic.com/deepomatic-cli/)

# Installation

```bash
pip install deepomatic-cli
```

If you need rpc support, prefer:
```bash
# 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:

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

For example if you use bash:

```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](https://github.com/kislyuk/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`:
```bash
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](docker/README.md). Please makes sure you can use it (it is patented and not free).

If you are on windows, there is an alternative using [openh264](https://github.com/cisco/openh264):
- Download the [library](https://github.com/cisco/openh264/releases) (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`

```bash
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`.

```bash
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




%prep
%autosetup -n deepomatic-cli-0.7.7

%build
%py3_build

%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
	find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
	find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
	find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
	find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
	find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .

%files -n python3-deepomatic-cli -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.7.7-1
- Package Spec generated