Separate names with a comma.
Discussion in 'TiVo Premiere DVRs' started by TiVoMargret, Nov 28, 2012.
I agree especially with the change of channels changing resolution..
That's what the 1080i fixed mode is for. I don't understand why anyone would use any other setting on a TV that can do 1080i.
I do Native. Always have and Always will If the Channel is 720P, I want my TV set to that
The reason to use native is fast action, sport events in particular, are better in 720p than 1080i. Fast action is smoother with a progressive scan.
Here Here. +1
Your TV always converts all video to the TV's Native resolution. So if it is a 1080p set everything (480i, 480p, 720p & 1080i) is up-converted to 1080p, if it is a 720p set everything is up or down converted to 720p. Having your TV convert 720p directly to 1080p without a TiVo converting it to 1080i in the middle may provide in a better picture but I am guessing most peoples actually setups make so they really can not tell the differance.
Mostly any issues with fast action sports are issues with the particular TV not if the broadcast is 1080i or 720p. Some LCDs have more problems than others with fast action and a 720p broadcast is easier for them to deal with but any good LCD TV and all plasma TVs should handle it just fine. My 4 yr old plasma has no visible issues on the 1080i or 720p stations with fast action sports. There is also no visible difference between using the TVs tuner (I am OTA) or watching through my TiVos which are all set to output fixed 1080i.
My TV does not convert the resolution to anything. If the source is 720P, then the TV displays a 720P resolution. Same if it is 1080i or P when using my PS3. I select all resolutions on my Tivo so it does not convert the resolution to anything other than what the source is
Your TV always converts everything to it's native resolution that is the way TVs work.
We can agree to disagree. I know this also from using the PC Input on my TV... it displays the resolution I send to it
All TVs have a fixed output resolution you are talking about input resolution. When your TV gets a signal it converts it to the TVs fixed output resolution (the TVs native resolution). When they say a TV is a 1080p TV that is what they are telling you - the resolution of the screen and thus what your TV has to convert all signals to. That is why some people on this forum use external high quality resolution converters, how well your particular TV converts the input signal to the fixed output resolution of your screen in part determines how your picture looks. If you send your TV an input signal with a input resolution that it was not designed to handle it will still convert it but you will end up with a partial blank screen.
To put it another way if you have a 1080p TV and sent it a 720p signal if the TV did not convert it to 1080p the picture would only take up part of the screen, because a 720p signal has significantly less pixels they what are available on a 1080p screen.
I just noticed this, too, after firing up my XL4 for the first time Monday evening. Checked my wife's HD in the bedroom and looked at my XL4 NPL ("My Shows") and saw that a couple recordings I KNOW were KUID were not marked as such....
It displays the resolution it receives as an input, but it still has to scale to the native display resolution of the TV itself. So the only consideration is if the TV or receiver does a better job at scaling than the TiVo. For many but not all TVs the difference is imperceptible. High end TVs and receivers will do a better job in which case using Native output on the TiVo makes sense, but the price you pay is resolution switching will cause the picture and sound to wig out for a little while the TV adjusts to the new input resolution.
Another new irritant I've noticed on this new update:
I'm (for example) watching live TV on ESPN HD. I have a recording set to start on the same ESPN HD channel in a few minutes. When the time for the recording to start comes around, the TV goes completely silent and the screen goes black for about 5 or 10 seconds as the recording starts. Before the update I would get a much shorter glitch that only affected the sound, now both sound and picture are screwed up for a longer period of time.
Whether TV or receiver does a better job at scaling than the TiVo is only a part of it. If you set Tivo's output resolution to fixed 1080i, and incoming signal is 720p, you'll have 2 conversions: 720p->1080i by Tivo and 1080i->1080p by TV/receiver. Theoretically, at least, that is worse than 720p->1080p directly, as the first conversion (forced interlacing) is losing some info, and the second is doing some guessing to make up for it, while direct conversion probably only does interpolation. Of course, your mileage may vary, depending on quality and size of you TV, how far you sit from it, etc.
1080i and 1080p have the same number of pixels. There is no conversion other than showing both fields of each frame at the same time, instead of one after the other, which your 1080p TV has to do anyway to display anything.
I might not be that picky, but I've never seen a diff with 720p channels on my 46" 1080p Panny S1 plasma with Tivo set to either native or 1080i. There's just nothing that I can see that would justify having the lag to switch res for native. And I watch a lot of sports on the ESPN 720p channels.
With the crappy quality we get on a lot of HD broadcasts now, there's not a lot any TV can do to make it better. And I'm not talking about Comcast etc., it's strictly due to crappy feeds from the sources.
Is this no longer active? Link says there is nothing available.
That's because the software has been released to everyone.
That is not nearly as simple as you think. You may want to read up a bit on deinterlacing. Just a couple of quotes from the easiest source to find:
Deinterlacing has been researched for decades and employs complex processing algorithms; however, consistent results have been very hard to achieve.
Yves Faroudja, the founder of Faroudja Labs and Emmy Award winner for his achievements in deinterlacing technology, has stated that "interlace to progressive does not work".