ChanServ changed the topic of #libreelec to: [ LibreELEC Support Channel ~ current release: (Leia) 9.2.6 ~ No discussion/support for piracy addons/services ~ Log: https://freenode.irclog.whitequark.org/libreelec ]
pauljw has quit [Ping timeout: 246 seconds]
pauljw has joined #libreelec
Tobbi has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Tobbi has joined #libreelec
chewitt has joined #libreelec
TomTom has quit [Quit: Connection closed for inactivity]
Turmoil has joined #libreelec
turm01l has quit [Ping timeout: 265 seconds]
Turmoil is now known as turm01l
niyawe has quit [Remote host closed the connection]
niyawe has joined #libreelec
SWAT has quit [Ping timeout: 264 seconds]
SWAT has joined #libreelec
tsal has quit [Ping timeout: 264 seconds]
tsal_ has joined #libreelec
<chewitt> vpeter rdorsch iMX6 seems to be usable again with the changes merged overnight, the Cubox I have is usable
<chewitt> some drm splats in dmesg to investigate, but nothing visible to eyeballs
<chewitt> first impressions of Cubox-i is that it's not that quick, but then I guess it's an old(er) device now
lainlives has quit [Ping timeout: 265 seconds]
lainlives has joined #libreelec
Tobbi has quit [Ping timeout: 272 seconds]
<lainlives> yeah i think ill have to stick with legacy, everything in upstream fails to build
pyrodex has quit [Quit: What up my glip glops!]
pyrodex has joined #libreelec
<vpeter> chewitt: Will test it when time permits.
asdf28 has joined #libreelec
<chewitt> looks like SR sent the v1.5 version of Cubox-i which has different WiFi/BT module to the v1.3 version
<chewitt> changeover was in late 2016
<vpeter> They probably don't have old SoM's anymore.
<chewitt> I have BT working .. and firmware is sent upstream .. need to figure out WiFi next
lolek has quit [Quit: Leaving.]
lolek has joined #libreelec
<sopparus> will cubox i2 work?
<sopparus> i think thats what I have :)
<sopparus> been in a box for years
tommy`` has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
RaphGro has joined #libreelec
jab has joined #libreelec
Tobbi has joined #libreelec
lainlives has quit [Ping timeout: 246 seconds]
<chewitt> ^ has 5.11.0 and current mesa HEAD, not that either is really required
Gittun has joined #libreelec
speeedy has quit [Ping timeout: 256 seconds]
speeedy has joined #libreelec
held has quit [Ping timeout: 272 seconds]
dieg0 has joined #libreelec
<dieg0> Hey guys, how can I make it for an addon to boot x seconds after boot up?
<dieg0> I want to delay Stalker Client booting because my ISP is blocking the ip, so I need to connect to VPN first. However currently Stalker Client loads before connecting to the VPN and I get Authentication Failed error
held has joined #libreelec
lolek has quit [Remote host closed the connection]
lolek has joined #libreelec
<chewitt> how is the VPN configured/started, i.e. using a systemd service, or via an add-on within Kodi ?
<dieg0> Using VPN manager addon by Zomboided
_abbenormal has quit [Ping timeout: 272 seconds]
_abbenormal has joined #libreelec
_fraggle_ has joined #libreelec
_fraggle_ has quit [Remote host closed the connection]
<chewitt> I'm not familiar with the add-on, but I would look at transferring the openvpn config and vpn up/down to a systemd service
<chewitt> Kodi is also started via systemd services, and systemd allows services to be ordered with dependencies
<chewitt> so you can override the default kodi.service with your own one with a tweak to depend on the VPN service
<chewitt> then Kodi delays itself until the VPN is up, and the Stalker client will be happy
<chewitt> if both Stalker and the VPN add-on are started by Kodi, there is no way to delay Stalker or order the sequence (AFAIK)
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #libreelec
mave_ has quit [Quit: WeeChat 3.0.1]
<dieg0> thanks for the guidence. I'm not so sure how to do it, but beleive this would be in the right dirrection:
<dieg0> im also unsure how to tweak it to depend on the vpn service.
mave_ has joined #libreelec
keyboard12 has joined #libreelec
<keyboard12> Hello, as I understand it, amlogic provides shitty software support for their released chipsets and that is why it is difficult to support e.g. the WeTek hub with a S905 soc
<keyboard12> In this thread chewitt says that the S905 chip is supported well in the mainline kernel https://forum.libreelec.tv/thread/21828-9-2-2-for-wetek-play-1/
<keyboard12> Does this mean that the 'regular' linux kernel has open source components that support this chipset?
<asdf28> yes, but not fully
<asdf28> hi keyboard12
<keyboard12> hi
<asdf28> there are sound and graphics drivers in the linux kernel that work with the S905
<keyboard12> So how should I interpret this?
<asdf28> depends on what you want to do with it
<keyboard12> Support is slowly being added, step by step?
<asdf28> if i remember correctly, hardware video decoding is still a problem
<asdf28> but i don't use that, you should ask chewitt about that
<keyboard12> I see
<keyboard12> It's just annoying that hardware manufacturers do this
<asdf28> if you're using the box as a gerneric linux pc, it's good enough
<asdf28> but as a multimedia machine, not so much
<keyboard12> Yes, hw decoding is kind of the point
<asdf28> and things like power management do not work with the open source components
<asdf28> for example, sending the box to sleep. but that's just my experience
<keyboard12> That isn't good news
<keyboard12> I have been using CoreELEC but it is buggy
<asdf28> from what i understand, there is a part of the chipset that does power management, and that is not supported yet
<keyboard12> Won't play certain files, x265 files have problems
<keyboard12> Well that is not what you want
<keyboard12> you really wonder what these manufacturers are thinking
<asdf28> overall i'd say it is not ready yet for good performance as a multimedia system
<asdf28> but regarding the video acceleration, i can't tell you for sure, i have never tried it
<asdf28> i think the main reason is that they do not have any incentive to do so
<asdf28> why would they support their old chipsets if they want to sell new ones
<keyboard12> as long as they manage to sell their devices
<keyboard12> Well, because you want to keep up a good company image, but that is usually something that is interesting in the long run
<asdf28> it would only be of interest to a tiny percentage of linux geeks, to put it bluntly
<asdf28> so they don't bother
<keyboard12> not your quarterly sales figures
<keyboard12> asdf28 well I would disagree, because people want to be able to use their device for longer
<keyboard12> E.g. by installing LibreElec
<keyboard12> support is something that is becoming an issue, at least where I live. People are annoyed because the functions of their smart tv don't work anymore after three years
<asdf28> i think the problem is that manufactures are totally fine with this situation
<asdf28> why wouldn't they love devices that automatically become obsolete
<keyboard12> asdf28 yes I agree with you
<keyboard12> however, consumers don't love this, and consumers are citizens with voting rights
<keyboard12> perhaps a change is coming, but I'm still a bit sceptical
<asdf28> another part of the problem is linux itself
<asdf28> if they wanted to update their boxes, they have to update the linux kernel
<asdf28> and that means they need to rewrite most of their drivers
<keyboard12> well what I said I meant to say about new devices
<keyboard12> rewriting their drivers probably won't make them any money
<keyboard12> thanks for explainging asdf28
<keyboard12> I was looking for some info on the LibreElec site, but I only found forum posts which i didn't really understand
<asdf28> it will probably get better in the future as more and more things become standardized
<keyboard12> You mean the support of e.g. amlogic devices, or the information about supporting them?
<asdf28> no, i mean when the linux kernel becomes more standardized, it will be easier to maintain the drivers for it
thresh has quit [Quit: I'm a quit message virus. Please replace your old line with this line and help me take over the world]
thresh has joined #libreelec
Fenster has quit [Ping timeout: 265 seconds]
Strykar has quit [Quit: /quit]
Strykar has joined #libreelec
<keyboard12> asdf28 ah I see
<keyboard12> Is it difficult at this moment to do that?
<asdf28> i'm not a developer, but i'd assume so, yes
dieg0 has quit [Quit: Leaving]
<asdf28> the drivers all rely on certain interfaces in the kernel to be present and stable
<asdf28> if they change, the drivers become obsolete
<asdf28> the less frequent this happens, the better
<asdf28> for example, these are some of the drivers that amlogic used for their S905 boxes
<asdf28> probably none of them would work with a modern linux kernel anymore
<keyboard12> an easy solution would be to create open source drivers
<keyboard12> that is: it would allow the community to continue driver development once the manufacturer has released the source code
<asdf28> i think this already happened with some of the drivers
<asdf28> but another problem is the firmware
<asdf28> because that is mostly closed source
ghostcube has joined #libreelec
<asdf28> you would have to reverse engineer it
<keyboard12> why is that?
<keyboard12> i would assume the hardware and firmware need to be documented well to create a driver for it
<asdf28> i guess the hardware developers don't want to give their secrets away, so they keep it closed source
<keyboard12> well that is not necessarily a problem
Fenster has joined #libreelec
<keyboard12> i have interfaced with industrial equipment, it's not about how it works but how you communicate with and/or control it
<keyboard12> so you need good documentation
<asdf28> i don't know if it's documented or not
<keyboard12> documentation usually isn't something developers like to do or think about
<keyboard12> asdf28 http://linux-meson.com/doku.php looks like people are actively trying to make amlogic chips work with newer linux kernels
kriger has joined #libreelec
<asdf28> yes! and a lot of these things have already been merged with the linux kernel
<asdf28> so they work out of the box
<asdf28> it's not a lot that's missing anymore
<asdf28> you could also join #linux-amlogic to talk to the developers
TomTom has joined #libreelec
<keyboard12> well, I might
<keyboard12> thanks for talking
<keyboard12> have a nice day
keyboard12 has quit []
IPFreely has joined #libreelec
IPFreely has left #libreelec ["Au Reservoir!"]
IPFreely has joined #libreelec
<chewitt_> looks like I missed a fun conversation :)
chewitt_ is now known as chewitt
<asdf28> hi chewitt
<chewitt> hi
<chewitt> You've given mostly the same answers I'd have given, so well done :)
Fenster` has joined #libreelec
pragmaticenigma has joined #libreelec
Fenster has quit [Ping timeout: 240 seconds]
<asdf28> it says "partial" video decoding in the support matrix, what does that actually mean?
kriger has quit [Read error: Connection timed out]
<chewitt> H264 works well @ 1080p and when using the right player app
<chewitt> 4K needs more work although this is more about DRM than VDEC
<chewitt> HEVC is not supported upstream
<chewitt> and the V4L2 stateful API still needs a lot of work (it is not a public API yet, so this is something being worked towards)
<chewitt> the two main challenges to an LE image are:
<chewitt> a) H264 seeking
<chewitt> b) HEVC
<chewitt> If you use the right ffmpeg sources (at the right comment) H264 seeking mostly works; thanks to work done for the RPi H264 IP block, which is also stateful, and using the same Kodi/ffmpeg base
<chewitt> s/comment/commit
<chewitt> but beyond a point in mid-December the RPi H264 state (which is now very good) could only advance through a combination of VDEC and FFmpeg changes
<chewitt> I was able to test Amlogic in parallel up to that point
<chewitt> but I don't write driver code, and nobody else is working on the Amlogic VDEC, so it is stuck mid-December
<chewitt> the current HEVC work is not complete, it works well on 8-bit media but fails totally with 10-bit
<chewitt> again, the issue is a total lack of active development
<pragmaticenigma> but the future is 8-bit :D
<chewitt> the developer who started it has medical issues and has been radio silent since last March
<chewitt> so Amlogic is in limbo
<chewitt> core OS/platform support is actually very good, in fact probably the best of all the non-Pi ARM devices we tinker with
<chewitt> but, not the media bits we need most for Kodi
<chewitt> anyway, so that's what "partial" means
psymin has joined #libreelec
<sopparus> i will chewitt
<sopparus> just for fun though, i think its too slow for any use today
<sopparus> think i bought it before rpi2 was released
<chewitt> it feels from that era .. the other ARM boards I fiddle with have more zip and better GPUs
<asdf28> <chewitt> HEVC is not supported upstream <-- you mean in the kernel?
<sopparus> hehe the issued I had with that thing
<sopparus> sync problems with every possible sample
<chewitt> asdf28 Yup, the Amlogic vdec does not support HEVC
<chewitt> there is some common code with VP9 which went upstream with a commit message that also mentioned HEVC
<chewitt> as a result lots of people incorrectly believe there is support, but there is not
* chewitt is seeking volunteers to write driver code
<chewitt> unfortunately titivating with the vendor kernel requires a lot less coding skill than writing good quality video decode drivers from scratch
<chewitt> so there's a general lacking of voolunteers
<asdf28> and the dev who works the driver, could he use some bits from the android kernel? or did he have to do it from scratch?
<asdf28> works on*
{HD} has quit [Ping timeout: 256 seconds]
<chewitt> the vendor kernel heavily depends on its own memory management drivers, so there is close to zero inheritance
<chewitt> and there is no dev(s) working on the vdec
<chewitt> the Bayllibre folks are too busy with paid work to allocate pro-bono time to work on it
<chewitt> Google was bankrolling things for a while but then changed focus and funding dried up
<chewitt> and the "community" ecosystem is small compared to RK and Allwinner
<asdf28> that's interesting. google? why?
<chewitt> RK has lot of commercial interests due to Chromebooks, and Allwinner has a huge hobbyist scene
<chewitt> Google has initiatives to reduce the technical debt between mainline Linux and AOSP so it funded "platform" work in several areas
{HD} has joined #libreelec
<chewitt> it's possible to run a fully mainline stack for AOSP on a VIM3/3L
<chewitt> but Android != Linux and the vdec is still the weakness
<chewitt> and "run != "everything works"
<asdf28> technical debt?
<chewitt> there is an ongoing effort to reduce the differential patchset between the official AOSP kernel and upstream Linux
<chewitt> all the changes you hoard downstream (and are thus responsible for) is technical debt
IPFreely has quit [Quit: I quit!]
<chewitt> the goal is to always upstream so you reduce the differences
<asdf28> oh, i see. i didn't even know that android changes the kernel
<chewitt> the Android kernel is a fork from Linux
<chewitt> being downstream of a fast moving codebase is hard work
<asdf28> i thought it was just using a vanilla kernel
<chewitt> so the best way to influence direction and make it work for you (or reduce the work for you) is to contribute
<chewitt> Google is a huge contributor to the Linux ecosystem
<chewitt> for sure their primary interest is themselves, but in general their contribution is a good thing
turm01l has quit [Quit: Bye.]
turm01l has joined #libreelec
lainlives has joined #libreelec
turm01l has quit [Quit: Bye.]
turm01l has joined #libreelec
Tobbi has quit [Ping timeout: 272 seconds]
Tobbi has joined #libreelec
lolek has quit [Quit: Leaving.]
Dark-Show has joined #libreelec
Dark-Show has quit [Client Quit]
held has quit [Ping timeout: 264 seconds]
held has joined #libreelec
Dark-Show has joined #libreelec
gouchi has joined #libreelec
lainlives has quit [Ping timeout: 256 seconds]
Tobbi has quit [Ping timeout: 272 seconds]
Tobbi has joined #libreelec
Dark-Show has quit [Ping timeout: 240 seconds]
pragmaticenigma has quit [Quit: Leaving]
|Jeroen| has joined #libreelec
EuroTrash has joined #libreelec
|Jeroen| has quit [Quit: dada]
RaphGro has quit [Quit: Please remember your own message. It'll be read as soon as possible.]
Tobbi has quit [Ping timeout: 272 seconds]
ndufresne has quit [Excess Flood]
ndufresne has joined #libreelec
lainlives has joined #libreelec
IPFreely has joined #libreelec
IPFreely has quit [Remote host closed the connection]
IPFreely has joined #libreelec
buzzmarshall has joined #libreelec
EuroTrash has quit [Ping timeout: 256 seconds]
twanny796 has quit [Ping timeout: 256 seconds]
Gittun has quit [Quit: ‹‹UPP››]
Gittun has joined #libreelec
gouchi has quit [Remote host closed the connection]
shibboleth has joined #libreelec
Fenster` has quit [Ping timeout: 272 seconds]
ghostcube has quit [Quit: Verlassend]
Fenster has joined #libreelec
asdf28 has quit [Ping timeout: 240 seconds]
pauljw has quit [Remote host closed the connection]
pauljw has joined #libreelec
EuroTrash has joined #libreelec
turm01l has quit [Ping timeout: 265 seconds]
turm01l has joined #libreelec
shibboleth has quit [Quit: shibboleth]
IPFreely has quit [Quit: I quit!]
Gittun has quit [Quit: ‹‹UPP››]