[mythtv-users] iPhone Frontend Issues

[Josh White]

2009/3/17 Nick F <nikos.f at gmail.com>

> On Tue, Mar 17, 2009 at 9:02 PM, Chase Douglas <
> chasedouglas.lists at gmail.com> wrote:
>
>> This leads me to the following question: Given the pros and cons of each
>> approach, what would other LIKELY users of an iPhone MythTV frontend prefer
>> to see implemented?
>>
>> Built-in:
>> * High quality (h.264 level 3 + mp3 or aac-he, full resolution and
>> framerate, high bitrates)
>> * Low battery consumption
>> * No commercial skip
>> * No extra controls (for changing channels, etc.)
>>
>> Software Decoding:
>> * Full commercial skip support
>> * Overlay controls are possible
>> * Lower quality (though still very acceptable)
>> * Very high battery consumption
>>
> As an iPhone user - I'd love to see a frontend for it.  I'd vote for the
> 'built-in' decoding though and sacrifice the comm skipping and extra
> controls.  The quality, battery life (and stability?) using the apple player
> swing it for me.
>
> (Thanks in advance for doing this!)
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
I'll second the vote for the Apple player using the hardware decoding.  I'd
rather have a partially featured system that worked well, looked good, etc.
The other approach would be cool to play with, and probably a more
interesting project, but in the end, it wouldn't be all that usable if it
killed the battery quickly.  If you really wanted commercial skipping, you
could incorporate that into the transcoding part on the backend.   It
wouldn't be perfect, but it'd be better than nothing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090317/76e20c13/attachment.htm>