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
Add IMF Support inside LWLibavVideoSource() and LWLibavAudioSource() #16
Comments
Would you provide a sample? |
Sure, there you go: IMF Sample For more info, check this discussion on Doom9 https://forum.doom9.org/showthread.php?t=173372 |
43,12 gb??? Can you upload small sample with hundreds mb?? |
Sure, but it's gonna take much longer 'cause I'm gonna have to create an IMF from scratch using Colorfront Transcoder here at work and we're all in Easter Break till Tuesday at the earliest. The thing with IMF is that if you trim the video you also gotta change the CPL.xml P.s I've been generous here, real master files are like 800+ GB eheheheh |
Try the attached version. Edit: try the latest version. |
Sorry, I've been a bit overwhelmed. Testing first thing tomorrow, I promise. |
I think it's work check here @Asd-g |
Works like a charm, thanks @Asd-g ! 🗡️ |
I have to mention that |
No problem. IMF packages always come as one big folder with all the files in it. ;) |
…orRange property for _Alpha clips Updates HomeOfAviSynthPlusEvolution#11. Fixes HomeOfAviSynthPlusEvolution#16. Signed-off-by: akarin <i@akarin.info>
Hi there,
essentially, FFMpeg supports IMF which is basically an xml file with the CPL describing which audio and which video should be taken and from where. In other words, if in FFMpeg someone does like ffmpeg -f imf -i "CPL.xml" etc it will decode video and audio correctly.
My proposal is to use the FFMpeg IMF decoder whenever an ".xml" file is passed to the indexer, hence adding the ability to index IMF packages inside Avisynth and VapourSynth.
If the .xml file is just an xml, it will fail and you can parse the ffmpeg error or return whatever error you like.
I can provide a sample if needed.
The text was updated successfully, but these errors were encountered: