Closed zhuker closed 4 years ago
also i frequently get something like 2019-05-29 14:45:42 ERROR : [/home/zhukov/ffmpegfs/mummy/scans/R1_235_CC.png] Timeout reading image frame no. 4442: (110) Connection timed out
These are probably actually two bugs. I'll look into it.
The error message is a bit misleading, it is issued when ffmpegfs tries to read past the end of the cache, i.e. an image that is not yet available. That should never happen...
Probably a multi threading problem. How many cores does your machine have? More than 8?
Added a lot of extra logging with these commits:
https://github.com/nschlia/ffmpegfs/commit/60b93c37fb889de87b15922478ffd9ae8e917487 https://github.com/nschlia/ffmpegfs/commit/51065aca310efed3f67901a1d1560325b5aaac8b
The logs should help me to figure out what's wrong. Multi threaded programming is like a box of chocolates. You never know what you're gonna get.
Please run ffmpegfs with --log_maxlevel=INFO to get the whole data. Probably even --log_maxlevel=TRACE would be good, although this may spoil the tests as it logs a whole lotta stuff. INFO should be sufficient, though.
Should be fixed with the new frame set logic.
high bitrate yuv444 h264 wont decode images