Many failed conversions with no info in log

Free all in one audio/video ffmpeg batch encoder

Brought to you by: eibol

Many failed conversions with no info in log

Forum: General Discussion

Creator: Ronald J Kienle

Created: 2022-01-31

Updated: 2022-02-02

Ronald J Kienle - 2022-01-31

I have been experiencing many failures lately on files I recorded a long time ago and are just sitting on hard drives waiting to be encoded. When I try to encode files recorded from the MGMHD channel over 75% of them fail but upon reading the log file it simply says "failed" with no information as to why.

Is there any way to get more info? Can I make ffmpeg write it's own log? Something in my parameters may be causing the issue but I cannot tell as the log tells me nothing.

I have a log file attatched....simply delete the appended .mgm and it is readable. I realize there is noting in there but someone may have some insight

Any help would be appreciated

Thanks

Last edit: Ronald J Kienle 2022-01-31

ff_batch.log

ff_batch.log.mgm

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abel - 2022-02-01

Hi, you can enable in settings "more verbose logs", so you will have the full ffmpeg log available for you to check.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2022-02-01

Thanks Abel, I will do that when this batch finishes.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2022-02-01

I just tried that and the log has more information but it still doesn't tell me why these files are failing. Any ideas Abel?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2022-02-01

It is an issue with my ffmpeg parameters. For some reason on SOME files if I have -rc-lookahead set to anything about 0 the encoding fails.

Any insight on that Abel?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2022-02-01

I think it is a time stamp issue....which are not needed anyway. If I demux with ProjectX (because it repairs issues while others result in out of sync audio) and remux with tsMuxer then the files encode properly.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abel - 2022-02-01

Hi, I was thinking that being transport stream files, there could be some glitch, or as you say some incoherent timestamps and ffmpeg would not expect it and throw an error.

Regarding the lookahead issue, no idea about it. Maybe you could update your drivers.
https://forums.developer.nvidia.com/t/seg-fault-with-ffmpeg-when-using-rc-lookahead-0/69522/8

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2022-02-01

Demuxing with ProjectX fixes the errors in the files so once they are remuxed with tsMuxer they encode fine with my settings.

But all my files fail if I try the latest build of ffmpeg 5

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abel - 2022-02-02

No clue about that. If ffmpeg 5 does not bring significant advantage, I would stick to v4.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.