Roemer
7th December 2021, 23:33
Hello all
I am using DGIndex to create an index for a Vob file, then process the d2v with Avisynth and in the end, remux everything with ffmpeg.
Now it seems I stumbled uppon a special case where my end-result is slightly out of sync. When I directly convert the whole thing with for example VidCoder/Handbrake, everything is fine.
Uppon further inspection, I found out that the wrong file has around 10 frames more. And uppon even more inspection, I saw that the vob contains two cells or video ids or chapters (no idea to be honest) whereas the second contains the correct video and the first is just a 00:00:00:00.10 long video. When I then create vob file without that first part with DVDDecryptor or with PgcDemux, I get a slightly smaller vob file which is then fully in-sync and also 10 frames shorter.
So is this a case where DGIndex simply cannot be used? I love DGIndex because it's simplicity and CLI functionality.
Many thanks for hints.
I am using DGIndex to create an index for a Vob file, then process the d2v with Avisynth and in the end, remux everything with ffmpeg.
Now it seems I stumbled uppon a special case where my end-result is slightly out of sync. When I directly convert the whole thing with for example VidCoder/Handbrake, everything is fine.
Uppon further inspection, I found out that the wrong file has around 10 frames more. And uppon even more inspection, I saw that the vob contains two cells or video ids or chapters (no idea to be honest) whereas the second contains the correct video and the first is just a 00:00:00:00.10 long video. When I then create vob file without that first part with DVDDecryptor or with PgcDemux, I get a slightly smaller vob file which is then fully in-sync and also 10 frames shorter.
So is this a case where DGIndex simply cannot be used? I love DGIndex because it's simplicity and CLI functionality.
Many thanks for hints.