I think you can rule out excessive memory use as a cause of your problem.
It’s very hard to make anything out of that log file as its extremely long, so without knowing exactly what time the problem occurs (relative to the timestamps in the file) it’s like searching for a needle in a haystack.
Could you reproduce the stall problem just once and take a note of the exact time that the stall occurred and the exact time that it recovered and include those times when you post the log ?
Also I may have missed it as I have only skimmed the thread, but where are the files playing from, or is it a stream ?
ok, will do on Sunday. I’m playing the files from a USB hard disk.
Also, I looked through the log myself and I think I have possibly found the point when the audio drops out completely as the highlighted comments don’t appear before this point…
@ntate6630 I have seen your issue. With enough starting and stopping creating the audio stream can hang, and that needs kodi to be restarted to fix. It is not a memory issue.
I don’t think it is the issue others have reported. This issue only occurs on start of stream - I don’t believe it will occur in the middle of video playback.
The alsa sink doesn’t have this issue. While not generally recommended, I’d be interested if you can try that and confirm you get the same behaviour. You’ll want “dtparam=audio=on” in config.txt (I believe that is a default), and make sure snd-bcm2835 is not blacklisted in /etc/modprobe.d. You should then be able to launch kodi and choose the alsa device in system/audio settings.
I do have a potential fix for this. It works but it’s not the right fix - I really need a colleague to look into the underlying cause and it’s next on his list.
Set “dtparam=audio=on” in config.txt. Previously I had it set to “off” because of an issue that came up with the January update… (January update now iqaudio dac not working? - #16 by ntate6630)
…and was expecting the sound to go back to the HDMI instead of “IQaudIO PiDAC +” but it didn’t change.
There is no blacklist.conf file in /etc/modprobe.d so nothing to edit in nano so im assuming that means “snd-bcm2835” wont be blacklisted.
Next I rebooted with logging turned on, opened terminal, started TOP, took a screen shot at time “21:45” before any videos were played… This was the same as before so didn’t feel the need to post it here again unless anyone wants it.
Next I play various videos on my USB hardisk, also fast forward, play, stop, change video, play, fast forward, stop etc. until the occurrence of the sound dropping out again which I can confirm the sound does drop out and the videos freeze again. The video starts playing with no sound after several seconds and if I stop a video it takes several seconds again before returning to the movie selection screen instead of instantly.
I took another screen shot of TOP at time “22:12” similar result as before so no need to upload here unless anyone wants it… “RES” was “96032” at this point.
It seems to be working OK for now as I haven’t had the sound drop out yet or any video freezes but will need more testing for longer duration of time to confirm its better. I will try again on Sunday.
I haven’t given up on finding the issue, but unfortunately there has been a lot of ‘noise’ / +1s in this thread and it’s made it tricky to work out what the issue may be.
The kernel remains unbumped from 4.4.1, but it may be worth trying the updated Kodi build to see if anything has improved. However for those experiencing issues with USB drives, I suspect it won’t make a difference
As far as I’m concerned, I’ve been using the updated kernel since its release a week ago, and the “random muting then freezing” has vanished for me (so far).
It only happens now if I set the GPU resample method to GPU instead of medium in system/audio settings. I will still use the GPU setting for audio only playback which has no problems at all. It would be great to have the GPU setting work properly for video because the audio quality is greatly improved in all cases, but maybe that’s a lesser priority at the moment.
Hi Sam
I can confirm (after a few days of testing), that new version with final Kodi 16 is much better for my case with USB drives. The increasing of RES is very very slowly.
Thank you very much for this version.
Regarding support of HEVC codec I tested a few files (also 720p), but without succes - no picture, only sound.
Do you have some sample file with HEVC codec which working on RPi2?
Thanks
Jan
Hlavní
Unique ID : 240836847870637196474175391342571019882 (0xB52F7D5D261E03D7BE43C1995D47DE6A)
Complete name : Z:\Downloads\TearsOfSteel_720p_h265.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 101 MiB
Duration : 12mn 14s
Overall bit rate : 1 153 Kbps
Encoded date : UTC 2013-09-04 21:15:18
Writing application : mkvmerge v6.2.0 ('Promised Land Rovi v1.0.4') built on Aug 29 2013 13:59:38
Writing library : libebml v1.3.0 + libmatroska v1.4.0
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L6.2@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 12mn 14s
Width : 1 280pixely
Height : 720pixely
Display aspect ratio : 16:9
Frame rate : 24,000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Default : Ano
Forced : Ne
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : A_AAC
Duration : 12mn 14s
Channel(s) : 6 kanály
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48,0 KHz
Default : Ano
Forced : Ne
I tested the updated OSMC with Kodi 16 and had the freeze happening on the 3rd evening, the two evenings before, everything went well. So, this still is unresolved, although something might have lead to it showing up less frequently.
The audio resampling had been set to GPU.
Hartmut
Same for me, I tried disabling CEC and adjusting the display rate, but it did not work. Only setting the audio resampling to anything other than GPU fixed it!
I have the model B and it was freezing every ~20 minutes in both OSMC and OpenELEC, with fresh installs, no addons and playing from USB. Setting the audio resampling to High fixed it. Maybe the bug isn’t due to OSMC at all, then. Could it be caused by changes in Kodi or in the underlying OS (raspbian?) ?
