How to stop grabbing ?

[grzegorznw]

I would like to stop the grabbing before the streaming ends.
If I stop the docker container the file will not be saved into save directory and all data will be lost.
How to stop the script and let them to finish saving file.

Kind Regards

[dwa99]

Same question here I use local script file. By pressing ctrl +q script still grabs streaming so file is constantly growing.
Ps. jaka jest zaleta wlaczenia skryptu w dockerze?

[KFERMercer]

The process residual issue of FFmpeg is a upstream problem, and has been around for a long time. All programs that reference FFmpeg will have this problem. As I tested, the severity of this problem depends on the distro. I've seen it a couple times on Debian, but never on Arch.

Back to your description, I don't really know what ctrl + q is, but you can switch to ctrl + c, which will send a SIGINT to the script, but there's still a very small probability to having residual process.

Or, you can use this script for secondary wrapping: #16 (comment). It will ensure that all processes are stopped on exit.

jaka jest zaleta wlaczenia skryptu w dockerze?

I can't read these words. here's the answer based on the translation, The docker container includes 2 scripts, ctbcap-healthcheck, which used to periodically check the health of the container; and ctbcap its self. There are several benefits of using container:

1. Easy to manage and upgrade.
2. Daemon. Easy to start, stop, schedule, autostart on boot.
3. Tailored FFmpeg. Only 4MB. Most of distro provided FFmpeg are 150MB+ (excluding dependencies), and may not be the best version. Most headless servers don't want FFmpeg, so containers are a good choice.
4. Like you said, it's safe to guarantee no process residue.

[KFERMercer]

I would like to stop the grabbing before the streaming ends. If I stop the docker container the file will not be saved into save directory and all data will be lost. How to stop the script and let them to finish saving file.

Kind Regards

Strange. How did you have this problem? The script doesn't delete any files, what's your compose config?

The only explanation is that CB has recently (temporary? ) limited the speed of single-threaded downloads, resulting in 30 sec ~ 1 min after starting record before it gets enough data and starts writing to file. If you exit the docker during this , you will get nothing.

But nonetheless, once you see the file, the file will never disappear.

[grzegorznw]

Hi @KFERMercer.
It's exactly as You described - I stopped docker too quickly - so the file was empty.
To stop kkmpeg we can also send kill -SIGINT

I have one more question - Is it possible to rewrite this script into a python script ?

Thanks

[KFERMercer]

I have one more question - Is it possible to rewrite this script into a python script ?

It's easy, but I have no plans to do it. Rewriting this project in python is only bad and have no any beneficial.

1. Will introduce python dependencies. This will increase the final container tarball size by ~100mb. To think, I even spent an afternoon working on their build system to tailoring FFmpeg to Reduce the size of FFmpeg, Now asking me to add 100MB to include python? (BTW DASH is only 134.1 kB)
2. One-Command Run is completely destroyed. I have to assume that all devices must have python interpreter.
3. The doomsday of low-power devices. DASH/Ash is very energy efficient. Imagine you have to install python on a $5 second hand OpenWrt router.

And more. The only reason I can imagine is if you want to use it on Windows. But installing Python on Windows is a even bigger disaster. You will be embedding a foreign program into the corner of your system that can never be fully uninstalled. Compared to just go install WSL is a million times better. Least it's a Microsoft official implementation.