Multi Commander > Support and Feedback
No properly working "Length" column for audio/video files
Cripple-resistant:
--- Quote from: Mathias (Author) on November 13, 2019, 08:10:45 ---
--- Quote from: FredeF on November 12, 2019, 19:37:15 ---You should use the MediaInfo.dll
It is open source och fungerar jätte bra. The documentation is rather inadequate and the frontend gui is awful, but for MC only the .dll is needed.
It will extremely fast rip the data even from almost any obscure file extension.
(...)
--- End quote ---
I had a look at it: the API is horrible and bloated. Not sure I want to increase the size of MC with 80% just to get some minor data about video files.
There must be something better.
--- End quote ---
One thing to note about using MediaInfo dll (not sure if other 3rd party libs would also provide this possibility):
It would allow you to provide in MC columns like:
"Video format", "Video codec id", "Audio format", "Audio codec id"
These columns would be very useful because the file name extension of a multimedia file only gives an indication about the multimedia container type and not about the video and audio formats/codecs actually being used by that file.
The video/audio format/codec information is very useful for example when you want to use a USB stick to play a video/audio file on TV: TV multimedia players often have limitations on the codecs they support so having the video/audio format/codec information of multimedia files being displayed directly in MC columns (instead of the MediaInfo GUI) would be very useful for this purpose for example.
FredeF:
--- Quote from: Mathias (Author) on November 13, 2019, 08:10:45 ---
--- Quote from: FredeF on November 12, 2019, 19:37:15 ---You should use the MediaInfo.dll
The documentation is rather inadequate and the frontend gui is awful, but for MC only the .dll is needed.
It will extremely fast rip the data even from almost any obscure file extension.
--- End quote ---
I have look at it. the API is horrible and bloated. Not sure I want to increase the size of MC with 80% just to get some minor data about video files.
There must be something better.
--- End quote ---
That is exactly what I wrote: Use only the .dll
It is small, fast and very tolerant on buggy file headers, and is of course not bloated.
Mathias (Author):
--- Quote from: FredeF on November 13, 2019, 20:49:19 ---
--- Quote from: Mathias (Author) on November 13, 2019, 08:10:45 ---
--- Quote from: FredeF on November 12, 2019, 19:37:15 ---You should use the MediaInfo.dll
The documentation is rather inadequate and the frontend gui is awful, but for MC only the .dll is needed.
It will extremely fast rip the data even from almost any obscure file extension.
--- End quote ---
I have look at it. the API is horrible and bloated. Not sure I want to increase the size of MC with 80% just to get some minor data about video files.
There must be something better.
--- End quote ---
That is exactly what I wrote: Use only the .dll
It is small, fast and very tolerant on buggy file headers, and is of course not bloated.
--- End quote ---
The dll is around 6MB for 64bit version , it would be smaller if build in using static lib.. Fast hmm Well it might be okey. But since everything is string based, it could have been faster. But I don't think that would be a problem, But It is bloated in the way that it support so much more then I need, 80% of everything in the DLL I do not need.
But there might be way to get Media Length and some other properties from Windows.
Cripple-resistant:
--- Quote from: Mathias (Author) on November 14, 2019, 07:40:06 ---(...)
The dll is around 6MB for 64bit version , it would be smaller if build in using static lib.. Fast hmm Well it might be okey. But since everything is string based, it could have been faster. But I don't think that would be a problem, But It is bloated in the way that it support so much more then I need, 80% of everything in the DLL I do not need.
But there might be way to get Media Length and some other properties from Windows.
--- End quote ---
Maybe you could use various (automatic or manual, binary or source-based) dead code elimination (DCE) techniques to remove all/most of MediaInfo code not referenced/called/used by MC. Or if you don't want to do it completely by yourself, you could ask the MediaInfo dev team if they would do that for you or maybe help you on how to do this (you have nothing to lose to ask them!) :)
Mathias (Author):
--- Quote from: Cripple-resistant on November 15, 2019, 01:03:12 ---
--- Quote from: Mathias (Author) on November 14, 2019, 07:40:06 ---(...)
The dll is around 6MB for 64bit version , it would be smaller if build in using static lib.. Fast hmm Well it might be okey. But since everything is string based, it could have been faster. But I don't think that would be a problem, But It is bloated in the way that it support so much more then I need, 80% of everything in the DLL I do not need.
But there might be way to get Media Length and some other properties from Windows.
--- End quote ---
Maybe you could use various (automatic or manual, binary or source-based) dead code elimination (DCE) techniques to remove all/most of MediaInfo code not referenced/called/used by MC. Or if you don't want to do it completely by yourself, you could ask the MediaInfo dev team if they would do that for you or maybe help you on how to do this (you have nothing to lose to ask them!) :)
--- End quote ---
No that will not work since it is not really dead code.. it is just ununsed code. It will not be able to removed it.
But as I said. Windows is able to get that information. And I think it will be possible to ask windows about it. However it does not support as much as that MediaInfo.
Maybe later a option downloadable plugin to MC can be added that exposes all properties in MediaInfo to MC. BUT it will be optional and installed separately
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version