[mythtv-users] easiest way to go from storage groups internal player to mplayer

Travis Tabbal travis at tabbal.net
Tue May 18 14:37:58 UTC 2010


On Tue, May 18, 2010 at 7:40 AM, Mark Kendall <mark.kendall at gmail.com>wrote:

> On 18 May 2010 21:16, ryan patterson <ryan.goat at gmail.com> wrote:
> > Is fixing these bugs a priority?  What is the proper way to submit
> > these to the developers?
>
> Yes - they are a priority, though I'm surprised to hear you have so
> many issues (I keep a sizeable collection of clips for
> testing/debugging purposes and there are currently a tiny number with
> significant issues - and those are mostly out of spec h264 files).
>
> Anyway, the best way to get these issues fixed is to create a ticket
> (http://cvs.mythtv.org/trac/wiki/TicketHowTo) and at the very minimum
> write a useful summary of the symptoms you are seeing, how to
> re-create them and attach the full, unabridged output of 'mythfrontend
> -v playback'.
>
> If there is a crash involved, try and catch a backtrace
> (http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2).
>
> If you really want it fixed, there is no substitute for making a 30-60
> second clip available for download somewhere.
>


To be completely fair, most of my prior issues with the internal player have
been resolved and it is the only one I use presently. However, I have run
into corner cases with some videos that while they may be "out of spec",
play just fine with mplayer, vlc, and xine. I also tested VDPAU vs. software
decode with similar results. The only reason I haven't created a ticket is
that I'm not on the latest code, so my ticket is less likely to be useful.
When I do upgrade to .23, I'll re-test and see what comes of it. The other
post with clarification on how external player support is to work in the
future was quite useful and I thank them for posting it. A little
communication goes a long way. It sounds like support is not being removed,
just simplified to a single external player command. That's perfectly
reasonable and as mentioned, we can use a shell script to use different
players for different files.

It would also be nice if the internal player were more tuneable. In mplayer,
I can change nearly every facet of how it works with command line options
and the config file. That is a lot of code to maintain, but a little
flexibility can make a big difference and I don't think it's reasonable to
ask the Myth devs to have quite that level of flexibility.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100518/27defcdb/attachment.htm>


More information about the mythtv-users mailing list