Jeff Hyche wrote: > On 06/29/2006 06:39:47 PM, Phil Ehrens wrote: > >Joe Emenaker wrote: > > > >His script is very naive, and is not what you want. However, since > >he went to the trouble to write this script, and learned quite a > >bit about transcode and video encoding in general in the process, > >I thought we might very gently walk him through making his script > >more generally useful, if he cares to do it. It's possible that > >within a couple of days his script will be able to do what you > >want ;^) > > > > > > Well I woudldn't call it "naive." That would be to generous. I would > call it dumb as a brick. There is really no error checking at all. If > something blows up the whole script blows up. It does one thing and it > seems to do it well and that is convert VOB's to xvid avi's.
In this context, naive is a technical term, not a put-down. It just means that it makes no attempt to validate input. It refers to the action of the script, not the code. I never find myself operating on VOB files, but I see a lot of people do. I thought that most people who were working with VOB's had them as the product of using a video capture device. Are you ripping from VHS? There may be a better strategy to use on your rips. > That is why I posted it to get feed back on the next level involved. > Once I figure out which direction to row in I want version 2.0 to > handle all the codecs that transcode can handle. There are a lot of dark corners in video (no pun intended). Some of them are documented in the transcode wiki: http://www.transcoding.org/cgi-bin/transcode If you would like to contribute to the wiki email me for the editing password.
