Re: [vdr] Replacing aging VDR for DVB-S2
In general, get a gt220, as it has built in audio hardware, so that you should get audio without clock drift relative to the hdmi output. It is also powerfull enough to do temporal spatial deinterlacing on 1080i material. what do you think about NVIDIA's GeForce GT 430 http://www.anandtech.com/show/3973/nvidias-geforce-gt-430 seems it's the best choice for vdr/htpc - more cold than gt220 - more powerfull - HDMI 1.4, - 3D over HDMI - Ethernet channel - Audio return channel - 4k × 2k Resolution Support -- Удачи, Игорь ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sat, Jan 15, 2011 at 1:09 PM, Goga777 goga...@bk.ru wrote: In general, get a gt220, as it has built in audio hardware, so that you should get audio without clock drift relative to the hdmi output. It is also powerfull enough to do temporal spatial deinterlacing on 1080i material. what do you think about NVIDIA's GeForce GT 430 http://www.anandtech.com/show/3973/nvidias-geforce-gt-430 seems it's the best choice for vdr/htpc - more cold than gt220 - more powerfull - HDMI 1.4, - 3D over HDMI - Ethernet channel - Audio return channel - 4k × 2k Resolution Support It's a nice card but I'm not sure why you think it's the best choice for VDR/htpc. It's not going to give you any better image quality on HD content then you get from a gt220 at half the price. I don't see any advantage for most users in spending the extra money for one. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On 15/01/11 21:49, VDR User wrote: On Sat, Jan 15, 2011 at 1:09 PM, Goga777goga...@bk.ru wrote: In general, get a gt220, as it has built in audio hardware, so that you should get audio without clock drift relative to the hdmi output. It is also powerfull enough to do temporal spatial deinterlacing on 1080i material. [Snip] what do you think about NVIDIA's GeForce GT 430 [Snip] It's a nice card but I'm not sure why you think it's the best choice for VDR/htpc. It's not going to give you any better image quality on HD content then you get from a gt220 at half the price. I don't see any advantage for most users in spending the extra money for one. Even if it does run cooler than a GT220 it can't be by much judging by the size of the heatsinks. Ones with fans might be too noisy in an HTPC, and ones without will need a well-ventilated case, bearing in mind they might be working quite hard decoding HD for long periods. So... I wonder whether it might be possible to use a more eonomical card which is only powerful enough to decode 1080i without deinterlacing it and take advantage of the abundant CPU power most people have nowadays to perform software deinterlacing. It may not be possible to have something as sophisticated as NVidia's temporal + spatial, but some of the existing software filters should scale up to HD without overloading the CPU seeing as it wouldn't be doing the decoding too. Alternatively, use software decoding, and hardware deinterlacing. Somewhere on linuxtv.org there's an article about using fairly simple OpenGL to mimic what happens to interlaced video on a CRT, but I don't know how good the results would look. BTW, speaking of temporal and spatial deinterlacing: AFAICT one means combining fields to provide maximum resolution with half the frame rate of the interlaced fields, and the other maximises the frame rate while discarding resolution; but which is which? And does NVidia's temporal + spatial try to give the best of both worlds through some sort of interpolation? -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sat, Jan 15, 2011 at 2:36 PM, Tony Houghton h...@realh.co.uk wrote: I wonder whether it might be possible to use a more eonomical card which is only powerful enough to decode 1080i without deinterlacing it and take advantage of the abundant CPU power most people have nowadays to perform software deinterlacing. It may not be possible to have something as sophisticated as NVidia's temporal + spatial, but some of the existing software filters should scale up to HD without overloading the CPU seeing as it wouldn't be doing the decoding too. Well, you can get a gt220 for around $40USD which does full rate temporal-spatial 1080i and allows you to use it with an old slow cpu's that are dirt cheap if you don't already have one collecting dust in your basement. Not sure how much more economical you can get aside of free. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] new OSD system
Hello, I read about the ongoing work at the OSD system. I have to confess, that I don't really miss a truecolor OSD, but what I miss is the possibility to configure the OSD for each output-device separately. Currently I use a backend-vdr with budget-cards and an old fashioned FF. My TV is plugged to the old FF and I watch HD through a frontend-client with xineliboutput. That's not bad at all, but one shortcoming I noticed is, that configuration works for all output-devices. I tried the cool anthra-skin for HD - but then I don't get any OSD on FF. Same happens with keyboard. Currently its easy to distinguish the keys, as they are created from different systems and for so have different keycodes. But when I update my TV to a HD system and use xineliboutput on the backend as well as the frontend, than there's no way to have separate keyboard configurations. Why I want different setups? At the vdr I use a standard keyboard and the frontend is my desktop, where I use a Natural keyboard from M$ - which has a completely different layout of function-keys and additional keys. So it would be nice, to have sections in remote.conf that could be separated by output-device. Really great would be, if that sections could be created based on the IP of the client :) kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, VDR User wrote: I don't know about any of that but I wonder if the new osd system will be able to maintain widescreen HD resolution even when viewing 4:3 SD channels. Or if it will behave as it currently does, stretches/shrinks according to the channel/recording you're watching. Preferrably it won't do that, or at least be something the user can toggle. My output is always 1920x1080. I opt not to scale SD content up to HD. This means that when I'm watching 4:3 SD content in 1920x1080, I have borders on the left right, which I'm ok with. However, there's no reason I'm aware of why the osd can't still take advantage of the full 1920x1080. That scaling, you're talking about is not related to the new OSD system. Scaling is part of the output device and at least xineliboutput can be configured to not to scale. I was talking about OSD only - independant of the stream-format. In the example I wrote, anthra was configured with 1920x1080 - when I watch TV from FF and hit the menue button, the screen will change to black font on black background :) As far as I understand a statement of Klaus, the OSD will be different depending on the output device. So I wrote about my wish: if the OSD systems already are different, it would be nice to have different configurations too. kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
