ChanServ changed the topic of #libreelec to: LibreELEC Support ~ Log https://libera.irclog.whitequark.org/libreelec ~ No discussion or support for piracy addons or IPTV/VPN services
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
tsal has quit [Ping timeout: 240 seconds]
tsal has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Fenster has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
NaviTheFairy has joined #libreelec
<NaviTheFairy> Hey, I seem to have gotten locked out of ssh access by fat fingering my password a time or two. Is there a way to disable this fail2ban like behavior in the gui?
jernej has joined #libreelec
jernej has quit [Ping timeout: 248 seconds]
<mack> NaviTheFairy: I've never heard of such a feature in LE. Something else has likely changed. There are some good troubleshooting steps in this forum thread, though -- like how to see a good log and how to login textmode. https://forum.libreelec.tv/thread/25004-ssh-not-allowing-login-nightly-build-on-rpi4-over-pxe/
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<newuser566> kodi works finally, thx for your work
newuser566 has quit [Quit: leaving]
Misotauros has quit [Ping timeout: 246 seconds]
<adema> jernej, I asked around where the most recent patches were and if there were some upstreaming in progress, I was here that if wasn't on the roadmap, so I am sorry if I overstep any boundaries. I thought this work was abandoned and that people kept rebasing the old patches.
<adema> I can definitely not pursue this though, I haven't wrote the code, you guys did, I just mostly refactored it. I am just not sure why not try to merge experimental support that can be improved by the community? I feel like it would gain in quality if more people would use it and review it?
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Fenster has quit [Ping timeout: 250 seconds]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
NaviTheFairy has quit [Ping timeout: 260 seconds]
NaviTheFairy has joined #libreelec
IgorPec has quit [Quit: ZNC - https://znc.in]
volki57 has quit [Ping timeout: 240 seconds]
IgorPec has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
jernej has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<LEBot> [slack] <jernej> adema: did you asked here? If so, I missed your post
<adema> I asked some bits here and some on ffmpeg-devel channel
<LEBot> [slack] <jernej> anyway, we certainly need someone like you to upstream the patches, but before that, some work needs to be done
<adema> but no worries, I won't be pushing forward my attempt for the time being
<LEBot> [slack] <jernej> if you're still interesting in this work, please take a look at RPi version
<adema> I really just thought it would be genuily better to have *something* in FFmpeg that we can iterate over
<LEBot> [slack] <jernej> RPi uses improved design, which should lower latency
<LEBot> [slack] <jernej> so that should be combined with stable codecs, tested and then sent to ffmpeg ML
<adema> I honestly don't much knowledge about the inner working for v4l2 request APIs, I just read a lot of code and decided to clean / refactor some bits and send a v2 of the original patches. You can probably do a better job than me upstreaming it. I just thought no one was willing to do it so I volountered :p
<LEBot> [slack] <jernej> yeah, but the thing is that I don't have much time for such work
<LEBot> [slack] <jernej> this is also the reason why it wasn't pushed to ffmpeg yet
<adema> No worries, I fully understand :)
gouchi has joined #libreelec
<adema> If I were to go forward how would I test all of this? I just run ffmpeg with -drm and -drm_device option without a rawvideo codec and it seems to decode fine but do you have a test harness somewhere for this? Or just instruction on how to verify it works fine
<LEBot> [slack] <jernej> in other words, it would be great if you learn all the details and the benefit would be twofold - upstream ffmpeg support and another dev with request api experience :)
<LEBot> [slack] <jernej> don't you have any RK or AW board?
<adema> I have a RK3328 board
<LEBot> [slack] <jernej> well, that's good for dev purposes
<adema> but you cannot use hwaccels with ffplay right?
<LEBot> [slack] <jernej> no, but it can be tested via ffmpeg
<LEBot> [slack] <jernej> you can then even run conformancy test via fluster
<adema> right, that's the bit I need to know more about
<adema> This fluster I presume https://github.com/fluendo/fluster ?
<LEBot> [slack] <jernej> yes
shibboleth has joined #libreelec
<LEBot> [slack] <jernej> you can join #linux-media on oftc
<LEBot> [slack] <jernej> ndufresne is another dev, which cares about request api
<LEBot> [slack] <jernej> but he is gstreamer developer
<LEBot> [slack] <jernej> we work in tandem to test different userspace and kernel drivers
<adema> Oh great
<LEBot> [slack] <jernej> so in general, you want both, ffmpeg and gstreamer packages with request api support
<LEBot> [slack] <jernej> and run fluster with both and compare results
<adema> gstreamer has a pretty good support for the request API already I believe
<LEBot> [slack] <jernej> yes, in 1.20 is pretty solid
<LEBot> [slack] <jernej> well, it still has rough edges in some cases, but it's already usable
<shibboleth> chewitt: ping
<shibboleth> <shibboleth> i've noticed that 10/12 (30/36)-bit playback is now possible on rpi4, is it possible to instruct the pi to also output the gui in 10/12 to avoid the seconds of delay when switching for playback?
<shibboleth> <LEBot> [slack] <chewitt> shibboleth not possible to preset higher but depths. Also not desirable for GUI speed reasons
<shibboleth> yes, that was my question. maybe i misunderstood your answer, but the depth is all i'm trying to adjust
<shibboleth> i remember back when using a debian vm with a passthrough amd gpu for kodi, ever since the radeon 6950 i had in what... 2011? the UI was output as 10/30-bit
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<shibboleth> now, this wasn't possible until very recently on the pi, but outputting the UI as 10/30 or 12/36 by default will save me a few seconds when switching to 10/12 iptv sources
<shibboleth> surprised my plasma from 2008 can do 12-bit though. but that's what you get for shelling out 500=USD in 2008-money for a Pioneer :)
<shibboleth> 5k usd even
<LEBot> [slack] <jernej> adema: example ffmpeg command line for request api: ffmpeg -loglevel debug -hwaccel drm -hwaccel_output_format drm_prime -i video.mkv -f null -
narf has quit [Quit: bye]
<ndufresne> LEBot: hi :-D
narf has joined #libreelec
<LEBot> [slack] <Nicolas Dufresne> Nice, didn't know we could also chat here but from slack
IgorPec has quit [Quit: ZNC - https://znc.in]
IgorPec has joined #libreelec
shibboleth has quit [Ping timeout: 240 seconds]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
syphyr has joined #libreelec
bnevets27 has quit [Ping timeout: 248 seconds]
bnevets27 has joined #libreelec
bnevets27 has quit [Ping timeout: 256 seconds]
bnevets27 has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Successus has joined #libreelec
<Successus> Hi, could you please tell me, can I run LibreELEC using VirtualBox or Qemu? Should I use the ova or img file? Thank you in advance
<colo> is gpu_mem=76 the recommended setting for a RPi4? (2GB model, so plenty of RAM to spare)
<LEBot> [slack] <CvH> last time (a year ago) vbox was lacking a gpu driver
<Successus> I found this, I will see if I can follow the guides: https://forum.libreelec.tv/thread/20970-virtual-libreelec/ https://libreelec.tv/virtual/
<LEBot> [slack] <CvH> qemu should work, ova->qcow2 is also possible
<Successus> I see
<Successus> I need to extract something from ova, or ova directly?
<Successus> It said 2. Extract the LibreELEC-Generic.x86_64-9.2.0.vmdk 3. Convert the vmdk to qcow2
<LEBot> [slack] <CvH> qemu-img convert -O qcow2 some.ova output.qcow2
<Successus> I see, thank you
<LEBot> [slack] <CvH> not tried it with LE but this works in general
<Successus> what is LE?
bnevets27 has quit [Ping timeout: 256 seconds]
volki57 has joined #libreelec
bnevets27 has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Successus has quit []
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
jernej has quit [Ping timeout: 240 seconds]
Misotauros has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
gouchi has quit [Remote host closed the connection]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec