Create cut ranges in output video after processing to examine it

kodidok

New member
The more i use VideReDo TvSuite the more amazed of it I am. Congratulations!


The whole concept of my idea is the easiest possible way to check whether created file is produced as intended - in terms of:

- cut points - are there some extra unwanted frames kept or maybe unexpected sound in the beginning of the part so i can go back cut more frames and do processing once again
- and broken parts - sth not recorded very well and how VideoReDo handled it, does it look OK, or it is better to record it once again

Currently to do that i can open second instance of the VideoReDo and check the cut points looking for them manually and check in log where is sth broken if report suggests there was a problem. It takes time so I request for the feature described below:

In the report you have OK with arrow option Open file in VideoReDo. I'd go even further! I'd request to open file with VideoReDo with predefined cut points and points with broken parts.

I think we can assume it is enough to see from 1 second before cut point/broken part to 1 second after that point. It could be configured manually.

I'll illustrate an example.

If there was something cut off from the beginning of the input video initiate "green" cut range from 00:00:00.00 to 00:00:01.00 (if we set 1 second as a range) automatically

then we have cut points from input video at 00:20:11.19 in the output file
so let VideoReDo create "green" cut range from 00:20:10.19 to 00:20:12.19

then we have sth broken about 00:23:57.17
so let VideoReDo create "green" cut range from 00:23:56.17 to 00:23:58.17

and next cut point at 00:32:10.07
so let VideReDo create "green" cut range from 00:32:09.07 to 00:32:11.07

all ends at 00:45:20.04; if it was not the end of source video so it was cut by VideoReDo
create last "green" cut range from 00:45:19.04 to the end

Then Toogle Preview mode automatically so everything is prepared to be checked manually in fast, clean and simple way.

This will make this great tool even better.
 
Last edited:

Dan203

Senior Developer
Staff member
Unfortunately that is not as simple as it appears. Internally we open the file, separate it into it's elementary streams, process each stream individually using a chain of modules each with a specific job, then finally mux it all back together. The timecodes used in the final output don't exist until that muxing part, but the errors are reported by the individual modules upstream that are working on the elementary streams. There is no easy way for us to correlate the detected errors in the source streams with their final position in the output file. As an example say you have a file with an error that is detected in the splitter portion of the code. That code has no idea if or where you're cutting, so that error could potentially be cut out or offset by one or more cuts that come before it. Best we can do is dump the error to the log and keep reading.

Now maybe it would be possible to devise some complex system that tracked every single frame and errors in surrounding frames, but it would be a lot more work than the feature would provide benefit.

Your best bet if you run into this a lot is to quickstream fix the files before you edit them. This will correct most errors ahead of time and then your cuts should be perfect.
 

kodidok

New member
I see.

In case of errors I was thinking at least about AC3 errors I've found in logs, it usually appears to be indication of bad but not terrible moment with also potential video issue in the same timestamp to check. It could be counted where approximately it appears and put it in higher range like ±3 seconds instead of 1 second like in cut points. The problem would be the question do we have somewhere broken video for more seconds...

The only wish I'd have is to get option to preview cut points in newly opened output file as described above only in case no errors are detected (and obviously if there are any cuts). Timestamps can be counted from source file cut points, be simple to implement, and pleasure to use.
 

kodidok

New member
I've realized that opening produced video replaces source video in the same window when choosing that option in report.

I was thinking about running preview in 2nd instance (or to support tabs in this case) so you can switch between source and output and easily, apply corrections to the source if needed, and process it again (with intelligent recode it can be fast worth doing if you intent so).
 

Dan203

Senior Developer
Staff member
There shouldn’t be a discrepancy between the cuts you make and the final output. Is that what you're seeing? If so please contact us at support so we can get a sample from you and figure out why. That would be a huge bug.
 

kodidok

New member
After having bigger sample size and learning some patterns I also come to conclusion that was very minor thing so never mind. I had some issues but it looks like it was matter of detecting type of frames...
 

Dan203

Senior Developer
Staff member
You shouldn’t have to pick frames. Unless you're using GOP editing mode it should be 100% frame accurate. If it's not please let us know.
 
Top Bottom