Hi! Ralph Glasstetter wrote:
[batch TS->PS conversion] > As CLI and without demuxing I only know of "replex", but that's no option > under windows (or is there a port? should not be to difficult...)... and > "ffmpeg" produces very strange output (at least the first few seconds are > missing.... if not the file is totally corrupted). I used to use my own tool for that. Linux based as well, of course. Nowadays, I cut TS directly and don't bother with conversion any longer. It's a two-edged sword anyway. >>>The good thing is that now no more project file is needed, since if no >>>START/STOP markers are known to dvbcut everything (except the last frame) >>>will be exported! >> >>Does that work with multi-file sources already? > > > Yes, of course... That's what you thought ;-) I also had to change the -batch option because it didn't accept multiple filenames. Your patch just went in, by the way. >>>for instance to give the path to the index file or to supply multiple >>>filenames or to specify the location of the export file (a patch Sven >>>hopefully will commit soon... would be nice if he also could add a >>>-expfile CLI switch... ;-)) >> >>Shouldn't be a problem to add that option. No need to bother Sven. > > Sven told me yesterday that he needed that option and implemented it already, > i.e. to specify <expfile=...> in the project file... What is it good for, except causing trouble? :-( I already have trouble enough with the absolute paths in *.dvbcut. You can't even move a project (both source and *.dvbcut files) into another directory because dvbcut will just say no, err, "file not found". Nor can I use files on a NAS or other external storage device, set the markers from one host and run the export on another one, unless the NAS is mounted at the same directory on both machines (which is not always possible). Besides that, the typical workflow is like this: - load and index source file(s) - set markers - save project - export Often I process a number of movies in sequence, without exporting them at all - because it's much more convenient to run the export in batch mode afterwards (while you're already doing something else). Therefore, when you save the project file, the name of the export file may not yet be known. So what's supposed to be written to the project file? > I just thougt that a > CLI switch would also be nice, because at the moment one has to call "dvbcut > -batch" from the position where one wants to have the output file. A CLI switch would not only be nice, it's the way to go. For batch mode, that is. >>But I don't think that specifying the export file name inside the >>project file is a good idea. > > Why not, it's the best way when you want to generate a project file by some > automatism for batch cutting! Until the program overwrites a file for the first time because its name was hardwired in the project file. No surprises, please. -- Michael "Tired" Riepe <[EMAIL PROTECTED]> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
