Replies: 2 comments 2 replies
-
I don't think there is currently a workaround to avoid seeking, but it should be easy to add an option to treat the input as not seekable. The changes made recently in #9 reduced the number of read access and that might help as well - A commandline option alongside |
Beta Was this translation helpful? Give feedback.
-
I've created a PR that adds some options to speed things up: #15. I still need to do a couple of tests but if you could take a look to see if it works for you that would be great. |
Beta Was this translation helpful? Give feedback.
-
We use mxf2raw in combination with http to retrieve metadata from our MXF files, e.g.
mxf2raw -i http://webserver/path/to/file.mxf
For some files this commands takes quite long (1 - 2 minutes), while accessing the same file over a filesystem is quite fast (1 - 2 seconds). I guess, bmx is seeking in the mxf file by sending a bunch of http range requests, which just takes time in sum and we end up in waiting 1 -2 minutes.
Since this long time is a problem for our workflow, is there a way to come around this? We had the same problem with ffprobe and figured out, that setting "seekable=0" solved this problem.
Beta Was this translation helpful? Give feedback.
All reactions