Or we could add a command line option to gopdit to read directly from the database? If only I had time... :-(Doesn't seem like it would be all that difficult. In the interim, I think it'd be easier to do a 2-step process... convert a myth cutlist to a "normal" cutlist, then import it into gopdit. I'm not really excited about requiring gopdit to use the database... more integration means more house of cards..... keep it simple.
I also do all of my "processing" offline. My mythbox is at home, un-networked, and no burners or much HD space. I bring .nuv/.sql files into school where my real machine is to process/burn, so reading .sql files directly is a less integrated approach.
Of course, once the functionality is rolled into MythTV, it's a nonissue. Basically, if this could be done well, a "lossless transcode" right from MythTV would actually *delete* the original file. Then the resulting .nuv would already be ready to roll.
-Cory
************************************************************************* * Cory Papenfuss * * Electrical Engineering candidate Ph.D. graduate student * * Virginia Polytechnic Institute and State University * *************************************************************************
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
