On Fri, 9 Mar 2012 15:54:29 +
Dominic Evans wrote:
> I don't know if anyone else still uses the xmltv2vdr.pl perl script
> for piping XMLTV data into VDR's epg, but I've been keeping a version
> of it updated with some additional function here:
I don't want to discourage you from that - but
On Fri, 9 Mar 2012 09:59:51 +
Dominic Evans wrote:
> Hi all,
>
> Running vdr-sxfe as a local frontend using a pipe _should_ be as fast
> (if not faster) than using XBMC over an http://localhost streamdev
> connection. However, I seem to find the opposite to be the case.
> vdr-sxfe still stru
On 9 March 2012 15:54, Dominic Evans wrote:
> I don't know if anyone else still uses the xmltv2vdr.pl perl script
> for piping XMLTV data into VDR's epg, but I've been keeping a version
> of it updated with some additional function here:
>
> https://github.com/oldmanuk/xmltv2vdr
>
> These are the
On 9 March 2012 16:25, Tony Houghton wrote:
>> I actually currently have deinterlacing disabled on both xineliboutput
>> and XBMC.
>
> AIUI interlaced fields are encoded as a pair in one field, so for most
> video players "disabled", ignoring the interlacing flags and treating it
> as as normal fr
On Fri, Mar 9, 2012 at 1:59 AM, Dominic Evans wrote:
>
>
> I just wish I could have the full VDR OSD, but within XBMC :)
>
Yeah, shame about that. It's unfortunate the development on XMBC isn't
anywhere as active or mature as VDR.
I recently got really lazy and installed yavdr-0.4 after 7 years
On Fri, 9 Mar 2012 14:15:06 +
Dominic Evans wrote:
> On 9 March 2012 13:42, Tony Houghton wrote:
> >
> > video.output.vdpau_hd_deinterlace_method:bob
> >
> > I was amazed at how good it looks, although I've only tried it at
> > 720p output so far, not at 1080p. I thought I was going to have
On 9 March 2012 16:18, Dominic Evans wrote:
> Ideally the channels column would be auto-sized to display the full
> channel name, as these tend to be a max of 20 characters it would be
> useful to be able to see the whole thing.
On a related note, it would also be good if the Now and Next pages o
Using the STNG skin at 1920x1080 (with the font size slightly reduced
from default), the columns on the Now and Next pages of the Schedule
don't currently adjust their width, but simply allocate all the extra
space to the final column containing the title. See
http://i.imgur.com/TKvGy.jpg for an ex
On 2012-03-09 16:34, Bio H wrote:
i also have struggled for this holy grail
xbmc would really be the ideal interface for me (just cant beat this
flexibility - try playing a .bin / .img over a network which is .rar'd -
cant do this on vdr)
i like the xbmc plugins and flexibility, for the most part
I don't know if anyone else still uses the xmltv2vdr.pl perl script
for piping XMLTV data into VDR's epg, but I've been keeping a version
of it updated with some additional function here:
https://github.com/oldmanuk/xmltv2vdr
These are the changes since the last version (1.0.9) was released on
th
On 2012-03-09 16:28, Dominic Evans wrote:
On 9 March 2012 15:11, Jonas Bardino wrote:
I launch vdr-sxfe with a command that overrides video_num_buffers,
Thanks for the suggestions. I'll add the buffers cmdline to my
vdr-sxfe startup. Interesting that you're using xvdr+tcp://localhost
rather t
i also have struggled for this holy grail
xbmc would really be the ideal interface for me (just cant beat this
flexibility - try playing a .bin / .img over a network which is .rar'd -
cant do this on vdr)
i like the xbmc plugins and flexibility, for the most part. :)
for last few months i've been t
On 9 March 2012 15:11, Jonas Bardino wrote:
> I launch vdr-sxfe with a command that overrides video_num_buffers,
Thanks for the suggestions. I'll add the buffers cmdline to my
vdr-sxfe startup. Interesting that you're using xvdr+tcp://localhost
rather than the default unix pipe. Intentional?
> T
On Fri, Mar 9, 2012 at 11:22 AM, Dominic Evans wrote:
> On 9 March 2012 10:09, Niels Wagenaar wrote:
>>> Does anyone have vdr-sxfe running flawlessly as a local frontend for HD
>>> content?
>>>
>>
>> I use a fully updated yaVDR 0.4 and I don't have any issues with the
>> vdr-sxfe frontend.
>
> H
On 9 March 2012 13:42, Tony Houghton wrote:
> The difference between vdr-sxfe and XBMC you're experiencing could be
> due to differences in the deinterlacing setting. You didn't say what
> your graphics card is, but the sort of low-power fanless card most of us
> like to have in an HTPC can't mana
On Fri, 9 Mar 2012 09:59:51 +
Dominic Evans wrote:
> Running vdr-sxfe as a local frontend using a pipe _should_ be as fast
> (if not faster) than using XBMC over an http://localhost streamdev
> connection. However, I seem to find the opposite to be the case.
> vdr-sxfe still struggles with HD
2012/3/9 Dominic Evans :
> On 9 March 2012 10:09, Niels Wagenaar wrote:
>
> Hmm. I have the same (yaVDR) running on an ION330 box. The channels I
> most have problems with are 1080i HD at bitrates of around 9-10 MB/s.
> Perhaps you could post your ~/.xine/config_xineliboutput to
> http://gist.gith
On 9 March 2012 10:09, Niels Wagenaar wrote:
>> Does anyone have vdr-sxfe running flawlessly as a local frontend for HD
>> content?
>>
>
> I use a fully updated yaVDR 0.4 and I don't have any issues with the
> vdr-sxfe frontend.
Hmm. I have the same (yaVDR) running on an ION330 box. The channels
2012/3/9 Dominic Evans :
> Hi all,
>
>-- SNIP --
>
> Does anyone have vdr-sxfe running flawlessly as a local frontend for HD
> content?
>
I use a fully updated yaVDR 0.4 and I don't have any issues with the
vdr-sxfe frontend.
For me, XBMC with the xvdr plugin seems to produce very ackward results
Hi all,
Running vdr-sxfe as a local frontend using a pipe _should_ be as fast
(if not faster) than using XBMC over an http://localhost streamdev
connection. However, I seem to find the opposite to be the case.
vdr-sxfe still struggles with HD content, has pops and clicks in the
audio, crashes out
20 matches
Mail list logo
