Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Sweden Transmission: DVB-T Encoding: MPEG-2 for SD (~15) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Finland Transmission: DVB-T, DVB-S/S2 Encoding: MPEG-2 for SD (lots of them) and H.264 for HD (about 10) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Germany Transmission: DVB-C, DVB-S Encoding: MPEG-2 for SD -- Needful GbR Rheinstraße 60a Telefon +49 (0) 26 24 / 95 29 301 56203 Hoehr-Grenzhausen Telefax +49 (0) 26 24 / 95 29 303 http://www.needful.deE-Mail m...@needful.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xinelibout --hud + xcompmgr = tearing
Alex Betis wrote: > I gave the nice xinelibout hud another try, but have to revert back since > running composite manager > creates tearing while watching movies. I've tries with xcompmgr with -n > option. > > Does anybody know how to fix that? > Or maybe there is another lightweight composite manager available? > > Without xcompmgr running there is no tearing at all. This is a known limitation of (at least) the NVidia drivers. Quoting the NVidia README: --snip-- The Composite extension also causes problems with other driver components: [...] On X.Org 7.1 and higher, the driver will properly redirect video into offscreen pixmaps. Note that the Xv adaptors will ignore the sync-to-vblank option when drawing into a redirected window. --snip-- Regards, Jörn -- Joern Reder -> http://www.exit1.org/ -> http://search.cpan.org/~jred/ pgpld7NvxNdFN.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: USA Transmission: DVB-S/DVB-S2 (soon) Encoding: MPEG-2 for SD, h.264 for HD (>100 channels) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Where do you live and what kind of broadcast do you receive?
Hi, I have wondered for some time how broad has VDR spread and how is it really used. So, if people could post their location and the type of broadcast they are receiving, we could get some kind of understanding about the state of DVB (or ATSC) as it is now. Just a brief description, using myself as an example: Country: Finland Transmission: DVB-C Encoding: MPEG-2 for SD (tens of channels) and h.264 for HD (less than 10 channels) The main point is to get an idea of the standards used across the globe. I know that wiki etc give some idea, but you can never beat the first hand information. -Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] power consumption, powertop and wakups per second with a af9015 device
On Mon, Mar 16, 2009 at 05:23:53PM +0200, Antti Palosaari wrote: > Heinrich Langos wrote: >> >> Anyway .. the main problem remains. >> >> Is there a tool that would only do some minimal actions on a dvb >> device? > > Like power_on? femon for example reads device status. zap, scan... > I cleaned up my system a little more to reduce the avg wakups per second. Now, when vdr is not started I get about 5 wakeups per second and only about 0.2-0.3% of the time is spent in C0 (cpu running). Now starting "femon" I get the following outut at about one line per second: | jukebox:/tmp/hgaf9015.MPZgGXIerw/af9015-a57ea2073e77# femon -H | FE: Afatech AF9013 DVB-T (DVBT) | status SCVYL | signal 18% | snr 0% | ber 0 | unc 6073 | FE_HAS_LOCK | status SCVYL | signal 18% | snr 0% | ber 0 | unc 6073 | FE_HAS_LOCK | status SCVYL | signal 18% | snr 0% | ber 0 | unc 6073 | FE_HAS_LOCK | ... The avg wakups per second go up to about 30, time spent in C0 is slightly higher with 0.4 - 0.6%. Now starting "zap" to tune into a channel: | jukebox:/tmp/hgaf9015.MPZgGXIerw/af9015-a57ea2073e77# zap -channels /tmp/channel.conf N24 | Using frontend "Afatech AF9013 DVB-T", type DVB-T | status SCVYL | signal | snr 0014 | ber | unc 17b9 | FE_HAS_LOCK Now the wakups per second go up up about 3000 and the cpu is running in C0 about 30% of the time! I ran "dvbtraffic" (itself causing about 10 wakups but hardly any cpu load) on another console to see what is happening and it seems like "femon" does only check the receiver's status while "zap" realy causes data to be transfered from the USB device to the host. So the rather heavy load that I see with vdr is probably not caused by vdr itself but by the USB data transfer. The new questions are: Does every USB DVB-T receiver cause the same amount of cpu load? Does vdr need to read the data stream all of the time? Can it be switched off? (At least while nobody watches and EPG data is not refreshed?) cheers -henrik ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
