Posts by popcornmix

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.

Quote from Gausak

Can anybody help me?

Do you have sync playback to display enabled?
That would cause 24fps video to be sped up to 25fps to maintain smooth video on 50Hz display.

There have been some changes with how kodi passes URL parameters through ffmpeg in Krypton.
Probably best to post here: Kodi Community Forum - VideoPlayer Development
including description and debug log where the right dev may know what to do.

Your system is obviously very broken. I'm suspecting power supply issues but it's hard to tell if it doesn't run long enough to get debug output.

You have a few not standard devices. Can you try removing the HifiBerry and the wifi (and using the ethernet connection), and we'll try to debug the display.
Report output of "tvservice -s" when the display blanks (if it still does).

After the screen has faded through ssh can you report output of:
vcgencmd get_throttled
tvservice -s
dmesg

Do you have any hardware plugged in? e.g USB or "HAT" boards?
Do you have any custom settings in cmdline.txt or config.txt?

Quote from donquijote

Thanks, i delete the Textures13.db file and now its working fine

If you delete Textures13.db then you should also delete .kodi/userdata/Thumbnails (at the same time) or you'll end up with orphaned thumbnails that are never used but waste disk space.

See also: [RELEASE] Texture Cache Maintenance utility

Audio-to-video synchronization - Wikipedia
"ITU performed strictly controlled tests with expert viewers and found that the threshold for detectability is -125ms to +45ms."

I really don't believe you can detect offsets smaller than 25ms.