Vero 4k video freeze for 3-5 seconds on last frame after a pause that was longer than 10 seconds

Is there any progress on a fix for this?Something that I could help out to test before it is released?

I purposely waited a few weeks with upgrading to V18 with the intention that minor things like this would surely been ironed out by now. Im aware that it is impossible to forsee everything and that there factors you’re not in control of, but for a stable release running on branded HW with optimized OS this is not impressing.
I can’t believe that a crucial function like pause/unpause that worked before has now become crippled, it is really irritating.

I know Sam is working on various video issues as we speak.

I have an idea on how to fix it but no way of verifying it. I have not been able to produce this issue whatsoever, and I’ve been using v18 for weeks as a daily driver.

I thought someone on the team could reproduce the issue. Can‘t you send him the possible fix?

That’s what I’ve done

Guys what screensaver do you use? It could have something to do with this.

It’s not that. I’m building a fix now.

ok :slight_smile:

WANT. NAO!

1 Like

Hi

Hopefully the issue is now addressed

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Edit the file /etc/apt/sources.list
  3. Add the following line: deb http://apt.osmc.tv stretch-devel main
  4. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  5. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.

Sam

I tried doing this (since I’m experiencing the problem) but upon playback, Kodi crashes. I see what appears to be the refresh rate change but it just comes back with the sad face.

My logs end with:

2019-05-16 20:25:00.963 T:3388957408  NOTICE: Creating InputStream
2019-05-16 20:25:01.280 T:3388957408  NOTICE: Creating Demuxer
2019-05-16 20:25:01.343 T:3388957408  NOTICE: Opening stream: 0 source: 256
2019-05-16 20:25:01.344 T:3388957408  NOTICE: Whitelist search for: width: 1280, height: 720, fps: 23.976, 3D: false
2019-05-16 20:25:01.346 T:3388957408  NOTICE: Display resolution ADJUST : 1920x1080 @ 23.98 - Full Screen (28) (weight: 0.000)
2019-05-16 20:25:01.381 T:4070367232  NOTICE: VideoPlayer: OnLostDisplay received
2019-05-16 20:25:01.382 T:4070367232 WARNING: CDVDMessageQueue(audio)::Put MSGQ_NOT_INITIALIZED
2019-05-16 20:25:01.382 T:4070367232 WARNING: CDVDMessageQueue(video)::Put MSGQ_NOT_INITIALIZED
2019-05-16 20:25:01.675 T:3388957408  NOTICE: CVideoPlayerVideo::OpenStream - Creating codec: 27
2019-05-16 20:25:01.681 T:3388957408  NOTICE: Creating video thread
2019-05-16 20:25:01.681 T:3291423456  NOTICE: running thread: video_thread
2019-05-16 20:25:01.731 T:3388957408  NOTICE: Opening stream: 1 source: 256

I tried 4 times and got 4 crashes. I’m using PlexKodiConnect and playing a file from a PMS. File is H.264/DD+ and I use audio passthrough.

Thankfully I had recorded in my backhistory the changes it made in the upgrade so I reverted back by removing the entry in the sources.list and then

apt install mediacenter-addon-osmc=3.0.671 armv7-libsqlite-osmc=3.21.0-2 vero3-mediacenter-osmc=18.2.0-6 armv7-eventlircd-osmc=1.3.4
apt purge ir-keytable

File plays just fine after this.

I’d need to see a full debug log to have an idea what the issue is.
With any luck other users experience this problem and can provide this.

Sam

Installed the update. Looks like I’m having the same issue with Kodi crashing now on starting any file playback. Ugh.

Sent you a log, Sam.

Just reverted using the above help. Hopefully Sam can solve this one.

You always need to sudo when using apt.

Gah you just beat me to it. I was able to sudo. Thanks.

Sam, you may want to remove that update since it breaks Kodi playback completely.

Where’s the log?

S

It’s in a development repository – not released to the stable repo.