On 8/8/05, J. Donavan Stanley <[EMAIL PROTECTED]> wrote: > Why the hell should Myth care is mplayer can play it's files or not?
It's like using the newest MS codecs with WMP and saying why the hell should I care if anyone else on any other OS can play my files. It's just a fact, you won't absolutely be able to run (the real, not the mpeg2) *nuv files on any normally configured OS, not just one, not to mention standalone players. > Myth can read and playback AVIs just fine. It just doesn't create > them. (because the container sucks ass) But why do you always compare nuv with the worst container on this planet? There are lots of really good and also commonly used and supported containers like mp4, ogm and matroska in particular (Container comparison: http://en.wikipedia.org/wiki/Container_format or more information about Matroska: http://www.matroska.org/technical/guides/faq/ and http://en.wikipedia.org/wiki/Matroska) > > How hard would it be (and are there any reasons no to) modify the code > >such that it will generate more friendly mpeg4 files? > > > > > There are lots of reasons why not to change. The least of which is "It > ain't broke". Sure, "it ain't broke" but I'm now quite happy to use DVB-generated "nuv" instead of the real nuv mpeg4/rjpeg format. > >My personal goals are to : > > - remove the DB dependance for generated files > > > There isn't a DB dependence for generated files. I dropped my mythconverg db by accident lately, now all entries in the MythGUI are gone althought the files still all exist. So there is a db dependance (you'll at least lose lots of information about the files when you accidently delete your db). Adam _______________________________________________ mythtv-dev mailing list mythtv-dev@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
