When I use the gui to enable double buffering on mplayer, I get an error the next time I start that says:"Couldn't open/init audio device -> no sound!".

If I go to disable double buffering using the gui, I notice that "enable frame dropping" has also been checked. (not my myself, though.) So one would think that by unchecking all the boxes that I would get sound back, but nope. I have to delete my gui.conf file to get sound back again.

When I hit F for fullscreen, I can't get back to the desktop "skin view" again by hitting F a second time. (It used to, but not anymore) Now the screen switches to a different aspect ratio instead.

Sometimes when viewing movies in fullscreen there is a randomly-placed pixel on the movie screen that stays white. I'm not sure how to reproduce that, but it's not a real dead pixel, because I've tested my screen.

Anyone have ideas on any of this? Are these bugs that I should report? I've heard that the developers of this project are pretty tough on newbies who don't know what they're doing. I'm afraid to email them because I don't want to get what Joe Barr got.

By the way, I compiled Mplayer from source and didn't have difficulties with gcc being the wrong version or any crap like that.

ha ha ha, yeah, they can be a little rough, but take it with a grain of salt. They say RTFM like it's a replacement for "the". No worries, they mean it all to not waste their time if it's already documented.

Try posting to their mailing list if you feel the desire, and if you get alot of, did you RTFM, then you might wanna see if it's documented there.

Good luck. But your problems with the gui aren't going to get very far, as the gui is still very alpha. If you can play the same video just fine with the command line, then I don't know if I'd post it or not.

Cool

good point. I think I'll wait until they start making it sound like the kinks have been worked out in the gui.