New VideoReDo format

[erik]

I requested feedback on the output format at the videoredo forum and I did not get a reply yet.
If people can use the newest videoredo with comskip output anyway then there is no real problem I assume?

[marvin-miller]

Basically, yes. I was under the impression that you would have to tweak your .vprj output to make it work but I haven't had an issue yet - even if the .vprj output is not 'optimal' it seems to me to be fine. I've processed +/- 100 shows with no issues so perhaps it's a non-issue

[erik]

Which format do you use to process these shows?
The version 2 or the version 3 format?

[marvin-miller]

The original, version 3 (the new attempt) fails each time

[dlflannery]

I see this in the version announcements thread:

Changes on 0.81.033
- Repaired the broken edlx output format
- Added output_videoredo3 parameter for ini file. Set to 1 to get type 3 videoredo output. Make sure to enable only ONE videoredo output format as they have the same name and one will overwrite the other.

When VAP launches Comskip, it automatically adds the -videoredo command line argument. Does the above change mean there will be a conflict if a user has inserted the output_videoredo3=1 line in his .ini file? (It would be nice if the statement in the .ini file overrides the command line option.)

[erik]

The only possible problem is that the chapters information is added in a version 2 compatible format a I do not know how to add in version 3 format.
Will think on how to solve.

[dlflannery]

The only possible problem is that the chapters information is added in a version 2 compatible format a I do not know how to add in version 3 format.
Will think on how to solve.

Hmmm... Just to be clear: If I launch Comskip with the command-line argument -videoredo and also have "output_videoredo3=1" in the comskip.ini file, there will NOT be problem with it trying to write both type 2 and type 3 videoredo project info into the same file name, correct?

[erik]

No,
as both files have the same filename extension I can not write both.
Its either one or the other.
For the moment there is actually no reason to write version 3 files as the new videoredo can read version 2 files.

[junzi]

Is there a resolution to the OP? I am having the same problem.

Comskip: Donor Version 0.81.037
VideoReDo: VRDTVSH264-4-20-7-629d.exe

I am unable to open the .VPrj file created by Comskip in VideoReDo.
I created the .VPrj file through command line \comskip -w --ini=<myfile, videoredo enabled, volume_slip=150>
Message says "No Audio Stream Found" for both .wtv and .ts files.

.wtv H.264 1080i generated by WMC7 using Hauppauge HVR-2250 tuner
.ts H.264 1080i files from Hauppauge Colossus capture

note: I changed the volume_slip levels as per the changelog.

Can anyone help? I would like to create .VPrj with comskip that open in VideoReDo.

----------
*Added:

the .VPrj file created by comskip is the following on a small sample .ts file in SD...it looks very different from the project file created by videoredo. Can videredo use this file?

<Version>2
<Filename>C:\Users\virg\Desktop\prac\twz.ts
<VideoStreamPID>65
<AudioStreamPID>68
<SubtitlePID1>0
<Cut>696028667:999331667
<Cut>3214544667:6322649667
<SceneMarker 0>695361333
<SceneMarker 1>998998000
<SceneMarker 2>3213877333
<SceneMarker 3>3264594667
<SceneMarker 4>3365362000
<SceneMarker 5>4282945333
<SceneMarker 6>4318647667
<SceneMarker 7>4559888667
<SceneMarker 8>5762089667
<SceneMarker 9>6322649667

------
The log file does not appear to have any obvious failure problems, but the last line states:
Search step failed, error too big: target = 0.000, pos = 632.365

I do not see a way to attach the log file; I can post it if that helps.

[dlflannery]

The problem is the version of VRD. Update to the latest beta, build 637g:

http://www.videoredo.net/msgBoard/showt ... hp?t=24328

[junzi]

Thanks dlflannery! That fixed everything!

Love the beta VRD GUI--sleek and fast...now it's on to getting proficient at VAP! I'm loving this! What have I been doing all these years using a DirecTV DVR like a dummy!

erik: please update comskip readme to include that comskip donor version 0.81.037 only works with VRD beta 637g (as of today). I will also pm you b/c that would have saved me many hrs! Thanks!

[cocoa117]

I am currently using TVSuite V4 4.20.7.646a, and it seems not happy with comskip project file again. It gives error message can't find the video stream error.

[marvin-miller]

I'm using the latest VRD version (whatver beta is the latest) and I'm not seeing any real issues yet. I always get the odd error but generally this is due to the QSF procedure and it doesn't happen often.

[cocoa117]

I'm using the latest VRD version (whatver beta is the latest) and I'm not seeing any real issues yet. I always get the odd error but generally this is due to the QSF procedure and it doesn't happen often.

Hi, Can I ask what quality of show did you used on? I was trying with h264 codec, HD shows. As far as I can remember, the SD show seems fine with MPEG2 codec. Is that the case with you as well?

[marvin-miller]

Hi, Can I ask what quality of show did you used on? I was trying with h264 codec, HD shows. As far as I can remember, the SD show seems fine with MPEG2 codec. Is that the case with you as well?

I'm recording with a Hauppauge Colossus which is H.264. It's set at the highest bitrate it supports and because I'm using Windows Media Center 7 it's in the .WTV container. 99% of what I record is 1080i HD.

What I have found is that once in a while the recordings get mangled. It's rare but when this happens VRD can't do a QSF and it fails. If the recordings are viable I just turn off QSF on those files. It doesn't happen often. It's probably the driver for the Colossus when that happens.