Mplayer has been my favorite video player for a long time. I found that it handles audio much better than VLC, while providing the same great support for video. I’ve never found a file that caused Mplayer to glitch. Okay, that’s actually not completely true. easy process. I recently compiled the latest version and it easily gobbled up the file which gave the old MPlayer for OSX some trouble.
It was mostly from my laziness that this latest program has sprung up. I didn’t feel like opening the Terminal and pathing out the file to my video file every time I wanted to view a video. But I also wasn’t willing to settle for the two-month old build of MPlayer OSX Extended. It’s probably my own fault that I’m not willing to deal with a slightly outdated version of a program which works just as good as the latest thing, and so I figured it was only right that I solved the problem myself. I did just that by developing a quick frontend for Mplayer for this week’s project.
I have been doing iPhone development up until now, but it is pretty much the same exact thing as Cocoa development (that is, the framework for Mac desktop applications provided by Apple). This week’s program really didn’t fit iPhone (I think there actually is an Mplayer port for iPhone, but I’m not trying to drain my battery faster than 3G data access), so I went with Cocoa instead.
I was a little rusty with Objective-C since it’s been almost three weeks since I did an iPhone App. That said, I was able to code the frontend in little time at all. It didn’t take more than 90 minutes, thanks mostly to the great description of NSTask at Cocoadev. It’s example was pretty much exactly what I needed to launch the Mplayer process from a Cocoa application. After that, I just had to meddle a little bit with NSMutableArrays to get the few options passed to Mplayer, and it was done.
Click here to download the source code for this week.
Note: I would include a binary, but I feel like it’s pointless considering I am running Snow Leopard and therefore only those with 10.6 or higher would be able to use it. Also, the path to Mplayer is hard-coded into the application, so you might need to change that and recompile anyway.
I’m not going to lie, Cocoa makes it VERY easy to make a frontend for a command-line application. I won’t hesitate to use it again for this purpose. On a completely unrelated note, it seems the rule I made for myself that I cannot ever skip a language environment more than twice in a row works well. If I had gone any longer without firing up XCode, I expect I wouldn’t be able to remember the difference between an outlet and an action. It’s really sad how poor my memory is with programming languages, but I suppose I can’t really complain. I just need to work extra hard to keep myself up to snuff.