-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't process MXF file / interval (-2305843009213s) is way to small / New Windows binaries #44
Comments
Strange, can you run ffprobe:
I've successfully tested: mt Version 1.0.11
Maybe you could try the sample file as well? might be a unsupported codec inside the container or something like that. Sadly my server i used to create Windows builds on did die a while ago and i didn't find the time to set up a new one. If installing a wsl subsystem is an option you could try that (most likely easier than compiling from source) but you should be able to compile it from source on windows as well given that you'll have a gcc compiler available. I cant tell you anymore than that since i don't have a windows system myself. Basically what you'll want to do is:
|
Your linked sample file works. The mxf files I'm talking about work after passing them through ffmpeg or using the latest mt version (on Linux).
I ended up building ffmpeg and subsequently mt from source and thanks to https://github.com/m-ab-s/media-autobuild_suite it wasn't actually that hard... took a couple of tries but it worked out. I needed to remove libopenh264 as mt complained about missing dll file, so dll file needed to be next to it. After compiling ffmpeg without and rebuilding mt, it worked fine. For anyone wishing to build a windows binary
Once ffmpeg build is completed successfully, download and unpack mt, open a MinGW shell (MinTTY shortcut in media-autobuild_suite folder), and change to the above unpacked folder. Proceed as in mt docs:
If your ffmpeg compilation folder was mt.ext should be built after some time :-) |
glad you got it working and thanks for sharing the build steps for windows :) |
mt version: 1.0.11
OS: Windows 10 Pro
I have some MXF files which can't be processed with mt (version 1.0.11 on Windows).
cmd:
mt.exe sample_short.mxf
output:
It doesn't matter if I specify interval, apparently the libav/ffmpeg version used has a problem dealing with the mxf file. If I remux with ffmpeg to mxf, mt works fine with.
ffmpeg -i sample_short.mxf -c copy -map 0 sample_short_remuxed.mxf
cmd:
mt.exe sample_short_remuxed.mxf
output:
For practical reasons I can't remux the files (usually around 100-200 GB). I've tested the same files on a temporary Linux system with the latest version of mt (1.0.13) and they work just fine, no remuxing needed. Would it be possible to Windows binaries of the latest version? Or is there some (detailed) guide on how to generate binaries for Windows?
The text was updated successfully, but these errors were encountered: