Page 1 of 1

Request: New ProjectX cutlist type

Posted: Tue Oct 05, 2010 5:46 pm
by mcb7
Hi,

I've seen various discussions about the use of comskip and ProjectX and it seems there was not really any resolution on the output format. E.g. viewtopic.php?f=5&t=534&hilit=+projectx

There seems to be quite a lot of good reasons to output the cut points in byte position i.e. Mode (0):
* They can be easily imported to ProjectX and viewed
* They can be used for all types of output action (demux, remux, etc), whereas frame pos only works for demux output (and ProjectX support are not likely to change this).

Hence here is a request to maybe add or modify the ProjectX output option in comskip to use byte position.

BTW, I noticed that the mencoder .edlx output type seems to be using byte position, so I'm guessing just a reformat of that output type would be possible.

Thanks

Re: Request: New ProjectX cutlist type

Posted: Tue Oct 05, 2010 6:35 pm
by erik
edlx outputs the byte position of the nearest GOP
would that be ok?

Re: Request: New ProjectX cutlist type

Posted: Wed Oct 06, 2010 10:48 am
by mcb7
Yes, I guess. I manually converted an edlx output and it worked just great. You may already know this but just in case, as ProjectX cut points are opposite logic to the edlx ones (i.e. include rather than exclude), some slight translation was necessary:
edlx:
<regionlist units="bytes" mode="exclude">
<region start="0" end="32818172"/>
<region start="308533144" end="412971468"/>
<region start="696839248" end="803011872"/>
</regionlist>
ProjectX:
CollectionPanel.CutMode=0
32818172
308533144
412971468
696839248

i.e. first "start" and last "end" are not needed.

I guess the best option here would be to add this feature as an addition to the existing ProjectX output in case someone has code relying on that format.
Thanks.

Re: Request: New ProjectX cutlist type

Posted: Wed Oct 06, 2010 11:09 am
by erik
Will put it on the todo list