First, I want to say that the new QCTools report generation is amazing. I did a 400 minute capture, creating an MKV with timecode, WebVTT, MP4, Framdemd5 and QCTools report concurrently with no dropped frames. The QCTools report took 38 minutes to finish generating post-capture, which isn't nothing, but is less than 10% of the runtime of the capture. I think this is a total gamechanger, thank you!
The issue that I've noticed is that the new QCTools report for these long files are somewhat weird. I consider this an edge case because more tapes are not this long, but it's worth mentioning. Here's a rundown:
If I try and open the mkv report for a long file while it is co-located next to the mkv pres file QCTools says the file is invalid or not supported. If I move the mkv report to it's own folder it opens fine, taking about 13 minutes to fully load the data. If I export a xml.gz report from the loaded data and try to open that while co-located with the mkv pres file it opens immediately.
Just for context, a co-located mkv report for a 120 minute mkv pres file opens and loads the data immediatley.
I wouldn't consider this a blocker at all, but it may be worth investigating in future iterations. I'd love to see if anyone else can replicate these issues.
First, I want to say that the new QCTools report generation is amazing. I did a 400 minute capture, creating an MKV with timecode, WebVTT, MP4, Framdemd5 and QCTools report concurrently with no dropped frames. The QCTools report took 38 minutes to finish generating post-capture, which isn't nothing, but is less than 10% of the runtime of the capture. I think this is a total gamechanger, thank you!
The issue that I've noticed is that the new QCTools report for these long files are somewhat weird. I consider this an edge case because more tapes are not this long, but it's worth mentioning. Here's a rundown:
If I try and open the mkv report for a long file while it is co-located next to the mkv pres file QCTools says the file is invalid or not supported. If I move the mkv report to it's own folder it opens fine, taking about 13 minutes to fully load the data. If I export a xml.gz report from the loaded data and try to open that while co-located with the mkv pres file it opens immediately.
Just for context, a co-located mkv report for a 120 minute mkv pres file opens and loads the data immediatley.
I wouldn't consider this a blocker at all, but it may be worth investigating in future iterations. I'd love to see if anyone else can replicate these issues.