Stefan Taferner wrote:
Yes, and if you use the latest vdrsync developer version, it will give you more info about the cut marks. I just hope that I am computing the total frames correctly. I assume by taking the total about of time (in seconds) and multiplying that by the frame rate would give a decent estimation. If there is a better way of computing it, pls let me know :)On Sunday 02 January 2005 22:14, C.Y.M wrote:Stefan Taferner wrote:On Sunday 02 January 2005 15:49, C.Y.M wrote:I have decided to add support for replex in vdrconvert in order to help solve the demux problem with edited vdr recordings. This patch requires[...] According to my own tests it is not enough what you did (replex -z) if you want to support AC3. But I might as well be wrong.I believe you are right. Replex should also be using the -x switch to handle ac3 streams. I have made a few small changes to the patch I just posted. But at least I am now able to demux edited recordings with large cut marks :).
I even had to manually tell replex which streams the recording has. Only specifying the -x switch crashed replex. Now my script uses
"vdrsync.pl -i" to find out about the streams prior to replexing.
I will have a closer second look by times...