-
Notifications
You must be signed in to change notification settings - Fork 30
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
Possible improvement? #1
Comments
What do you mean by "parse the output directly from stdout rather than parsing the ffmetadata ini"? The module currently parses the ffmetadata ini output from Support for multiple input files would be great though! I am not sure what the ffmpeg output would look like with multiple |
Yeah, as far as I can tell -f ffmetadata works only on the first input file so the metadata would have to be read directly from the output of ffmpeg (no -f) which would be more difficult to parse. I am not sure what the limit of input files is, but I tested a single album with 20 songs and it was very fast. It would also save the expense of spawning huge numbers of ffmpeg processes while iterating over a large collection. |
Ah ok, I understand now.
Sounds great - I would gladly entertain a patch. |
Do you think it would be possible to parse the output directly from stdout rather than parsing the ffmetadata ini so that multiple input files could be processed with a single instance of ffmpeg?
This would provide a significant performance gain when reading metadata for a large collection, right?
I could probably hack on it if you can't think of any major caveats to this approach.
Ex:
ffmpeg -i 01.mp3 -i 02.mp3 -i 03.mp3..
The text was updated successfully, but these errors were encountered: