Posts by HiassofT
-
-
A1RFORCE1 also please test with buffermode 1 in advancedsettings.xml as described here RE: Nightly builds Rpi4 Audio passthrough TrueHD/Master HD not working (huge stutter) anymore - you might also get the warnings because your HDD or network share can't keep a sustained data rate (which is a lot more demanding for high-bitrate BR rips).
so long,
Hias
-
A1RFORCE1 please post full pastekodi debug logs -snippets are completely useless and the warnings you posted are rather harmless.
so long,
Hias
-
That's the default configuration of the Intel HDA driver. You can of course create another PCM using the "softvol" plugin - see here for details ALSA project - the C library reference: PCM (digital audio) plugins
In LE use /storage/.config/asound.conf instead of ~/.asoundrc and simply set the slave PCM to the HDMI PCM device you normally use.
so long,
Hias
-
Hopefully someone would come along who can give me any pointers on why amixer has no effects on HDMI sound other than mute and unmute.
The answer is simply that there is no volume control for the IEC958/HDMI outputs. Only the analog outputs have (software) volume control.
so long,
Hias
-
lolek FYI: today's nightly build LibreELEC-RPi4.arm-9.80-nightly-20210226-e12ff43.tar includes the ALSA buffer size change mentioned above.
Please give that a try, if you still get drop-outs and buffer underrun entries in kodi log test with buffermode 1.
so long,
Hias
-
lolek thanks, got your mails, I'm answering here so other users can follow, too:
The buffer underruns ("snd_pcm_writei(-32) Broken pipe" lines in kodi log) are most certainly caused by kod not being able to sustain the data rate of the file.
Kodi requests 200ms audio buffers, but can only get a ~86ms one due to the current defaults in the vc4 driver. As you play the files from local media this means kodi won't use a read buffer/cache, so if the read rate from the drive drops (eg due to seeking etc) you have a higher chance of getting underruns.
Please do the following tests on the current nightly builds:
First try if increasing the audio buffer size helps:
When playing a HD audio file kodi log should now indicate that it could use a 200ms buffer (the "setting timeout..." line)
Code2021-02-25 15:28:49.606 T:941 DEBUG <general>: CAESinkALSA::InitializeHW - Request: periodSize 9600, bufferSize 38400 2021-02-25 15:28:49.610 T:941 DEBUG <general>: CAESinkALSA::InitializeHW - Got: periodSize 9600, bufferSize 38400 2021-02-25 15:28:49.610 T:941 DEBUG <general>: CAESinkALSA::InitializeHW - Setting timeout to 200 msThen try with an advancedsettings.xml file, setting buffermode to 1 (so local files use kodi's cache, too) .
/storage/.kodi/userdata/advancedsettings.xml:
Code<advancedsettings version="1.0"> <cache> <buffermode>1</buffermode> </cache> </advancedsettings>Reboot, so the audio buffer size change is restored back to the default and advancedsettings change take effect and test again.
It could also be that both audio buffer size increase and local buffering are required.
Please let us know which variants work and send me pastekodi logs of the cases where you got audio dropouts / underruns. I'm also still interested in a pastekodi log of a dropout with plain nightly build, wiithout any of the above mentioned changes.
so long,
Hias
-
reefer in case you are using LibreELEC 9.2 - yes, the issue is well known, and no, it won't be fixed in LE 9.2. LE 10 nightly builds don't have the issue.
so long,
Hias
-
The passthrough options in audio settings apply to music as well. But mp3 passthrough isn't supported.
The IEC 61937 series includes standards for MPEG-1, MP3, AAC (and a few other niche formats) passthrough, but I'm not aware of any AVR supporting those formats and it's definitely not implemented/supported in kodi.
so long,
Hias
-
One more question, is there any chance to passthrough the music?
AC3 and DTS music files should just work if you have passthrough enabled. Just checked with an .ac3 file and a WAV containing DTS - kodi log showed that as being passed through.
so long,
Hias
-
Try without /storage/media mounted - if you copied stuff to /storage/media (on the SD card) that won't show up with du -x - as the smb mount is hiding that.
so long,
Hias
-
chook55 there's nothing suspicious in the logs you emailed me and I also couldn't reproduce the issue here.
As I wrote before check your cabling - contact issues, bad cables / adapters are the number one cause of the issues you described. I'd recommend starting with a direct connection from your RPi to your TV, try also a different, known good HDMI cable, leaving the argon case and HDMI splitter out of the chain - they are all potential sources of issues.
so long,
Hias
-
Kodi automatically redacts sensitive information (like username/passwords) in it's log so there's very low risk when uploading them to a paste site.
You can also tell pastekodi to save the info to a file by using the "-c" option - eg pastekodi -c > my.log and then eg send it to me via email [email protected]
so long,
Hias
-
chook55 Just enter "pastekodi" after you reproduced the issue. This should give you an URL - if not (eg if the paste site is overloaded) try again for a second time. Then post the URL here.
so long,
Hias
-
-
hdmi_edid_file won't work on LE10, this was for the legacy (firmware) graphics drivers. With LE10 you have to use the standard linux kernel KMS approach (as used eg on x86 builds).
The info in our wiki only describes how to do this for x86 builds, on RPi you need to use a slightly different approach:
First dump your edid to the firmware/edid directory, name it eg "myedid.bin":
Codemkdir -p /storage/.config/firmware/edid cat /sys/class/drm/card0-HDMI-A-1/edid > /storage/.config/firmware/edid/myedid.binThen create a cpio archive so the file is also available in the very early boot stage:
Codemount -o remount,rw /flash rm -rf /tmp/cpio mkdir -p /tmp/cpio/usr/lib/firmware cp -r /storage/.config/firmware/edid /tmp/cpio/usr/lib/firmware cd /tmp/cpio find usr -print | cpio -ov -H newc > /flash/edid.cpio cd /storage rm -rf /tmp/cpioAdd the following line to /flash/config.txt to load the edid.cpio as an initramfs
And add the following option to the end of /flash/cmdline.txt (in the same line, separated by a space from the options before) to use your myedid.bin file for the first HDMI port:
Then reboot. To verify everything worked fine run "dmesg | grep EDID", you should see the following lines indicating your myedid.bin is used:
CodeLibreELEC:~ # dmesg | grep EDID [ 3.142571] [drm] Got external EDID base block and 1 extension from "edid/myedid.bin" for connector "HDMI-A-1" [ 3.153272] [drm] Got external EDID base block and 1 extension from "edid/myedid.bin" for connector "HDMI-A-1" [ 13.281974] [drm] Got external EDID base block and 1 extension from "edid/myedid.bin" for connector "HDMI-A-1" [ 17.737414] [drm] Got external EDID base block and 1 extension from "edid/myedid.bin" for connector "HDMI-A-1" [ 17.751318] [drm] Got external EDID base block and 1 extension from "edid/myedid.bin" for connector "HDMI-A-1"so long,
Hias
-
Device Stops for 2S every 50S to 80S. Screen blanks and audio stops when playing music. It is occurring on nightly releases 20210218 20200219 and 20210220 and possibly earlier.
The device is a RPi4b with 2GB ram.
Please test with this build LibreELEC-RPi4.arm-9.80-devel-20210205165343-b642f3c.tar
If this has the same issue post debug logs: enable debug logging in kodi, reproduce the issues, then run "pastekodi" via ssh or use the logfile upload function in LibreELEC settings.
Note that screen blanking is often a sign of a bad HDMI cable - especially if you run at 4k resolution. Double-check that and also try running with kodi configured to 1920x1080 (that should work even with crappy HDMI cables).
so long,
Hias
-