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

Request: pre and post processing #52

Open
lars18th opened this issue Oct 22, 2019 · 3 comments
Open

Request: pre and post processing #52

lars18th opened this issue Oct 22, 2019 · 3 comments

Comments

@lars18th
Copy link

Hi,

The prescript and postscript functions are very useful to start/stop some external process. However, I request if some "pre-processing" and "post-processing" of the TS can be done. At time only the ffmpeg process can receive data and generate the TS. But my request is about something like:

PRE-PROCESS ---/ pipe /---> FFMPEG ---/ pipe /---> POST-PROCESS >>> node-ffmpeg-mpegts-proxy

The idea is to feed the ffmpeg with an external tool, or do a change in the TS from the ffmpeg process to replace some data.

You agree?

@Jalle19
Copy link
Owner

Jalle19 commented Oct 22, 2019

Could become quite complicated, I have to think about it a bit.

@lars18th
Copy link
Author

Could become quite complicated, I have to think about it a bit.

OK. I hope you can found a simple solution.

Thank you for listening! 😉

@lars18th
Copy link
Author

Hi @Jalle19 ,

After more thinking on this, I have a different proposal to achieve the same objective.

First, think on this: If we want to preprocess and postprocess the TS, we can use three chained calls. A chained call is when the source URL is a call to the server itself for a different program. For example we can configure /channel1-pre, /channel1 and /channel1-post. Then the "channel1-post" can feed from the "channel1", and that from the "channel1-pre".

So the only requisite to implement this is that we can process the program using another different binary instead of the avconv. In this case, the "channel1-pre" and "channel1-post" will not use the ffmpeg and the result will be the same.

And in order to implement this, perhaps it's sufficient to support another different module than avconv.js. For example, you can provide support for a generic binary (ex generic-child.js). Or to support a simple tool (for example socat.js) and after we can modify the source or copy-and-paste to create a new module.

What you think?

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

No branches or pull requests

2 participants