Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support of input type "std input" #434

Open
theojk1 opened this issue Oct 6, 2024 · 1 comment
Open

Support of input type "std input" #434

theojk1 opened this issue Oct 6, 2024 · 1 comment
Labels

Comments

@theojk1
Copy link

theojk1 commented Oct 6, 2024

Problem/Use Case

PySceneDetect is designed to process one input file only. Most of the files I want to process are splited in 1GB chunks (vob files).

Solutions

Other programs can be called with an input type std-input. Which means the frames of the video input are read from the std input and this is filled by a pipe by another program (in my case it would be vaporSynth).

Proposed Implementation:

I use this for the finale encoding of the videos with x265. This encoder program has a command "--input -" which tells it, to read from std input pipe instead of an input file

Alternatives:

Alternative would be the direct support of AviSynth-API. So the inputfile would be a AviSynth-Script file.

Examples:
https://www.videolan.org/developers/x265.html
https://www.vapoursynth.com/

@Breakthrough
Copy link
Owner

Breakthrough commented Oct 18, 2024

This is possible with the Python API if you use the PyAV backend. How do you specify the pixel format when working with videos like this?

I'm open to integrating this into the command-line but I'm not that familiar with processing videos this way. It should be possible to create a new backend with the AviSynth Python API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants