Brandon Castellano

In the next release, DVR-Scan will ignore these frames. This isn't ideal, but is the quickest solution. To assist with indicating when this happens, I've added warnings when generating output...

Interesting, this is very useful to know. We should definitely look into this some more. I can certainly add a config file option to switch what to use for internal...

The following snippet shows a potential definition for a new timecode type that would support VFR videos as well: ```python class Timestamp: def __init__(self): self._frame_index: int = 0 # Index...

Whenever you pass multiple files to DVR-Scan, it treats them as a single contiguous video. This allows you to combine multiple videos from a single camera angle, while still handling...

I've added a workaround for this in the user guide in v1.6, but will defer adding the flag to v1.7.

Are you sure the framerate is 23.98 exactly? Could you provide a deubg log as well? E.g. add `-v debug --logfile log.txt` to the beginning of your command and attach...

> If I need to be ultra exact, its 23.976, however I was still getting this issue before defining the frame rate as exactly 23.98. The FPS *must* be exact...

> To help with this, I've also done the same test with a video I do have rights to share, converting with the same process as used for the redacted...

> > Do you suspect the issue is related to a specific codec? If so, could you try running using the PyAv backend (add `-b pyav` to the beginning of...

Glad you got the issue sorted out. > as a side note, with the EDL format, would it be possible to enable an argument that allows offsets in the outputted...