Author Topic: video/audio length or duration  (Read 5499 times)

aboalsmasem

  • Newbie
  • *
  • Posts: 2
    • View Profile
video/audio length or duration
« on: March 21, 2017, 22:35:30 »
this feature is almost in every explorer, I really would like to see it in the future.

AlanJB

  • Power Member
  • ****
  • Posts: 365
  • VERY old Programmer
    • View Profile
Re: video/audio length or duration
« Reply #1 on: March 22, 2017, 11:48:59 »
You can add Length to the column layout for audio/video file types.

Mathias (Author)

  • Administrator
  • VIP Member
  • *****
  • Posts: 3886
    • View Profile
    • Multi Commander
Re: video/audio length or duration
« Reply #2 on: March 22, 2017, 12:32:36 »
Well Yes and No.. the Lenght property are from the audio extensions.. but it works for some video formats..

Adding support for all video formats are messy. I need a 3rd party lib that I can use. because I'm not writing it my self. (will take years)
However, finding a good free 3rd party lib in c++ that fits into MC is not easy.

aboalsmasem

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: video/audio length or duration
« Reply #3 on: March 22, 2017, 20:33:14 »
You can add Length to the column layout for audio/video file types.

What if i only want video?

hillschmidt

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: video/audio length or duration
« Reply #4 on: March 30, 2017, 22:11:29 »
For me, the correct lenght of mp4 videos is shown correctly as long as the movie has not more than 2GB...

I already opened a bug report ...

Mathias (Author)

  • Administrator
  • VIP Member
  • *****
  • Posts: 3886
    • View Profile
    • Multi Commander
Re: video/audio length or duration
« Reply #5 on: March 31, 2017, 07:24:59 »
For me, the correct lenght of mp4 videos is shown correctly as long as the movie has not more than 2GB...

I already opened a bug report ...

Unfortunately that will not be fixed anytime soon.
MC depends on 3rd party library support for this (TagLib) and the maker of that lib have added 2G+ support in there new v2 branch, but v2 is a total rewrite and is still unstable.
And since v2 have lots of API changes, It will require some work in MC too when going over to v2. So first a stable version of it needs to be released and then I need to find the time to rewrite how MC is using it.