vdr February 2005

vdr@linuxtv.org

107 participants
103 discussions

RE: [vdr] OT: Best DVI Video Card for Xine
by jori.hamalainen＠teliasonera.com 28 Feb '05

28 Feb '05

> > I think Faroudja chips are not so good. At least my Philips > LCD TV has > > such chip, and everytime text is scrolling Faroudja's > autosensing goes > > This autosensing is not done by the FLI2300, but by Philips circuitry. Like I already said it can be problem of TV. And to be clear, FLI can be the best deinterlacer hardware for PAL material, but on my environment it has its limitations, and I see that on scrolling news tickers, and it annoys a bit. But I … [View More]am wondering, what chip then in TV's make the decision what type of deinterlacer is needed? Most logical place IMO would be deinterlacer chip, because it makes the conversion also. ADC's just dump fields to RAM. Thats why I wrote that Philips should have menu option or similar to make Faroudja to do just PAL deinterlacing with 50Hz. > Normally, the FLI2300 are thought of as the best deinterlacer > for stuff like sports etc (video mateial) (vs SI). > > > doesn't allow this. I see that this is problem of my TV, but if > > Faroudja was good it would not do this. > > So, what scaler/deinterlacer do you have on your proj? I think it is Pixelworks. But it is projectors backend system feature to control deinterlacer/scaler. It has 3 options, none, video and film. Film is autosense for 24/50 material, video is just 50. > > HTPC also can read MPEG streams flags to aid deinterlacing/inverse > > telecine, and Faroudja's don't have that stuff because they > are behind > > video line on TVs/projectors. > > This is true, but as long as we do not have CPU´s powerful > enougth, hardware solutions will be better. I tend to use Nvidia's purevideo, which is a bit of both. I hope someday also Linux support is introduced. So vdr-xine a lot of CPU is needed. With Purevideo support all nice features are available on 20% CPU time on 3GHz HT-processor. Just quick meaningless conversion is 100%/2 CPU (how windows sees, as real HT is ~1.3 CPU's) = 50%=1 CPU on 3GHz => 20% on 50% => 1.2GHz processor roughly is needed. > Also, a big > problem is that HTPC´s cannot change their refreshrate to the > framrate. Which means bad picture quality, unless "burning" > video bandwith by going over 85Hz refresh (or prefferebly > higher), but who wants that? Well I adapt my framerates based on content. Because if I see the effort to view my stuff in HD, I can change X & Windows framerates also with much less effort.. :-) I think automatic refresh-rate adaptation is just video players feature. If modelines are already on X-config file, and tv/projector/monitor has picture optimized for output rate, I cannot see why for example Xine could not automatically change the rate based on input content. Best regards, Jori [View Less]

1 0

Re: vdr-xine and df_xine
by Lucian Muresan 28 Feb '05

28 Feb '05

Lucian Muresan wrote: > mike lewis wrote: > >> Hello People, >> >> I was just wondering if it was possible to use df_xine as the >> front-end to vdr-xine? > > > Should be possible. At least I heard that from Rob Shortt, one of the > Freevo developers on the Freevo IRC channel. I wanted to try that > myself, but I couldn't until now, most likely I have to reinstall the > system as I cannot sort out a linker problem which is stopping me to get … [View More]

2 1

xine-lib patch for xine CVS ?
by Grégoire Favre 27 Feb '05

27 Feb '05

Hello, has someone a patch for the CVS version of xine-lib ? Thank you very much, -- Grégoire Favre ___________________________________________________________________ http://magma.epfl.ch/Gregoire.Favre mailto:Gregoire.Favre@gmail.com

3 6

vdradmin-0.96 patch: store channel-id into auto timers
by Rantanen Teemu 27 Feb '05

27 Feb '05

Hi, Here is a small patch which modifies vdradmin to store channel id into auto timer entries (instead of channel number). This way auto timer channels will not get messed up when moving channels in VDR. http://tvr.dy.fi/vdradmin-0.96_For_vdr-1.3_StoreAutotimerChannelID_And_E ventIdCheckDisable.diff This patch also includes my earlier vdradmin -patch for vdr-1.3, and disables EPG event-id check from all timers created by vdradmin. Let me know if it doesn't work. You might want to backup … [View More]

1 0

to use a current theme color in a plugin
by tinconn＠virgilio.it 27 Feb '05

27 Feb '05

hallo all I'm like to make dynamic the color of my plugin using the current set theme. I have read the PLUGIN.html but i understand that with this three line of c++ code i can set a clrTitle color and then i can use it: static cTheme Theme; THEME_CLR(Theme, clrTitle, 0xFFBC8024); int clrBackwindow = Theme.Color(clrTitle); I don't wont to redefine the color, but i want to use the actual theme color... Please help me

5 11

Dropping support for '-icam' firmware
by Klaus Schmidinger 27 Feb '05

27 Feb '05

Is any VDR user still using the so-called '-icam' firmware for full featured DVB cards? That's the "old" firmware that handled CAMs directly, without any control from the application. The recommended "new" firmware has "link layer" CAM support built in, which allows the application to have full control over the CAM. Most likely everybody nowadays uses the new firmware, so I'd like to drop support for the '-icam' version from VDR. Note that this only affects users with CAMs - if you don't have … [View More]

2 1

Problems with 20 Timers
by Chris Warren 27 Feb '05

27 Feb '05

Hi all, I've managed to import EPG data for 2-3 weeks in advance. The trouble is I use epgsearch to automatically create timers to record a couple of series. This leads me to have around 20 active timers. It seems that the more timers you have the slower VDR (1.3.21) becomes. I normally get "max. latency time 2 seconds" in my syslog, however when I have 20 timers, I get "max. latency time 17 seconds". What's causing it to slow down so much? I've tried removing all plugins but if I leave the … [View More]

11 20

xeatre ?
by John Grant 27 Feb '05

27 Feb '05

I think I installed the wrong requant for dvd burn, but for the last three weeks I have been unable to get to their website to get the "correct" version, if only to check it against what I have. Is there another source for it somewhere? ====================== Disclaimer ======================= The information in this message is confidential and is intended solely for the addressee. Access to this message by any other person is not permitted. If you are not the intended recipient, any … [View More]

1 0

Mailing List Etiquette
by Clemens Kirchgatterer 27 Feb '05

27 Feb '05

This is the (updated) 'official' vdr-mailing-list-etiquette-reminder. Please take this as a serious advise. The VDR mailinglist is getting quite large and it shouldn't become a pain in the ass to follow. Take the time to read it, especially if you are new to mailinglists in general. E-mail formatting ================= Mailing list email should fit the following criteria: DO -- * Trim quoted material to the minimum needed to clarify what you're talking about. * Add a blank line _before_ … [View More]and _after_ each quote for better readability. * Make sure you are attributing material to the correct person (i.e. make sure the "On 19/07/2002, Joe Bloggs said:" is correct) * Write your responses _after_ the quoted text, not before. If your mail client makes it difficult to do this, get a new one. * Make sure lines are wrapped at maximum 76 characters (to fit an 80 character wide screen), even if the text had been quotet several times. * Use ">" at start of line to mark quoted text. * Set your mail client to "english headers" to avoid subjects like: "AW: Antwort: Re: AW: AW: AW: Re: Some Topic allready trunkated" If you see one, don't just add another "Re:" but remove all "AW:" and other chained "Re:". * Use a descriptive subject! A message titled "A small wish" doesn't tell what it is about. Better use something like "should do xyz" or "crashes when doing xyz". * Always write one separate message per topic. some people (especially those who matter) might not read mixed-up and lengthy threads. * Start a new thread when posting a new subject. * Make emails as short as possible whilst keeping them comprehensible. Don't ----- * Don't post in either HTML-only or in Text and HTML. If your mail client doesn't support this, change it. * Don't top post. * Don't give a one line answer having quoted the whole post. * Don't use a too long signature. * Don't reply where you should have started a new thread. * Don't break threads by sending a new mail, where you should have replied. * Don't test post. Send your test posts to "echo(a)fu-berlin.de" or similar reply machines. * Don't use lengthly disclaimers. If not possible, use a freemail account. * Don't quote disclaimers and other footers. General Etiquette ================= This can really be summed up in one phrase - 'be polite'. Allways use your 'Real Name' when posting to mailinglists or newsgroups. If you think something is off-topic, don't reply to the list although you may want to send a short and *polite* note to the person privately telling them which list would be more appropriate; don't just say - "that is OT here". Before asking a question, please Have a look at the mailing list archives at http://www.linuxtv.org/pipermail/vdr/ If someone flames or trolls the list, don't reply - it wastes everyones bandwidth and time. Don't reply to spam which gets through to the list - just ignore it when it does. Resources ========= * The ultimate guide to most matters to do with email etiquette is RFC-2822 which can be found at: ftp://ftp.isi.edu/in-notes/rfc2822.txt * A german site set up by some usenet-people, who take it even more serious with netiquette. http://learn.to/quote [View Less]

1 0

unsubscribe
by Joerg Vogtschmidt 27 Feb '05

27 Feb '05

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr February 2005