Skip to content

FFprobe integration #10

Closed
teamwenger opened this Issue Oct 10, 2012 · 6 comments

2 participants

@teamwenger

Before every transcode session, I need to retrieve info on the source file to determine output settings. It would be efficient to incorporate this function into the codem-transcode package as it could allow for a single system to manage all the transcoding tasks as well as some automated presets based on input file parameters.

There is a handy package already available to retrieve json data from source files which could be added easily into the codem system: https://npmjs.org/package/node-ffprobe

@tieleman
Hiro member

So you would have some endpoint that you can use for retrieving information about a file on the filesystem, something like:

POST /probe

With some additional data:

{
    "source_file": "/PATH/TO/INPUT/FILE.mp4"
}

And you would receive the result of that probe in a JSON-formatted response.

I think that would be a good way to do such a thing. You could then decide what kind of processing presets you want to send to the transcoder.

@teamwenger
@tieleman
Hiro member

Great, I'll whip up a patch.

@tieleman tieleman added a commit that referenced this issue Oct 15, 2012
@tieleman tieleman Added support for ffprobe (Issue #10)
Extra endpoint /probe and extra config option "ffprobe".
28752af
@tieleman
Hiro member

I've pushed a branch containing the new functionality, see:

https://github.com/madebyhiro/codem-transcode/tree/ffprobe

Let me know if this works for you and I'll push a new release. The README is updated, so check that out on how to use the ffprobe functionality.

@tieleman tieleman was assigned Oct 15, 2012
@teamwenger
@tieleman
Hiro member

A new package has been pushed to npm (0.4.1):

https://npmjs.org/package/codem-transcode

@tieleman tieleman closed this Oct 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.