Posts by popcornmix

Post a debug enabled log.

By 4k do you mean 4k resolution? That is not supported on Pi.

Post a complete debug enabled log (use a paste site).

Your log does have some Emby compaints.

20:05:56.117 T:1778185120  NOTICE: EMBY.kodimonitor -> Item is invalid for playstate update
20:06:00.323 T:1778185120  NOTICE: EMBY.player -> Could not find itemId, cancelling playback report...

I'd suggest disabling Emby and first test playback of the file locally (e.g. copy to sdcard or locally attached USB stick).
If that is okay then try playing from a network share (without using Emby).

Testing with a clean install may be the best option if you have a spare sdcard.

Not really a RPi3 clone - it won't run any of the same software images.
It is a Rockchip SoC. Kodi has no support for Rockchip, so chances of LE support are low.

Do you have the same issue with recordings from tvheadend? If so then a sample file may be useful.
Otherwise post a debug enabled kodi log.

Post a debug log of you starting a movie.

Quote from MaDi86

I can select the Hifiberry AMP driver and hear the system sound over the Hifiberry. However playing movies I have no sound with the Hifiberry, but only via HDMI output.

Anybody with a similar observation or a hint where to look at?

It sounds like you have enabled passthrough and it is set to HDMI. Try disabling it.

What is Pi connected to for audio (i.e. HDMI or spdif? TV or AVR?)
What are the system/audio settings set to?
Lack of voices is normally caused by setting number of channels to 5.1 when audio equipment only supports 2.0.

I did have a look at some samples from German DVB-T2. It seems they use the following resolutions:
960 x 540/p50 (Quarter HD)
1280 x 720p/p50
1920 x 1080/p50

1920x1080p/p50 will never be possible on a Pi3. You will need something with hardware decode support for this.
1280x720p/p50 should be possible. I think they use weighted B slices which isn't currently GPU accelerated, but could be in theory.
960x540p/p50 should be fine.

If your initial test was positive it probably was using one of the lower resolution streams.

Testing with an ethernet would be useful to narrow the issue down.
In theory stream should stop to buffer and resume when buffer is full, but that assumes data is received without errors (but too slowly).

Your log has read errors in which suggests the network connection dropped, which won't be recovered from.

Yes, power supplies can gradually degrade with time.
You are more likely to observe this if the supply was close to borderline to begin with.

2.5A is normally recommended for a Pi3, but that allows for some USB peripherals - do you have anything connected?

Ideally measure the voltage with a voltmeter, or try with a different supply to confirm the problem.

The ALSA audio driver needs to report passthrough support for kodi to be able to use it.

It is possible to do this through an alsa configuration file. It would like something like this (this is the HifiBerry version)
LibreELEC.tv/HifiberryDigi.conf at master · LibreELEC/LibreELEC.tv · GitHub

But would need device name changed to JustBoom.
You can't write to /usr/share/alsa/cards/ in LE, but I think a file placed in /storage/.config/asound.conf will be used.

It stops because of:

16:57:13 18168.835938 T:1697641376   ERROR: ffmpeg[652FF3A0]: [matroska,webm] Read error
16:57:51 18207.369141 T:1697641376   ERROR: ffmpeg[652FF3A0]: [matroska,webm] Read error
16:58:06 18222.324219 T:1622139808   ERROR: Read - Error( -1, 22, Invalid argument ) - Retrying
16:58:36 18252.328125 T:1622139808   ERROR: Read - Error( -1, 22, Invalid argument )

Now that is some sort of network issue. What is the server you are using?
The fact it works with OE 6.0.3 is surprising. Perhaps some difference in versions of libraries used?
Might be worth trying with a Krypton LE build (7.90.010) just in case the issue is resolved.

Try disabling GPU accelerated resampling in system/audio settings.

Quote

device_tree_overlay=overlays/hifiberry-dac.dtbo
dtoverlay=hifiberry-dac

Remove the first line. The second line is correct.

[ 996.977697] bcm2835-dma 20007000.dma: DMA transfer could not be terminated

is certainly the problem. Can you post the working dmesg log with v7.90.005?

Can you post a debug enabled log file?

Could of options:
Raspberry Pi FAQ - Official Kodi Wiki

Or you can add bootcode_delay=10 to config.txt.

ADSP does not work on either Jarvis or Krypton.
Do not enable it. We need to make sure it is removed by final release of Krypton.

Quote from Gausak

Yes, this option is enabled for me... Disable them?

If you don't want the speed change, then yes.