Choppy video since Krypton update on Vero 1

Most of my h264 mp4 23.976 fps videos (encoded with Handbrake myself), that played absolutely smooth before the Krypton update, now play very choppy (looks like 2 frames per second get skipped) on my Vero 1. I’m using the “adjust refresh rate” and “sync playback to display” features, but even if I turn them off, playback is still choppy.

I think this issue was already reported in a Vero 2 thread, however this is a separate thread vor Vero 1 users as suggested. I can’t watch movies choppy like this, so if there’s no way to fix this I will have to go back to before Krypton I guess.

Can you upload a debug log? I’ll look in to this for you

+1

Are you also +1 to provide a debug log?

ups, thought initial poster had uploaded - here you go:

http://paste.osmc.io/fiqekezumi

have tried different settings for video as well as audio

mediainfo:

Format : Matroska
Format version : Version 4 / Version 2
File size : 15.6 GiB
Duration : 2 h 2 min
Overall bit rate mode : Variable
Overall bit rate : 18.2 Mb/s
Encoded date : UTC 2014-09-03 09:02:54
Writing application : mkvmerge v7.1.0 (‘Good Love’) 32bit built on Jul 27 2014 12:59:18
Writing library : libebml v1.3.0 + libmatroska v1.4.1

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 2 h 2 min
Bit rate mode : Variable
Bit rate : 14.0 Mb/s
Maximum bit rate : 30.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.282
Stream size : 12.0 GiB (77%)
Language : English
Default : Yes
Forced : No

Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Format profile : MA / Core
Mode : 16
Format settings, Endianness : Big
Codec ID : A_DTS
Duration : 2 h 2 min
Bit rate mode : Variable / Constant
Bit rate : 4 184 kb/s / 1 509 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 spf)
Bit depth : 24 bits
Compression mode : Lossless / Lossy
Stream size : 3.57 GiB (23%)
Language : English
Default : Yes
Forced : No

Text
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1 h 55 min
Bit rate : 12.4 kb/s
Count of elements : 2852
Stream size : 10.2 MiB (0%)
Language : English
Default : No
Forced : No

You need to enable debug logging before creating logs.

followed the guide and went into system - logging and enabled
component specific logging
event logging

then rebooted and started playing the file

then proceeded to upload

not sure what else I can do?

Debug logging is just above that point

sorry but this is all i get

debug-log: Vero 1 Kodi Krypton Choppy Playback - Pastebin.com

Try to switch to OSMC skin to enable debug logging

I encoded a small test-file (around 150MB) which plays choppy for me, uploaded it and send the link to Sam via Email. Send me a PM, if you are interested in the link.

settings under osmc skin is the same as under amber - just tried…

Here also these experiences.
After a while video hangs and I even had a crash (bad face).
Looks worse with 1080p.

With Jarvis No problems with content.

+1 on hangs and crash

You’ve probably got it disabled in advancedsettings, this will hide the gui element, see here to enable http://kodi.wiki/view/AdvancedSettings.xml#loglevel

that was it - thanx

new log uploaded:

http://paste.osmc.io/ogefuxebof

Same issue here, uploaded some pastes:

Mediainfo : http://paste.osmc.io/opelavubar.vhdl
Debuglog : http://paste.osmc.io/uvizacutox.vhdl

EDIT: just crashed on me as well :frowning:

I also got crashes in playing a movie last night a few times and one frowny face - never an issue vefore Krypton. Also on a Vero 1.

It just freezes at random points - have to press stop and play again - it’s like the file is corrupted.

1 Like

I’m looking in to this.

Once I can replicate the issue, I’ll let you know.