FieldStation42: More Realistic Station Break Positioning using BlackDetect and SilenceDetect
Currently, station breaks are evenly spaced. It would provide a more accurate simulation if natural breakpoints can be detected using FFMPEG’s BlackDetect filter. As a backup (or to validate BlackDetect locations) SilenceDetect could be used to locate silence. These breakpoints should be stored as metadata in the catalog.
Drawbacks: this will likely add considerable time to the catalog build.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 5
- Comments: 22 (8 by maintainers)
No, but I don’t want to re-invent a format if I can help it, so I would prefer to use chapter markers since lots of videos already contain them and there are lots of tools already to create, edit, update and delete them. I’m thinking of doing it in two passes: providing a simple tool to let people detect commercials break spots and put markers in the video (or they can use any existing tools to do the same automatically or manually) and then during scheduling, it will look for chapter markers and use them if that’s how you configure it. So, no change to the catalog and no new formats - just using existing standards.
Perhaps an --update_catalog command instead of --rebuild_catalog? That way, users can opt to scan for updates or do a full rebuild if it is warranted.
I just committed a VERY experimental version of this - it should only be used for testing. Essentially, it lets you specify a directory that you want to scan for break points (it should be a directory already in your catalog) and store them in the db. Then the next time you make a schedule, it will use the break points from the db. There are still lots of pieces to finish on this, but I wanted to merge back with the mainline. Here is the new option:
--break_detectI would push for the data being baked in being optional as I know several people prefer to leave the media files untouched for a varity of reasons. I mount my media files over NFS read only to specifically to ensure nothing gets changed in them. I’m all for using existing standards, so to that end I would suggest using the file format that FFMPEG expects for chapter metadata,
ffmetadata, that you can see documented here: https://ffmpeg.org/ffmpeg-formats.html#metadata