as I said, the same file that one time causes the problem, plays fine the next time.
That was one of the reasons I didn’t want to send the initial grab-logs (besides it containing IMHO a lot of sensitive informatiton like IP-addresses etc…). It contains a lot of cruft. I sifted through the log-file and provided the line that occurred at the time of the problem.
IP addresses should actually be local (not sensitive) to your subnet.
As for scene releases (if present); if you are concerned about that, we don’t care. We are interested in solving potential playback issues across all sources of media.
Feel free to PM me a link to logs. I’m the only one that can access https://paste.osmc.tv pastes directly; and even then I cannot tie it to an individual unless they give me a link to the paste. Pastes are deleted after 30 days.
We should update the Wiki to document how to enable debugging without activating the overlay. This is also covered by the Kodi wiki; so we could provide a link to that instead.
I have done that but did not switch off the component specific debugging. I thought I was logging less because I had activated only a limited set of components. I’ve switched off the component specific logging. Next time the problem occurs I will upload new logs.
Just want to let you guys know I have the exact same issue. Occasionally (like once every 2 files I play) and usually only once during the movie/episode (at a random time).
The only thing (mind you I didn’t change any loglevels or so) I find in the kodi log is:
19:18:12.664 T:3126797296 NOTICE: CVideoPlayerAudio::Process - stream stalled
Do you have enough information from nrosier to try and find out what’s happening? Or do you need logs from me as well?
As for a workaround I use is to just wait until it syncs automatically again (usually after about 5 to 10 seconds) and then rewind back to where I was. Of course it’s not a nice thing to encounter when I’m in the middle of an exciting scene.
(This, and the stuttering in certain video’s while the camera is panning are the only real issue I currently have with the Vero 4K)
@sam_nazarko analyzed one of the files and said it was a bad encoding (frame rate changes in the file). I’m not entirely convinced this is the issue as I’ve had several files from several sources all showing this issue.
This happened again last evening twice during the same movie:
21:00:42.250 T:3126797296 NOTICE: CVideoPlayerAudio::Process - stream stalled
for the second time during the same movie I don’t see any record in the kodi.log
Mediainfo:
General
Unique ID : 221232641803760937280796082225041146356 (0xA66FDB613E77878D933E4837B89481F4)
Complete name : xqz.1080p.bluray.x264.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 8.74 GiB
Duration : 2 h 6 min
Overall bit rate : 9 908 kb/s
Encoded date : UTC 2017-07-25 19:51:53
Writing application : mkvmerge v8.5.2 (‘DiAMOND’) 64bit
Writing library : libebml v1.3.3 + libmatroska v1.4.4
Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Format settings, Endianness : Big
Codec ID : A_AC3
Duration : 2 h 6 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 spf)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 578 MiB (6%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No
Text #1
ID : 3
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Title : English regular
Language : English
Default : No
Forced : No
Text #2
ID : 4
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Title : English sdh
Language : English
Default : No
Forced : No
I was trying to think why @Vince35 and I are having this problems and nobody else is reporting them. Then I remembered we both use hyperion. For HEVC support in hyperion I needed to set following: echo 1 > /sys/module/amvdec_h265/parameters/double_write_mode
I switched it off and for the last hour I haven’t had any problems where as I had the problem twice in 30 minutes before. Still need some testing to make sure but it could be worth investigating.
Strangely enough the files I’m wattching are h264 and this parameter appears to be h265 specific.