This gets us no closer to solving the problem of a viable default video player, though, unless we want to shift KMPlayer into tde- multimedia.
Merging kmplayer is worth a discussion, unless we fix kaboodle with nominal effort and pain. We're no longer in the 1990s --- we really do need a working default video player these days.
We have two hurdles with kaboodle:
Broken in R14. I can play audio files with some user accounts and can't start kaboodle at all with other accounts. Probably something at my end, but consistently I can't play videos.
The supported video formats are few and they are both early generation versions. Yes, both. As far as I can tell the only supported formats are early generations of AVI and MPG.
I filed bug reports against both issues.
Darrell
longterm kmplayer/smplayer/mplayer/mpv user here chiming in.
The advantage with kmplayer is manyfold
1) we only maintain a wrapper GUI, which means new changes to mplayer are simple to handle 2) mplayer supports a plethora of codecs 3) mplayer supports a plethora of video output drivers (gl, vaapi, xrender, etc) 4) supports our native playback engine, arts 5) less to maintain, lots of benefit from upstream development 6) mplayer has a large and active user/development base. 7) all distros support mplayer in one form or another
seems like a good idea to have it as a default
On 4 February 2014 19:15, Darrell Anderson darrella@hushmail.com wrote:
This gets us no closer to solving the problem of a viable default video player, though, unless we want to shift KMPlayer into tde- multimedia.
Merging kmplayer is worth a discussion, unless we fix kaboodle with nominal effort and pain. We're no longer in the 1990s --- we really do need a working default video player these days.
We have two hurdles with kaboodle:
Broken in R14. I can play audio files with some user accounts and can't start kaboodle at all with other accounts. Probably something at my end, but consistently I can't play videos.
The supported video formats are few and they are both early generation versions. Yes, both. As far as I can tell the only supported formats are early generations of AVI and MPG.
I filed bug reports against both issues.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 02/04/2014 06:49 PM, Calvin Morrison wrote:
longterm kmplayer/smplayer/mplayer/mpv user here chiming in.
The advantage with kmplayer is manyfold
- we only maintain a wrapper GUI, which means new changes to mplayer
are simple to handle 2) mplayer supports a plethora of codecs 3) mplayer supports a plethora of video output drivers (gl, vaapi, xrender, etc) 4) supports our native playback engine, arts 5) less to maintain, lots of benefit from upstream development 6) mplayer has a large and active user/development base. 7) all distros support mplayer in one form or another
seems like a good idea to have it as a default
I like mplayer -- but after testing all the video players we have in TDE, there is something wrong with 'k'mplayer. For some reason it seems 'orders of magnitude' slower than mplayer, xine, and kaffeine. I don't know why, but it is. mplayer, which launches full screen, plays fine, kmplayer on the other hand runs in slow motion -- badly.