[8.0.2e] LibreELEC 8.0 for S905/S905X

You'll find people are more likely to look at your log if you stick it on a paste site rather than expect them to download and open a zip.

Oh well...if it is such a chore, never mind...

Tested beta5b this evening with DVB-S2 streams, blu-ray backups and a lot of misc media files. Found no regression, but somehow that one blu-ray backup which used to have some weird problems with chapter skipping (like showing a few seconds of the video stream just before the chapter mark, but with no sound) played fine for the first time.

How are you guys testing 23.976hz playback? Sometimes I'll notice little jumps in the cadence of panning scenes etc, as if frames are skipped or there is a short lag, but I wonder if its my imagination, or an anomaly with the source itself, because I find its quite a difficult thing to spot for certain.

With that in mind I found here that the Kodi project has provided some 23.976 testcard footage:
FPS_test_1080p23.976_L4.1.mkv - Google Drive
(Source: Samples - Official Kodi Wiki)

But even with this I find it hard to tell for sure, either way (watching in todays beta5b build). My eyes are no good lol. What do you guys think watching this on beta5b? My box is S905 FWIW (Mini MX 2G).
As ever thanks to kszaq for all the hard work and heavy lifting.

Quote from RowanDDR

How are you guys testing 23.976hz playback? Sometimes I'll notice little jumps in the cadence of panning scenes etc, as if frames are skipped or there is a short lag, but I wonder if its my imagination, or an anomaly with the source itself, because I find its quite a difficult thing to spot for certain.

I sometimes get this feeling too, but it only seems to happen at the start of a video. After a minute or so of watching the jumps seem to disappear and everything looks smooth.

Quote from kszaq

I have uploaded 7.95.beta5b build with some experimental changes:

5b seems to handle the 4K material that I have a lot better thanks!

Unfortunately I don't have a box with Gbit ethernet, so I'm using a USB Gbit adapter which reaches speeds of about 200 Mbit with iperf.

This seems enough to play for example the webrips of "a certain car show" that didn't play very well on the previous beta.

Quote from RowanDDR

How are you guys testing 23.976hz playback? Sometimes I'll notice little jumps in the cadence of panning scenes etc, as if frames are skipped or there is a short lag, but I wonder if its my imagination, or an anomaly with the source itself, because I find its quite a difficult thing to spot for certain.

With that in mind I found here that the Kodi project has provided some 23.976 testcard footage:
FPS_test_1080p23.976_L4.1.mkv - Google Drive
(Source: Samples - Official Kodi Wiki)

But even with this I find it hard to tell for sure, either way (watching in todays beta5b build). My eyes are no good lol. What do you guys think watching this on beta5b? My box is S905 FWIW (Mini MX 2G).
As ever thanks to kszaq for all the hard work and heavy lifting.

I noticed the same thing with 2 episodes - and it is repeating the entire video.

Quote from RowanDDR

How are you guys testing 23.976hz playback? Sometimes I'll notice little jumps in the cadence of panning scenes etc, as if frames are skipped or there is a short lag, but I wonder if its my imagination, or an anomaly with the source itself, because I find its quite a difficult thing to spot for certain.

With that in mind I found here that the Kodi project has provided some 23.976 testcard footage:
FPS_test_1080p23.976_L4.1.mkv - Google Drive
(Source: Samples - Official Kodi Wiki)

But even with this I find it hard to tell for sure, either way (watching in todays beta5b build). My eyes are no good lol. What do you guys think watching this on beta5b? My box is S905 FWIW (Mini MX 2G).
As ever thanks to kszaq for all the hard work and heavy lifting.

I am reporting the same problem ... but no one answers me ... I thought succedese just me ... there are small picture shots during video playback to 23,976 hz

Lets not forget that it is already a "known issue" that was recently added to OP:

• fractional frame rates are not fully working (frame jumps)

I think I misread the beta5b changelog, thinking this was "fixed", but thats another issue that is referred to ("removed waiting for a key frame in Amlogic decoder to fix some unplayable samples"). Whoops!

Quote from MrMagic

I sometimes get this feeling too, but it only seems to happen at the start of a video. After a minute or so of watching the jumps seem to disappear and everything looks smooth.

5b seems to handle the 4K material that I have a lot better thanks!

Unfortunately I don't have a box with Gbit ethernet, so I'm using a USB Gbit adapter which reaches speeds of about 200 Mbit with iperf.

This seems enough to play for example the webrips of "a certain car show" that didn't play very well on the previous beta.

What's your internet speed ? I have 40 Mbps speed but all my 4K streams stutters after 5 mins and the video bitrates were between 60-90 mbits, please share your thoughts

Sent from my iPhone using Tapatalk

Quote from RowanDDR

How are you guys testing 23.976hz playback? Sometimes I'll notice little jumps in the cadence of panning scenes etc, as if frames are skipped or there is a short lag, but I wonder if its my imagination, or an anomaly with the source itself, because I find its quite a difficult thing to spot for certain.

With that in mind I found here that the Kodi project has provided some 23.976 testcard footage:
FPS_test_1080p23.976_L4.1.mkv - Google Drive
(Source: Samples - Official Kodi Wiki)

But even with this I find it hard to tell for sure, either way (watching in todays beta5b build). My eyes are no good lol. What do you guys think watching this on beta5b? My box is S905 FWIW (Mini MX 2G).
As ever thanks to kszaq for all the hard work and heavy lifting.

Confirmed, like an imagination. Tested with 2 movies.

kszaq beta5b solved my issue with am-h264 hardware decoding, thanks!

Quote from TheLegendOfMart

My tuner isn't working in the latest version, I know some tuners aren't working I'm just showing which one it is.

2017-02-05 08:05:53.000 linuxdvb: Silicon Labs Si2168 : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]

It's an August T210 that uses Geniatech T230 drivers Geniatech T230 - LinuxTVWiki

I've got same issue with latest build:

2017-02-06 13:13:46.692 mpegts: 658MHz in dvbt - tuning on Realtek RTL2832 (DVB-T) : DVB-T #0
2017-02-06 13:13:46.693 linuxdvb: Realtek RTL2832 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
2017-02-06 13:13:46.693 mpegts: 522MHz in dvbt - tuning on Realtek RTL2832 (DVB-T) : DVB-T #0
2017-02-06 13:13:46.693 linuxdvb: Realtek RTL2832 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
2017-02-06 13:13:46.693 mpegts: 754MHz in dvbt - tuning on Realtek RTL2832 (DVB-T) : DVB-T #0
2017-02-06 13:13:46.693 linuxdvb: Realtek RTL2832 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]

but I can with w_scan scan channels:

##############################################
#                 LibreELEC                  #
#            http://libreelec.tv             #
##############################################


LibreELEC (community) Version: 7.95.beta5
LibreELEC git: 9a197f4ea5fcba5fa939f950fd5fa93f075e1b59
LibreELEC:~ # systemctl stop service.tvheadend42.service
LibreELEC:~ # /storage/w_scan -!v -ft
/storage/w_scan -!v -ft 
w_scan version 20161022 (compiled for DVB API 5.10)
WARNING: could not guess your country. Falling back to 'DE'
guessing country 'DE', use -c <country> to override
using settings for GERMANY
DVB aerial
DVB-T Europe
scan type TERRESTRIAL, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
   check Realtek RTL2832 (DVB-T):
           DVB-T
        /dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Realtek RTL2832 (DVB-T)": good :-)
Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.10
frontend 'Realtek RTL2832 (DVB-T)' supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
BANDWIDTH_AUTO not supported, trying 6/7/8 MHz.
FREQ (174.00MHz ... 862.00MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
   check Realtek RTL2832 (DVB-T):
           DVB-T
Scanning DVB-T...
Scanning 8MHz frequencies...
474000: (time: 00:00.810) 
482000: (time: 00:03.030) 
490000: (time: 00:05.160) 
498000: (time: 00:07.290) 
506000: (time: 00:09.420) 
514000: (time: 00:11.550) 
        (0.900sec): SC (0x7)
        (0.900sec) signal
522000: (time: 00:12.510) 
        (0.880sec): SC (0x7)
        (0.880sec) signal
        (0.950sec): SCL (0x1F)
        (0.950sec) lock
        signal ok:      QAM_AUTO f = 522000 kHz I999B8C999D999T999G999Y999 (0:0:0)
        initial PAT lookup..
read_sections: count2: 32
PAT for transport_stream_id 259 (0x0103)
PAT (xxxx:xxxx:259)
        ===================== parse_pat ========================================
        len = 20
        0x00: 00 00 E0 10 0B B9 EC 1D 0B BA EC 81 0B BB EC E5 :                 
        0x10: 0B BC ED 49                                     :    I
        ========================================================================
        QAM_AUTO f = 522000 kHz I999B8C999D999T999G999Y999 (0:0:0) : updating transport_stream_id: -> (0:0:259)
          check_duplicate_transponders()
          ================= list_transponders() =======================
          new_transponders(000): QAM_AUTO f = 522000 kHz I999B8C999D999T999G999Y999 (0:0:259)
          =============================================================
        initial NIT lookup..
read_sections: count2: 59
NIT(act): (xxxx:12290:xxxx)
        ===================== parse_nit ========================================
        len = 47
        0x00: F0 0A 40 08 54 6F 77 65 72 63 6F 6D F0 21 01 03 :   @ Towercom !  
        0x10: 22 BF F0 1B 41 0C 0B B9 01 0B BA 01 0B BB 01 0B : "   A           
        0x20: BC 01 5A 0B 04 7E 83 40 1F 81 1A FF FF FF FF    :   Z  ~ @       
        ========================================================================
        QAM_AUTO f = 522000 kHz I999B8C999D999T999G999Y999 (0:0:259) : updating network_id -> (0:12290:259)
          check_duplicate_transponders()
          ================= list_transponders() =======================
          new_transponders(000): QAM_AUTO f = 522000 kHz I999B8C999D999T999G999Y999 (0:12290:259)
          =============================================================
        ----------------------------------------------------------
        NIT(act): (8895:12290:259)
        ===================== parse_terrestrial_delivery_system_descriptor =====
        len = 11
        0x00: 04 7E 83 40 1F 81 1A FF FF FF FF                :  ~ @       
        ========================================================================
          F754000 B8 M64 C23 D999 G4 T8 other_frequency=0 (0)
          0 cells
        find_transponder(8895:12290:259):          -> not found.
        find_transponder_by_freq(QAM_64   f = 754000 kHz I999B8C23D0T8G4Y0 (8895:12290:259))          -> not found.
        find_transponder_by_freq(QAM_64   f = 754000 kHz I999B8C23D0T8G4Y0 (8895:12290:259))          -> not found.
        new transponder: (QAM_64   f = 754000 kHz I999B8C23D0T8G4Y0 (8895:12290:259)) 0x405A
          check_duplicate_transponders()
          DELETING DUPLICATE TRANSPONDER new_transponders(001): QAM_64   f = 754000 kHz I999B8C23D0T8G4Y0 (8895:12290:259) (line:611)
          ================= list_transponders() =======================
          new_transponders(000): QAM_64   f = 754000 kHz I999B8C23D0T8G4Y0 (8895:12290:259)
          =============================================================
530000: (time: 00:16.800) ^C
ERROR: interrupted by SIGINT, dumping partial result...
(time: 00:17.990) dumping lists (0 services)
..
Done, scan time: 00:17.990
LibreELEC:~ #

To fix this problem, use my build from :[7.95.beta5] LibreELEC 8.0 builds for KI Plus / KII Pro
If is same as kszaq's only adding support for internal dvb tuner. Also install tvheadend42 + pvr.hts from this post.

kszaq: I have two differences in my build:
1. Amlogic I2C support is necessary for internal dvb driver;
2. I had issue with patches to compile latest media_build. To fix it I temporary deleted media_build-02-add-to-backports.patch

Is there anybody else having the issue that shutdown actually restarts the box with Beta5 running from SD?
Is this expected (know bug as suspended) or should I open a bug for it?
Thank you!

Quote from ssarava9

What's your internet speed ? I have 40 Mbps speed but all my 4K streams stutters after 5 mins and the video bitrates were between 60-90 mbits, please share your thoughts

My internet speed is 100 Mbps, but it's not relevant, since I was talking about 4K material being streamed from my local NAS.

Haven't tested this yet, but basically it's the kszaq's beta5b built with RetroPlayer patch.

EDIT: Moved to a separate thread as suggested (thread-4637.html).

The screen is black when the box is trying to play the next video file after finished the first one if Auto Play Next Video is ON, and
- The files are MOV (from Cannon DSLR camera, Quicktime format?)
- Files are on a local/NAS drive
- There is no OSD menu

Tested the same files with Kodi 17.0 final on Andriod (Same box), the Auto Play Next Video feature works fine.

I have search around several forums for assist with no success, I have a Tronsamart s905 Meta, I was successfully running Libreelec from internal Hard drive, until I decided to upgrade, but I accidentally installed incorrect file or tree, the box stopped working, on the box it display blue light but nothing is displayed into my TV.
I have exhausted the USB approach posted in Tronsmart forum, yet this approach did not work, the box appear to be active, but something is preventing it from being display on TV, this driving [img][img]

Thanks for your help!

Quote from r4w

Is there anybody else having the issue that shutdown actually restarts the box with Beta5 running from SD?
Is this expected (know bug as suspended) or should I open a bug for it?
Thank you!

Nope, it is not expected. Mine shuts down when told to do so
I don't remember anyone else mention this problem.
[hr]

Quote from mickr

The screen is black when the box is trying to play the next video file after finished the first one if Auto Play Next Video is ON, and
- The files are MOV (from Cannon DSLR camera, Quicktime format?)
- Files are on a local/NAS drive
- There is no OSD menu

Tested the same files with Kodi 17.0 final on Andriod (Same box), the Auto Play Next Video feature works fine.

My files from NAS play OK. I see this "bug" when I play Youtube playlists.
I thought it was a Youtube problem (one of many).