You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tens of thousands of episodic prores files on S3 (AWS). Some have caption tracks which are taking 20-30 minutes to run. Is there a way to ignore the caption track when running Mediainfo? The files without caption tracks return results in <1 second.
Thank you!
The text was updated successfully, but these errors were encountered:
morganbitpress
changed the title
Very slow performance (many minutes) doing an interrogation of a mov file with a 608 caption track
Very slow performance (many minutes) doing an interrogation of a mov file on s3 with a 608 caption track
Feb 28, 2025
Some have caption tracks which are taking 20-30 minutes to run.
When having a caption track, we probe in the middle of the file for catching if there is real caption content.
It is normal that it is longer, but not normal that it is so long.
Is there a way to ignore the caption track when running Mediainfo?
There is something more or less similar, we implemented a feature permitting to set the duration of the caption probe but we didn't implement it with "no caption probe" in mind, we need to check if it work with "0" and/or tweak it a bit (handling "0" as "no caption probe" without any seek.
You may try some low values in order to reduce the count of seeks and byte read, but no commitment that it will work.
Willing to sponsor the change if the price is right!
Please drop us a message and we see, but I don't see a high duration for a development (and we invoice per hour of dev) if it is about checking / tweaking an already existing feature.
Hi,
I have tens of thousands of episodic prores files on S3 (AWS). Some have caption tracks which are taking 20-30 minutes to run. Is there a way to ignore the caption track when running Mediainfo? The files without caption tracks return results in <1 second.
Thank you!
The text was updated successfully, but these errors were encountered: