The image is abnormal when playing fMP4 video

[chAlices]

Hey guys

I got a fmp4 video which was generated by ffmpeg. And the video format is hevc.

When I play it with windows ver. VLC media player and seek to any frame, the picture is abnormal. If you continue playing for a while, the image will return to normal.
It seems that the seek operation landed on a non-key frame, due to the lack of reference frames during decoding. So, the resulting image is abnormal.
But it's strange that VLC player on Mac do not have this issue.

My VLC player version of windows is 3.0.21 Vetinari. And here is the detail of this fMP4 video:

General
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso6/iso2/mp41)
Duration : 12 s 928 ms
Overall bit rate : 40.1 Mb/s
Frame rate : 59.940 FPS
Writing application : Lavf60.18.100

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L5.2@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 12 s 913 ms
Bit rate : 39.8 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.321
Stream size : 61.3 MiB (99%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : hvcC

[Lotesdelere]

Please open Tools -> Messages (set Verbosity to 2) before you start the playback, and then paste the full resulting log here or on Pastebin.com or on Justpaste.it if it's too long.

Also upload a short sample of your original problematic file to WeTransfer.com or Disroot.org and then post the link to the file here.
https://wetransfer.com
https://upload.disroot.org

If needed cut it with DGsplit and read here about how to do it:
https://forum.videolan.org/viewtopic.ph ... 35#p193335
200 MB max should be enough but a full complete short file is better.

[chAlices]

Please open Tools -> Messages (set Verbosity to 2) before you start the playback, and then paste the full resulting log here or on Pastebin.com or on Justpaste.it if it's too long.

Also upload a short sample of your original problematic file to WeTransfer.com or Disroot.org and then post the link to the file here.
https://wetransfer.com
https://upload.disroot.org

If needed cut it with DGsplit and read here about how to do it:
https://forum.videolan.org/viewtopic.ph ... 35#p193335
200 MB max should be enough but a full complete short file is better.

Please check this: https://we.tl/H0s1p59rRV
I uploaded the source fMP4 video and an 'error.log'. I also uploaded a screenshot as soon as I perform a 'seek' operation.
Thanks for your help!

[Lotesdelere]

Your log is not the whole full log from the very beginning to the very end that we need.
That said, I think there are known issues with Intel Graphics maybe because they are using shared memory rather than dedicated video memory.

Code: Select all

avcodec info: Using D3D11VA (Intel(R) UHD Graphics 630, vendor 8086(Intel), device 9bc5, revision 5) for hardware decoding main error: Timestamp conversion failed for 6239567: no reference clock main error: Could not convert timestamp 0 for FFmpeg main error: Timestamp conversion failed (delay 1000000, buffering 100000, bound 3000000) main error: Could not convert timestamp 620992644857 for faad main error: Timestamp conversion failed for 9142467: no reference clock

[chAlices]

Your log is not the whole full log from the very beginning to the very end that we need.
That said, I think there are known issues with Intel Graphics maybe because they are using shared memory rather than dedicated video memory.

Code: Select all

avcodec info: Using D3D11VA (Intel(R) UHD Graphics 630, vendor 8086(Intel), device 9bc5, revision 5) for hardware decoding main error: Timestamp conversion failed for 6239567: no reference clock main error: Could not convert timestamp 0 for FFmpeg main error: Timestamp conversion failed (delay 1000000, buffering 100000, bound 3000000) main error: Could not convert timestamp 620992644857 for faad main error: Timestamp conversion failed for 9142467: no reference clock

Sry I set Verbosity to 2 and dump a debug log again.
https://we.tl/H0s1p59rRV
If that's related to Intel Graphics, can I use software decoding instead of the Intel hardware acceleration? Will the output be normal? I tried but seems still failed.

[Lotesdelere]

The log is still not complete, as I said you need to open the messages window before you start the playback and to keep it open during the whole process.
That said, in this new debug log it looks like you're trying to play a live stream and you can't seek a live stream.

[chAlices]

The log is still not complete, as I said you need to open the messages window before you start the playback and to keep it open during the whole process.
That said, in this new debug log it looks like you're trying to play a live stream and you can't seek a live stream.

OK, I updated a new one. https://we.tl/H0s1p59rRV

[Lotesdelere]

"Failed to download file"
Other files are downloading fine though.

[chAlices]

plz try again. I updated a new one. You can also replay the fMP4 in your env.
https://we.tl/H0s1p59rRV

[Lotesdelere]

What is drive N: ? An USB drive ? A network drive ?
Can you copy the file on a local drive and check if the problem still occurs ?

Code: Select all

avcodec info: Using D3D11VA (Intel(R) UHD Graphics 630, vendor 8086(Intel), device 9bc5, revision 5) for hardware decoding

And again, I believe there are known issues with HEVC and Intel on-board cards.

[chAlices]

Drive N just a local drive on my PC.
As I said before, I changed a 'general MP4' to fMP4 file using ffmpeg and did not do the secondary encoding for the hevc stream. I also upload the original MP4 to wetransfer. https://we.tl/H0s1p59rRV

FYR the ffmpeg command is:
ffmpeg -i input.mp4 -c copy -movflags frag_keyframe+empty_moov output.mp4

When I replay the general MP4 and seek, the VLC output is normal. But for fMP4 is abnormal. So I believe this is not just an issue with Intel's HEVC decoding, but there also may be a issue with VLC playing fMP4.