<div>just confirming that [16167] (ie HEAD at the time I did it) with additional patches of #4706,#4699 and #4702 "works for me" on win32. :-)<br></div>
<div>Buzz.<br></div>
<div class="gmail_quote">On Feb 19, 2008 6:05 AM, Andrei Tanas <<a href="mailto:andrei@tanas.ca" target="_blank">andrei@tanas.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><5f881c1cb986fc58c6d85ad3a2409631@localhost><br><<a href="mailto:3a83b0a90802181134t2d5679a8yd6e25c6b04b25bf9@mail.gmail.com" target="_blank">3a83b0a90802181134t2d5679a8yd6e25c6b04b25bf9@mail.gmail.com</a>> <<a href="mailto:b75f78d70802181146o132bb2e7qed8295bb4f23c4b9@mail.gmail.com" target="_blank">b75f78d70802181146o132bb2e7qed8295bb4f23c4b9@mail.gmail.com</a>><br>
Message-ID: <3ce57158aafa624d86cd6492f2e46b01@localhost><br>X-Sender: <a href="mailto:andrei@tanas.ca" target="_blank">andrei@tanas.ca</a><br>Received: from <a href="http://192.168.1.201/" target="_blank">192.168.1.201</a> [<a href="http://192.168.1.201/" target="_blank">192.168.1.201</a>] via <a href="http://vhost.unchanged.net/" target="_blank">vhost.unchanged.net</a><br>
[<a href="http://206.248.136.31/" target="_blank">206.248.136.31</a>] with HTTP/1.0 (POST); Mon, 18 Feb 2008 15:05:16<br> -0500<br>User-Agent: RoundCube Webmail/0.1b<br>Content-Type: text/plain; charset="UTF-8"<br>
Content-Transfer-Encoding: 8bit<br><br><br><br>On Mon, 18 Feb 2008 13:46:26 -0600, "Robert Johnston" <<a href="mailto:anaerin@gmail.com" target="_blank">anaerin@gmail.com</a>><br>wrote:<br>
<div>> On Feb 18, 2008 1:34 PM, Kevin Kuphal <<a href="mailto:kkuphal@gmail.com" target="_blank">kkuphal@gmail.com</a>> wrote:<br>>> Stable or usable? I'm very curious once the playback gets implemented<br>
<br></div>Stable and usable.<br>
<div><br>> what<br>>> happens on a Windows frontend if you have the nVidia PureVideo (read:<br>> $$)<br>>> drivers installed. If that ends up providing maximum acceleration from<br>>> video card hardware, that could be very interesting indeed.<br>
><br>> As the nVidia PureVideo drivers use DirectShow Codecs/Filters to know<br>> what/where/when to accelerate, and Myth isn't using DShow, Myth would<br>> see no benefit whatsoever from PureVideo (Or AVIVO for you ATI fans<br>
> out there).<br><br>> I believe it would take a major architecture change (Which would also<br>> break Myth on every other platform) to implement DShow in<br>> MythFrontend.<br><br></div>I don't believe it would either require a major architecture change to use<br>
DShow decoders and video rendering, but it is a major task.<br><br>Currently CPU usage is about at the same level as Linux version with<br>xv-blit renderer, NTSC content (720x480, 6MBps) causes less than 10% CPU<br>utilization 720p playback uses 70% of a single core of my Core2 Duo.<br>
<br>Several things are still missing: I have not tried to figure out whether<br>it's possible to access the same video folders that Linux frontends use<br>after "storage groups" have been implemented.<br><br>
Some features definitely don't work: DVD playback (although DVD ISO images<br>play perfectly), CDDA in mythmusic, multichannel audio (though it should be<br>fairly easy to implement), to name some.<br>
<div>
<div></div>
<div><br><br>_______________________________________________<br>mythtv-dev mailing list<br><a href="mailto:mythtv-dev@mythtv.org" target="_blank">mythtv-dev@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</a><br>
</div></div></blockquote></div><br>