I’ve just upgraded to the latest Kodi/OSMC version on my Vero 4K+ and I now have 2 issues which I didn’t have on the version just before this:
in an ISO BluRay I have multiple audio tracks, one 6 channel which it selects by default and an 8 channel TrueHD one, which I want to switch to, but instead of switching the audio doesn’t change, the screen displayed it does. It also has 4 other 6 channel tracks, those can’t be switched to either. It worked on the previous version just before. - switching in other eg. mkv files it works fine. I’m using NFS to my file sever to connect. Looks like it only happens if I don’t start from the beginning of the ISO, so as a workaround, start from the beginning, then seek to where you left off. Log: https://paste2.org/L2cwkKDA at around 2:02 - mediainfo inside the mounted ISO: https://paste2.org/AwKzsNxF
when seeking in certain videos (eg. +10s/+30s jump, forwards or backwards), most of the time I get still screen, but the audio continues. As a workaround, if I seek the opposite direction, it eventually starts working. I also see this issue on HTTP network streams too, not just NFS. I didn’t have this issue with the previous version. - Logs at around 2:05 in the above linked file - mediainfo: https://paste2.org/Ptf07vew
-Can you please help with these issues? What (debug) logs would you need?-
Just a standard upload of debug logs would be great, but please keep in mind that Vero 4K / 4K+ support has now ended with regards to software updates.
Same behavior when seeking here. The playback does eventually recover, but it just hangs for several seconds while audio playback continues. It does not happen consistently on every skip, some are fine.
Without component-specific debugging, this " waiting for keyframe" message seems to be the last message before a “hang”:
The linked log has component-specific logging for video enabled. The way I captured this: started the file playback, did skips until I hit one that got stuck, waited until playback resumed, then hit ctrl+c on the log capture to stop it, so the relevant information should still be somewhat close to the bottom of the file. I hope that’s condensed enough, this log level is very verbose and a bit hard to capture.
Sorry, but that’s not the full log. For instance, I miss the information about installed packages and their versions. Without that information we can’t tell you if all the packages are up-to-date on your device. Or if there were any errors during installationg etc.
I have the same issue on the Vero V after the March upgrade. A chapter skip results in the video freezing for 5 to 6 secs, while the audio continues fine.
Adding up here as well, just wanted to open a thread and stumbled across this one.
Also since March update on Vero V seeking forward and backward produces the video to freeze for 5 to 10 seconds while audio already starts playing back normal almost instantly…
discovered this seeking issue myself, but I only just got my first Vero so figured it’s just how it is.
I resolved the issue on the show I am currently encoding by reducing keyint=250 (which is the default in x264 and x265) to keyint=96.
I noticed 96 is what HBO uses (one of the few platforms that leave their encode settings in the video metadata).
Of course I have hundreds of videos with the default keyint=250 so my workaround is informative but not particularly helpful.
Same here, we are experiencing image freeze sometimes after using the seek 10s, 30s function, but sound continues. I didn’t got this kind of issues before so I was pointing out the latest update from March.
Edit: after quick analysis, there are more freeze chances when doing a seek10s at the end of a video. It looks like a buffer issue, and as sound get another buffer than images… disynchronisation between sound and image ?
I am having this same issue on multiple Vero 5 devices with different TVs. None of the files that I’m having the issue with had the issue before the March update. One commonality I’ve noticed is they all have Dolby audio.
