New VideoReDo format

[marvin-miller]

I do not have the latest version of Videoredo so I prefer to stay with the old format now its working with videoredo.

I'm not sure that it is, people are starting to report problems that look like they might be tracked back to the .vprj format issue (again).

You asked me to contact the folks at VideoRedo to get information about the 'new' format so that we could put an end, once and for all, to the .vprj issues. They kindly did that (and spent time changing code) in an effort to help ComSkip with compatability. I think that was pretty good of them

I think it would be a lot smarter to revisit this issue now, and finish it once and for all, while it's fresh in everyone's mind.

That way it can be fixed permanently and never crop up again - make sense?
At least, I thought that's what all of us were doing?

You I think you can find a time-limited beta here => http://www.videoredo.net/beta/VRDTVSH26 ... 7-634d.exe

[erik]

Will do, thanks

[erik]

Implementing now

could you check to see if instead of

<cut Sequence="2" CutStart="00:00:05;10" CutEnd="00:00:20;16" Elapsed="00:00:02;01">
<CutTimeStart>54000113</CutTimeStart>
<CutTimeEnd>206400112</CutTimeEnd>
<CutByteStart>4652532</CutByteStart>
<CutByteEnd>17301504</CutByteEnd>
</cut>

its also ok to use

<cut>
<CutTimeStart>54000113</CutTimeStart>
<CutTimeEnd>206400112</CutTimeEnd>
</cut>

As the sequence and human readable time parts seem to be comment

[erik]

The new output is

<VideoReDoProject Version="3">
<Filename>S:\erik\work\streams\Fa.mpg</Filename><CutList>
<Cut><CutTimeStart>0</CutTimeStart> <CutTimeEnd>1030800000</CutTimeEnd> </cut>
<Cut><CutTimeStart>12491600000</CutTimeStart> <CutTimeEnd>16316800000</CutTimeEnd> </cut>
<Cut><CutTimeStart>35762800000</CutTimeStart> <CutTimeEnd>39879200000</CutTimeEnd> </cut>
<Cut><CutTimeStart>58241200000</CutTimeStart> <CutTimeEnd>61776000000</CutTimeEnd> </cut>
<Cut><CutTimeStart>77554000000</CutTimeStart> <CutTimeEnd>78256000000</CutTimeEnd> </cut>
</cutlist></VideoReDoProject>

Videoredo needed

<MPEG Stream Type>4

Where and how to put this in the new format?

[marvin-miller]

Videoredo needed

<MPEG Stream Type>4

Where and how to put this in the new format?

The stream type is determined automatically, so it shouldn't be necessary to add that any longer.

[erik]

Then if the format below is OK, that is without the human readable times then I'm done implementing and it will be available in the next release. To be released after some testing this weekend

[marvin-miller]

Then if the format below is OK, that is without the human readable times then I'm done implementing and it will be available in the next release. To be released after some testing this weekend

The format below?

If you like, post up a completed sample and I can ask the folks at VideoRedo to check it over? It's up to you

[marvin-miller]

Never did see that format below (from above ) but I am getting errors with the new videoredo output format.
I tried opening the .vprj file directly and got this error from VideoRedo;

Videoredo
Video Program Stream not Found
Unable to open file .....

So I think your format is still a little messed up. Maybe you could ask the folks at VideoRedo directly? It's probably a very simple thing

[erik]

I posted a question at their forum

[erik]

I think I see the error
Can you edit the vprj file and replace
</cutlist> by </CutList>

[marvin-miller]

No dice

[Gripweed]

No dice

So, you are saying that the replacing of </cutlist> by </CutList> doesn't fix the problem? The happy face is confusing me. It really doesn't matter anyway because my VAP is setup for automatic processing. I'm not going to use a new Comskip if I have to manually edit all my vprj's.

[marvin-miller]

I think you might be confused
No, you won't have to manually edit your .vprj files - we're testing

[Gripweed]

Ahh, that sounds more promising. I'm eager to combine the new VRD beta with the new format vprj Comskip.

[marvin-miller]

I'm starting to wonder if it's worth changing. The folks at VideoRedo kindly changed the code to support the old-style logs generated by ComSkip so it works at present with the latest VideoRedo beta.

Maybe we're just chasing down something that's not worth the effort?

What do you think Erik?