You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merli1-2.avi.2023-08-27-20-23-48.tar.gz
--apply-offset-seconds does not seem to function as expected. E.g., I set it to 107, i.e., 1 minute and 47 seconds, and the subtitles begin syncing to 1 minute and 37 seconds.
The video file begins with a review of the last episode, while the subtitle file ignores the dialogue in the review. I noted that the actual dialogue which corresponds to the subtitle file begins at 1 minute and 47 seconds, and therefore thought the --apply-offset-seconds would begin syncing from this point on, but it does not seem to function this way.
The text was updated successfully, but these errors were encountered:
spirited1086
changed the title
--apply-offset-seconds not applying set argument
--apply-offset-seconds not applying set argument of 107 seconds
Aug 28, 2023
Also, this can be fixed easily by using another program to manually offset the subtitles by the correct amount and then running ffsubsync while omitting parameter --apply-offset-seconds. In this case all I did was use an external program to offset the subtitles by +105 seconds instead of +107 (the original subtitle file begins at the ~2 second mark) then run the standard ffsubsync file.avi -i subtitle.srt -o subtitle.s.srt.
Merli1-2.avi.2023-08-27-20-23-48.tar.gz
--apply-offset-seconds does not seem to function as expected. E.g., I set it to 107, i.e., 1 minute and 47 seconds, and the subtitles begin syncing to 1 minute and 37 seconds.
The video file begins with a review of the last episode, while the subtitle file ignores the dialogue in the review. I noted that the actual dialogue which corresponds to the subtitle file begins at 1 minute and 47 seconds, and therefore thought the --apply-offset-seconds would begin syncing from this point on, but it does not seem to function this way.
The text was updated successfully, but these errors were encountered: