Am Sonntag, 24. August 2003 18:29 schrieb G�tz Waschk: > Am Sonntag, 24. August 2003, 15:30:50 Uhr MET, schrieb Steffen Barszus: > > I have rechecked the last 0.91 mplayer package and mplayer gui is > > still using "default" as default skin. Since the beginning of june > > the theme "blue" is the default skin for mplayer. Could the skin > > package be updated please and the new default theme set aprroriate > > ?. > > The skin package was updated to include the Blue theme. But it's not > the default skin, as I haven't changed the default mplayer.conf. If > you think this is wrong, als the MPlayer developers at the > mplayer-users list.
Ok so i recheck it. Maybe i have missed it and i will ask them to change the default mplayer.conf to reflect their own decissions. Afzer all it wouldn't have much affect on your package, so could you set blue as default ? Its a lot nicer and has more functionality then the old default skin. > > I would further suggest to take out fullscreen and cache from the > > default configuration, but we had this discussion allready ;) > > Yes, I'm against that as I think the defaults from the MPlayer > developers are reasonable. Ok didn't get that it are defaults from mplayerhq > > BTW orange and krystal is missing two in the skin package as far as > > I can see. > > I don't want to include ALL skins available, but I could throw out > the more ugly ones to include the better looking skins. Please get > the latest mplayer-skins package and check it first. Will do so, i just thought that it would be good to have the top three ones from mplayerhq skin contest in the skin package. > > BTW2: mjpegtools 1.6.2 will be released soon as far as i can tell. > > I'M using the cvs version and can tell that it works really well. > > Next week is a version freeze, so I guess it's too late :-( Maybe we > could make an exception, so could you please test all the apps that > use mjpegtools? The apps I use work unproblematic. Namely this are kimg2mpg and tosvcd. If someone using transcode usually could test that .. but i wont touch transcode as i don't know anything about transcode (have never used it) . The only problematic things i have seen on mjpeg mailinglist is compilation problems on altivec-code. The release is a minor release. What make it so much better is, that you can choose now different matrices (kvcd, tmpgenc, the standard ones and own load from a file). For svcd creation this gives you a big quality boost as the bitrate doesn't hit the maxbitrate so fast. A pitty that it comes so short after version :(. What i can offer is to test the things i can test. So if someone other then me can test transcode .... Greets Steffen
