2014-07-20, 16:33
Already tested transmission, everything is working fine!
(2014-07-20, 20:55)Mafarricos Wrote: Is release related?
(2014-07-20, 20:55)Mafarricos Wrote: Trying to open some YouTube videos using yatse. And with this latest version I'm getting this type of errors:
http://xbmclogs.com/show.php?id=250741
Another log more complete:
http://xbmclogs.com/show.php?id=250752
Is release related?
(2014-07-21, 02:42)Milhouse Wrote: I don't really use Yatse any more, I tried opening a few Youtube videos with a recent release and the Youtube add-on without any problem. The errors appear to be http rather than https, can you try a pre-libressl release and see if the problem is still there?Hello people.
(2014-07-22, 00:57)AlderaaN Wrote: @Milhouse: Mind I ask which remote control solution are you currently using for your OpenELEC setup?
(2014-07-22, 03:14)Milhouse Wrote:Cool.(2014-07-22, 00:57)AlderaaN Wrote: @Milhouse: Mind I ask which remote control solution are you currently using for your OpenELEC setup?
VRC-1100 for my Pi. With my OpenELEC/x86 I use a Harmony One programmed with VRC-1100 codes.
(2014-07-22, 17:55)Heiko123 Wrote: Ohhh with one of the latest builds, I can't play all h264 files.
It is now the same problem how in raspbmc!
Is it possible to change the codec?
(2014-07-22, 20:39)glenn 1990 Wrote: Is there some kind of a hardware/firmware limitation according deinterlacing on SD content?
(2014-07-22, 23:51)popcornmix Wrote:(2014-07-22, 20:39)glenn 1990 Wrote: Is there some kind of a hardware/firmware limitation according deinterlacing on SD content?
Not a hardware limitation. There are two deinterlace algorithms - a complex one for SD and a simpler one for HD.
I have seen another (SD) interlaced sample that behaves better with the simpler deinterlacer.
I suspect that your file will look better with the simpler deinterlacer.
The short term solution is to provide a way of choosing the deinterlace algorithm (either through GUI or config.txt).
The longer term solution is to understand what's going wrong and fix it. There will be something unexpected in the encoding that means we are not identifying the fields correctly.
(2014-07-23, 20:01)glenn 1990 Wrote: Yea, a option in config.txt would be a nice thing.
I saw you did some work to offload deinterlacing to the TV, wich would prabably work ok then?
Simple deinterlacer is basic software BOB I assume, right?
# uname -a
Linux rpi512 3.15.6 #1 PREEMPT Thu Jul 24 11:13:25 BST 2014 armv6l GNU/Linux
# vcgencmd version
Jul 23 2014 21:08:37
Copyright (c) 2012 Broadcom
version 174cdd77563b98023955a94cb8d072d9c7095d6f (clean) (release)
# lsb_release
OpenELEC_Helix (Milhouse) - Version: devel-20140724114934-r18816-gc6c7a82