I’ve got several series of a show which will not play on the Vero 4K correctly.
Audio is heard then at intervals audio drops off and you get video for around 0.5 seconds instead.
I’ve given a link to a sample I cut.
Issue with Vero 4k+ with latest Leia. But I reset to default today (Krypton) and have same issue.
Plays fine with i386 on Krypton (CPU decode). And also Fire tv 4k stick Leia RC1.
In kodi.log I get:
NOTICE: CVideoPlayerAudio::Process - stream stalled
I’ve not given logs, as I think this should be easily reproducible with the sample.
I suspect it’s with the GPU Vero uses. If so not really a Vero issue. Sorry if I should be asking over in Kodi forumn, but you guys are the best
I had hoped someone would have tried to reproduce the issue.
Playback is over the LAN. I can play 50Gb+ files, so this tiddler is not an issue.
Played the above sample with debug enabled: https://paste.osmc.tv/ifoqukexaf
The sample doesn’t terminate correctly, but up until the end has same issues as the full thing.
Changed /sys/module/amvdec_h265/parameters/dynamic_buf_num_margin from 12 to 16.
Works ok for 20 secs, then issues for another min or so. Then it it plays ok.
It would help to know the full encoding parameters that include things like references, because if the reference count isn’t extra high, the profile (Main@L5.1) is more than is needed for the video. It should be Main@L4.0 based solely on the resolution and frame rate.
More references mean more stored frames in memory to refer to, which means more memory allocation. If the extra memory requirements are close to the limit of the chip, it could cause issues with playback. But, if the video doesn’t actually need it, then it’s just a waste.
There are free or moderately priced tools to fix this kind of thing with H.264 streams, but I don’t know of any for H.265 streams.
Handbrake does h.265 now. Personally I would stick with h.264 for HD content as there is not a very big difference in file size for the same video quality, but there is a big difference in encode speed.
I was talking about tools like VideoRedo, which can fix errors in an H.264 bitstream without re-encoding. This includes fixing metadata like the profile and level that that are stored in the bitstream. The newest version of VideoRedo does support H.265, but it’s still in beta, and still pretty buggy.