Re: [vdr] Replacing aging VDR for DVB-S2
I've avoided the noise problem by putting the VDR under the stairs where it can make as much noise as it likes. There it plugs in to a X-VGA splitter/broadcaster which sends duplicate signals over CAT-5 to each TV, where another small STB converts the signal back in to VGA. I've also put Infrared extenders everywhere. Result - a TV with no other hardware visible: no cables, no equipment, nothing. Just a TV on a wall bracket. Wife happy! Does that work with HD without much quality compromise? The VGA adapter I bought supports my TV which does 1366x768 just fine. It will also do 1920 resolution (I think) but my TV won't do that anyway. Picture is perfect - no complaints. Only thing my setup won't do is different front ends - but I have no need to watch different things in different rooms. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sun, 16 Jan 2011 10:46:27 -0800 VDR User wrote: > On Sun, Jan 16, 2011 at 10:22 AM, Tony Houghton wrote: > > > The pictures of these cards are enough for me, I'm sticking to my > > assumption that if I bought a GT220 I'd have to budget for either > > getting a specialist model with silent cooler, or replacing the > > cooler myself. > > No, pictures aren't enough. That's as silly as saying you can look at > a car and somehow magically know how it handles while driving. Sorry, > doesn't cut it. I can tell the difference between a Lotus Elise and a Volvo 740 by looking at pictures as well as I can tell the difference between a cooler designed to be silent and a cooler designed to be cheap. What models of GT220 do you use? > >> "VDPAU testing tool". > > > > The results don't give the right information to determine how well a > > card can handle 1080i. > > You apparently don't know the results come from analyzing actual > playback of actual samples of actual content. I only looked at the first page and didn't notice that the tool had been improved with more useful tests since the early postings. I'll have to give it a try myself. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Mon, 17 Jan 2011 09:53:00 +1300 "Simon Baxter" wrote: > I've avoided the noise problem by putting the VDR under the stairs > where it can make as much noise as it likes. There it plugs in to a > X-VGA splitter/broadcaster which sends duplicate signals over CAT-5 > to each TV, where another small STB converts the signal back in to > VGA. I've also put Infrared extenders everywhere. Result - a TV > with no other hardware visible: no cables, no equipment, nothing. > Just a TV on a wall bracket. Wife happy! Does that work with HD without much quality compromise? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
Indeed they do. I'm particular about noise as I use htpc's with my televisions. I don't want to watch something and have to listen to a fan. If I can barely hear a fan with the tv off, that is acceptable but it must be very low noise. I've avoided the noise problem by putting the VDR under the stairs where it can make as much noise as it likes. There it plugs in to a X-VGA splitter/broadcaster which sends duplicate signals over CAT-5 to each TV, where another small STB converts the signal back in to VGA. I've also put Infrared extenders everywhere. Result - a TV with no other hardware visible: no cables, no equipment, nothing. Just a TV on a wall bracket. Wife happy! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sun, Jan 16, 2011 at 9:42 AM, Eric Valette wrote: > BTW: is temporal-spatial available on ion2 and do you see improvement? I > think I read somewhere than the bus between the N10 and the ion2 has not the > bandwidth to do 1080? Just curious The ion2 is currently being used for testing. It actually can do just over 60 fields temporal-spatial on 1080i with the latest stable driver 260.19.29. IIRC previous driver versions had some issues there. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sun, Jan 16, 2011 at 10:22 AM, Tony Houghton wrote: > I've bought many graphics cards over the years and every time one came > with a fan it's been noisy and I've replaced it with an aftermarket > cooler with a bigger heatsink, and either a bigger fan(s) or no fan. > > People have different standards of noisy. If everyone was as demanding > as me they wouldn't have considered using an XBox as a media player! Indeed they do. I'm particular about noise as I use htpc's with my televisions. I don't want to watch something and have to listen to a fan. If I can barely hear a fan with the tv off, that is acceptable but it must be very low noise. > The pictures of these cards are enough for me, I'm sticking to my > assumption that if I bought a GT220 I'd have to budget for either > getting a specialist model with silent cooler, or replacing the cooler > myself. No, pictures aren't enough. That's as silly as saying you can look at a car and somehow magically know how it handles while driving. Sorry, doesn't cut it. >> Maybe a better idea is to not assume anything at all, but rather >> actually look up real life data or just buy one and see for yourself >> (as I did). There's no reason to take guesses about any of this >> stuff, plenty of users have posts their results and specs at various >> forums. A good place to start would be nvnews.net and read the thread >> "VDPAU testing tool". > > The results don't give the right information to determine how well a > card can handle 1080i. You apparently don't know the results come from analyzing actual playback of actual samples of actual content. Yes, the data tells you exactly what kind of performance you can expect since it's generated from actual use cases. Again, stop assuming everything and turning your nose up at first-hand experience. I've ran those tests myself, obviously know what deinterlacers I'm using, and have watched plenty of content seeing the result with my own eyes from the hardware we're talking about. Additionally I've done the same with various hardware configurations.. What you're telling people simply doesn't agree with reality. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sun, 16 Jan 2011 09:33:30 -0800 VDR User wrote: > It's a bad assumption to say lesser expensive gt220 cards have cheap > and noisy fans. It's simply not true. I've bought many graphics cards over the years and every time one came with a fan it's been noisy and I've replaced it with an aftermarket cooler with a bigger heatsink, and either a bigger fan(s) or no fan. People have different standards of noisy. If everyone was as demanding as me they wouldn't have considered using an XBox as a media player! The pictures of these cards are enough for me, I'm sticking to my assumption that if I bought a GT220 I'd have to budget for either getting a specialist model with silent cooler, or replacing the cooler myself. > Maybe a better idea is to not assume anything at all, but rather > actually look up real life data or just buy one and see for yourself > (as I did). There's no reason to take guesses about any of this > stuff, plenty of users have posts their results and specs at various > forums. A good place to start would be nvnews.net and read the thread > "VDPAU testing tool". The results don't give the right information to determine how well a card can handle 1080i. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
grr, nvidia and their stupid naming system. 430 looks more like a 5xx card but with the discontinued number line. 4xx was being replaced by refined 5xx. This is the first non-crippled chip released with a 4xx number. So once again, like with the 8400's we can't be sure what die it's based on. On 1/15/2011 2:09 PM, Goga777 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
I wouldn't buy any 4xx cards. All have dead weight on chip and are basicly power hungry/wasting beta versions. Look for 5xx On 1/15/2011 2:09 PM, Goga777 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On 16/01/2011 18:33, VDR User wrote: One I'm using as a full time htpc, the other is a test box at the moment. And they do 1080i just fine. The ion1 box can't do temporal-spatial on 1080i but it does temporal just fine. I'm very satisfies with the very low power and no noise from the ion's. I can confirm this as I use the same setup. BTW: is temporal-spatial available on ion2 and do you see improvement? I think I read somewhere than the bus between the N10 and the ion2 has not the bandwidth to do 1080? Just curious -- eric ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On Sun, Jan 16, 2011 at 6:00 AM, Tony Houghton wrote: > I also/mainly mean more economical in power consumption and ease of > installation and cooling. Most cheap GT220s have fans (most likely cheap > & noisy ones) so I wouldn't want one of them in my HTPC. A fanless one > might overheat being packed in closely with my DVB cards. But many > motherboards already have integrated NVidia chipsets with HDMI, > including audio, and basic VDPAU functionality. Mine is an 8200 and I > know there's also been a lot of interest in Ion systems for HTPCs, so I > think finding some way of getting these systems to display 1080i nicely > should be a good move. It's a bad assumption to say lesser expensive gt220 cards have cheap and noisy fans. It's simply not true. It's funny you mention ion as well. I have both ion and ion2 systems as well. One I'm using as a full time htpc, the other is a test box at the moment. And they do 1080i just fine. The ion1 box can't do temporal-spatial on 1080i but it does temporal just fine. I'm very satisfies with the very low power and no noise from the ion's. Maybe a better idea is to not assume anything at all, but rather actually look up real life data or just buy one and see for yourself (as I did). There's no reason to take guesses about any of this stuff, plenty of users have posts their results and specs at various forums. A good place to start would be nvnews.net and read the thread "VDPAU testing tool". Cheers ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, Steffen Barszus wrote: > As already said. Start a second vdr instance , using streamdev server > and client for the dvb devices, and xineliboutput as output, start the > plugins you want for the client on that instance. and you are done. OK - I'll try that on my next bigger sparetime slot ;) When I setup my HD-vdr, I was not able to get streamdev running. > you did not say anything about your installation, so help on this is > impossible. Well - this thread has already become very OT, but ok: my setup is: Vdr-Backend: CPU: single-core Athlon 2500 reduced to 1900 MB: Gigabyte GA7N400S dvb: FF from Hauppauge, Budget from Mystique vdr: 1.7.16 from e-tobi with ACPI wakeup os: debian squeeze hd: removable for recordings net: gigabit TV: connected to FF AV: connected to FF via SP/DIF-Opto-converter Vdr-Frontend (my desktop): CPU: Phenom II X4 965 MB: Gigabyte GA-880GM-UD2H os: debian squeeze net: gigabit Monitor: 60Hz standard I start the frontend with this script (as mentioned earlier - I don't have a vdr installation at that machine): --- --- #!/bin/bash # name of vdr-host vdr='vdr' # options for xine postprocessing post='tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1' # options: tcp | udp transport='tcp' # options: sxfe | fbfe display='sxfe' vdr-$display --width=1200 --height=720 --buffers=5000 --post $post xvdr:TCP://$vdr:37890 --$transport --- --- kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
On Sun, 16 Jan 2011 16:27:47 +0100 Gero wrote: > With my current setup I do have certain issues. But meanwhile I know > how to handle most of them, which means, I don't have any pressure to > change my setup. > As already said. Start a second vdr instance , using streamdev server and client for the dvb devices, and xineliboutput as output, start the plugins you want for the client on that instance. and you are done. Like that you can also start a second for another client if you are in need. The server vdr/vdr main instance will have all dvb devices, client vdr asking for the channels via streamdev as needed. Thats what gerald was referring to. How you do that is up to you - you did not say anything about your installation, so help on this is impossible. Steffen ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, Gerald Dachs wrote: > Sorry, but I think I don't ask you for too much, if I ask you to look > into the sources of this addon yourself. Ok - you could have mentioned that earlier. I expected the solution in the blog article. ... but what stated Steffen: my expectations are wrong. Obviously! Currently I'm working on a quite odious job - may be I'm quite a bit too huffish. Sorry for that. kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Am Sun, 16 Jan 2011 16:27:47 +0100 schrieb Gero : > I beg your pardon second time! > > I don't use yavdr and I'm not willing to change my vdr to yavdr - so > using your addon is no acceptable solution - no matter how good your > addon might be! You know, that the reason for not using yavdr is > ubuntu being the base of yavdr and that my rejection is NOT related > to the yavdr team in any kind! Sorry, but I think I don't ask you for too much, if I ask you to look into the sources of this addon yourself. It is really very easy. You can find it here https://launchpad.net/~yavdr/+archive/unstable-yavdr/+sourcepub/1385820/+listing-archive-extra Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, Gerald Dachs wrote: > You should really look more carefully into it. I beg your pardon! I read that page for sure, but I can't state, that I understood much. I did not find any hint, that could change any of my issues either. May be that hint might be there, but then I did not understand it. I'm willing to change my installation - no question - but I have very little sparetime, so I don't have the time to search for lots of additional links and follow each of them. Sorry. > Maybe you didn't find anything about installing a second instance, > because it has not to be done. When you look few postings back, I got the advice to install a second instance. I know, there are people around who run such a configuration, I read that hint quite often in the forum, but I did not find a page, where the problems of such an installation where disscussed or solved. Therefore I don't want to change my installation, before I know how to solve my upcoming issues. With my current setup I do have certain issues. But meanwhile I know how to handle most of them, which means, I don't have any pressure to change my setup. > You only have to start your already installed vdr with another configuration. > This happens in the addon I pointed you to. I beg your pardon second time! I don't use yavdr and I'm not willing to change my vdr to yavdr - so using your addon is no acceptable solution - no matter how good your addon might be! You know, that the reason for not using yavdr is ubuntu being the base of yavdr and that my rejection is NOT related to the yavdr team in any kind! Anyway ... You could explain me, what you did or show me a page, where that items are disscussed. No question, I'm willing to learn - but I'm not willing to change my basic principles or waste my time. I don't know - did you expect me to dive into your sources? kind regards Gero ___ 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.1.2011 23:09, Goga777 wrote: 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 + hw support for bitstreaming DTS-HD and Dolby TrueHD etc audio codecs. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Am Sun, 16 Jan 2011 12:19:41 +0100 schrieb Gero : > Hello, > > thank you for the link. > > Gerald Dachs wrote: > > It is not really what you are looking for, ... > > Hm - may be I missed the real thing, but I did not find anything > about installing 2 vdr instances on the same machine. Maybe you didn't find anything about installing a second instance, because it has not to be done. You only have to start your already installed vdr with another configuration. This happens in the addon I pointed you to. You should really look more carefully into it. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replacing aging VDR for DVB-S2
On 16/01/11 01:16, VDR User wrote: On Sat, Jan 15, 2011 at 2:36 PM, Tony Houghton 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. I also/mainly mean more economical in power consumption and ease of installation and cooling. Most cheap GT220s have fans (most likely cheap & noisy ones) so I wouldn't want one of them in my HTPC. A fanless one might overheat being packed in closely with my DVB cards. But many motherboards already have integrated NVidia chipsets with HDMI, including audio, and basic VDPAU functionality. Mine is an 8200 and I know there's also been a lot of interest in Ion systems for HTPCs, so I think finding some way of getting these systems to display 1080i nicely should be a good move. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Al 16/01/11 12:09, En/na Gero ha escrit: Currently when I forget to switch to a SD channel on the xineliboutput frontend before stopping that frontend, the vdr is not operable for the FF- user. There's no way to recover. I had the same issue with vdr-xine and the dxr3 plugin. Maybe the ff output should do something similar to what I did with the dxr3 plugin: if the stream is hd (actually h264), instead of sending it to the dxr3 (and crashing it), just show a message that the video stream is not supported. Everything else (audio, osd), still works fine. Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, Steffen Barszus wrote: > actually i think its wrong setup on your side. call it "wrong > expectations". That - of cause - may be true! I'm quite new to client/server vdr. I tried lot of things and my current installation is the only, I succeeded to get into play. ... and - after all - it works quite fine! My issues are issues in the sense of "you put sugar in your coffee?" and not the question, whether it is possible to create coffee. So don't give my issues to much importance. I think - there are several aspects of vdr, that could be improved. The question is not, whether improvement is possible, but if that aspect has enuf relevance to start thinking about improvement. But - that's not my decision. I only can talk about what I like to get improved. kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, thank you for the link. Gerald Dachs wrote: > It is not really what you are looking for, ... Hm - may be I missed the real thing, but I did not find anything about installing 2 vdr instances on the same machine. When I install a second instance on my backend, I need to know, what happen to the DVB-cards, who is responsable for recording, who resolves resource conflicts ... A lot of questions I'd like to know before I change my installation. kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
On Sun, 16 Jan 2011 12:09:34 +0100 Gero wrote: > Hello, > > Udo Richter wrote: > > Its probably a lot easier to solve this at the output side within > > xineliboutput. > > So you change a possible issue into a 'NMP'-issue - not very smart. > (NMP stands for "not my problem") actually i think its wrong setup on your side. call it "wrong expectations". see Geralds answer. As allready said, put a streamdev client locally on the server or put vdr on the client and use xineliboutput on the client. You actually want streamdev for client/server. xineliboutput is just an output plugin , not client server. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, Udo Richter wrote: > Am 16.01.2011 05:35, schrieb Gero: > > 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. > > You're using a very special situation here, as xineliboutput is IMHO the > only output device that can promote itself to be 'the' output device at > runtime. Well - that is a point, I don't like at all! So if someone watches TV with the FF card, the TV gets dark as soon as I start the xineliboutput frontend. I don't know anything from the vdr internals - I'm just a user. >From my (user-)point of view the vdr may not break, if a client does an error. Currently when I forget to switch to a SD channel on the xineliboutput frontend before stopping that frontend, the vdr is not operable for the FF- user. There's no way to recover. I have to start the xineliboutput frontend, change the channel and then stop that frontend again. > VDR itself has not much to do with this switching, Best would be, to be able to switch this kind of switching off completely. > and doesn't know in advance how many of its devices suddenly may or may not > be the output device. That's how it should be - at least from my point of view ;) > Keeping multiple configurations for OSD persistently > would break a lot (including plugins), and will probably have lots of > issues. Well, after all it was just a wish :) I think, the task to create a new OSD system is neither simple nor small - so lots of issues have to been taken into account. I like to think about upcoming issues in advance and I'm sorry, but I don't like that pessimists, that only know to talk about things, that are impossible, that should never get touched, > Its probably a lot easier to solve this at the output side within > xineliboutput. So you change a possible issue into a 'NMP'-issue - not very smart. (NMP stands for "not my problem") kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Am Sun, 16 Jan 2011 10:44:16 +0100 schrieb Gero : > > Its not to much overhead actually :) > > Well, I decide that, when I see the system load ... > > So - I'm curious and willing to test. Do you know a url occasionally > of someone who already did it? It is not really what you are looking for, but I implemented the picture in picture addon for yaVDR with this approach: http://www.yavdr.org/blog/blog-post/2010/12/01/announcing-yavdr-addon-pip-picture-in-picture/ It is unbelievable simple and could give you an idea what the system load could be. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Am 16.01.2011 05:35, schrieb Gero: > 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. You're using a very special situation here, as xineliboutput is IMHO the only output device that can promote itself to be 'the' output device at runtime. VDR itself has not much to do with this switching, and doesn't know in advance how many of its devices suddenly may or may not be the output device. Keeping multiple configurations for OSD persistently would break a lot (including plugins), and will probably have lots of issues. (I already can imagine OSD size depending on DVB driver load order...) Its probably a lot easier to solve this at the output side within xineliboutput. xineliboutput could easily backup the OSD parameters when replacing the primary device, set his own parameters, and set them back when disconnecting. Probably needs some care to make sure that parameters get restored in any case, but solvable. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Hello, thank you for your support! Steffen Barszus wrote: > configure a second vdr instance (on the client or the server) ... Hm - the client does not have a vdr-instance yet - and for so, the only thing I can configure there, is the IP of the server and the frontend to use. AFAIK all configuration (remote.conf) is done on the server. At least on my tests I had to add the XKeySym entries to the servers remote.conf If there exists a kind of key mapping in the frontend already, please let me know. I did not find a way to add client specific configuration yet. > Its not to much overhead actually :) Well, I decide that, when I see the system load ... So - I'm curious and willing to test. Do you know a url occasionally of someone who already did it? There are too much questions otherwise ... kind regards Gero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
On Sun, 16 Jan 2011 06:16:59 +0100 Gero wrote: > 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. configure a second vdr instance (on the client or the server) serving the xineliboutput, then you can have 2 configurations right now allready. Its not to much overhead actually :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
