On 9/12/06, <b class="gmail_sendername">Michael T. Dean</b> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 09/12/06 12:22, Richard Krehbiel wrote:<br><br>> I do wonder what's better: running the display at 1080i and letting<br>> the LCD panel de-interlace, or using 1080p and having Myth do it.<br><br>Depends on what you mean by better (
i.e. what do you want to be<br>better--both approaches have their drawbacks and advantages).</blockquote><div><br>
I'd been laboring under the impression that Myth would impose a single
output format, to which every source must be scaled (I'm happy to
find that impression was mistaken), so I was concerned about the
CPU burden of deinterlacing 1080i.<br>
<br>
I'm still thinking about XvMC. I expect my CPU is buff enough so
I shouldn't need it, but CPU cycles saved means cooler and quieter.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> A question for the developers, maybe: what about having Myth actually<br>> change the video output mode to match the source material (480i,
<br>> 480p, 720p, 1080i), for those with TVs that already do a nice job of<br>> scaling, 3:2 pulldown, deinterlacing, etc?<br><br>Hmm. We could create an option:<br><br>Separate video modes for GUI and TV playback
<br>Switch X Window video modes for TV. Requires "xrandr" support.<br><br>and put it in mythfrontend settings under "Appearance" on the 2nd or 3rd<br>page or so... (Hint, hint.)</blockquote><div><br>
Ah. I get it. :-) Thanks.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> So, I have another piece of hardware on order: a<br>> D-Link DWL-G730AP. It's a $50-ish portable multifunction device that
<br>> can bridge Wifi (as a client) to Ethernet. (Wifi on Fedora 5 is<br>> apparently a jungle - this will greatly simplify things.)<br><br>Hope this won't be necessary for pushing out video to remote clients<br>(
i.e. hope you only have a single combined frontend/backend). You might<br>be able to make it work, otherwise, but are likely to have "issues"<br>(i.e. prebuffering pauses, no ability to do HDTV remotely, etc.).
<br>
</blockquote></div><br>
Yes, it's a single box. I figure it just needs Internet access,
and access to some photos archived on another computer. (When the
day comes, I'll either cough up for 802.11n, or - urgh - pull the
wires.)<br>
<br>