Comment 2 for bug 1690619

With all due respect I think when you write "me-tv isn't designed/intended to watch, record, rewind or pause LIVE tv." you misunderstand the request and the use case somewhat and are misrepresenting simple design as well.

Currently, if you run Me-TV and start a station playing, that's it, consuming GPU/video resources and producing sound without any ability to stop it short of quitting the app. If it's not designed to watch TV then my mind is literally blown away a little, I read no-where in the process of trying it out and did not divine anywhere in the UI that its primary intent was your use case of quietly scheduling recordings. Now as a TV viewer, I can of course mute my PC great, but while watching something will commonly want to stop the playback, cut the sound and resource consumption while something else needs to be done. Then come back and continue watching.

In this use case, you have to quit, restart, find the station again and start it. All way weird when every single video app ever encountered has a way (a pause or stop button) which leaves you in the app but playback is stopped. Such a button is a simplification of experience, no overhead on layout (a super familiar button) and its absences has nothing obvious to do with simplification of anything not even layout.

But sure, if I find something else that plays back better, off I got. Because this lacking feature is a showstopper for, more or less. More or less because I don't actually watch TV (who does anymore?) and put a TV receiver and played around with TV for my wife alone who had one show per annum in mind that she's watching and preferred on the free to air version to the streamed version fro some reason ;-).

If anything kills development on Me-TV and related products it'll be the obsolescence of TV itself. But that said, I'd much rather hear from a developer (about the minimal effort to add a stop button as opposed to rather serious effort for me to find the source assuming it's open source, build it, get my head around the GTK or QT code and add a stop button to my own fork ... which is more effort than I'll give it for now, but if I were geared up fro a project like this, such a button is a small job, and I'd love to hear the arguments against it, not having been won over one jot by the argument of simple interface - as the use case outlined points out, it's more complex without it, not more simple).