Thread: Request: TCPMP
View Single Post
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#6
Originally Posted by iliaden View Post
maybe.
No, not "maybe". Fact.

Originally Posted by iliaden View Post
the only feature i want is the capacity to lower the quality of a video, making high-bitrate videos display perfectly without any conversion.
MPlayer is perfectly capable of doing this. This will give you half-resolution decoding:

Code:
mplayer -lavdopts lowres=1 <videofile>
Originally Posted by iliaden View Post
Quite honestly, I doubt that there exists a MPlayer client capable of doing so. This is why I asked for the compilation of a player that already has has this feature.
No, but the point is is that porting a whole new client is pointless, as it would be a trivial feature to add to one of the many existing mplayer front-ends. Especially when porting that client will likely involve more work to port than starting from scratch and leverages exactly none of the thousands of hours already put into optimizing media playback on the NITs with mplayer. . . .

Really, just make it easy on yourself and play your videos from xterm with the command I gave you above.

Originally Posted by mudhoney View Post
Also, of course, it can scale a high resolution video down on the fly. I do believe in some way mplayer can do the things you describe, the only problem is that it probably takes CPU time to do so just like it does to convert a high quality movie down to a lower quality on any PC.
The whole idea between lowres decoding is to reduce the CPU impact by decoding less than the full frame. What you're thinking of is called reencoding, but all we need to do is decode a portion of the frame, not decode the whole frame then reencode it at a lower resolution.

Originally Posted by mudhoney View Post
As far as porting TCPMP, the challenge there would be that it's made for Windows. Which of course makes the port work a lot more difficult than most other apps ported to Maemo.
Actually, the fact that it's written for Windows is probably the easiest hurdle to jump. The real challenge is that it's designed for very different hardware and doesn't have any optimizations for the NITs.
 

The Following 4 Users Say Thank You to GeneralAntilles For This Useful Post: