Alternative to Windows Properties for video files

[TheGhost78]

Could you add functionality to make use of ffmpeg or MediaInfo / MediaInfo Lite for reading video file details? In particular, frame rates read by Windows are quite often off by a little. Ffmpeg doesn't need to be installed, the executable file just needs to be on your system somewhere. MediaInfo is installed or can be portable.

So, instead of:
<(System.Video.FrameRate)>
<(System.Video.FrameWidth)>
<(System.Video.FrameHeight)>
<(System.Audio.SampleRate)>
<(System.Audio.EncodingBitrate)>

There would be the equivalent options of:
<(ffmpeg.Video.FrameRate)>
<(ffmpeg.Video.FrameWidth)>
<(ffmpeg.Video.FrameHeight)>
<(ffmpeg.Audio.SampleRate)>
<(ffmpeg.Audio.BitRate)>
<(ffmpeg.Audio.EncodingBitrate)>

This would be similar to how installing Icaros gives additional options within BRU:
<(Icaros.VideoTracks)>
<(Icaros.AudioTracks)>
<(Icaros.SubtitleTracks)>
<(Icaros.ContainsChapters)>

[Admin]

How does this work ?

This would be similar to how installing Icaros gives additional options within BRU:
<(Icaros.VideoTracks)>
<(Icaros.AudioTracks)>
<(Icaros.SubtitleTracks)>
<(Icaros.ContainsChapters)>

Does Icaros add Windows File Properties to the files ?

[TheGhost78]

The software adds more options to Windows properties - you can select additional columns to display in Windows Explorer, and these are also available for selection in BRU.

Icaros fields in Windows-Explorer:


Icaros fields in BRU:

[Admin]

Can ffmpeg or MediaInfo / MediaInfo add tags to the file properties, same as Icaros??

[TheGhost78]

I don't think so, no.

[therube]

(ffmpeg can write tags. MediaInfo, no.)


Oh. So you're saying that BRU does read an Icaros property, like <(Icaros.SubtitleTracks)> - cause Icaros set up this, otherwise unknown to Windows, Property, & because of that, Windows just see it as any other Property, which is then directly available to BRU, too.


But what you're looking for is to have BRU use ffmpeg (ffinfo), directly, to read various meta-data from files, rather then simply using what the "Windows Property" systems may or may not see.

(And likewise, then you wouldn't need to use Icaros to write said data, necessarily, as you'd be reading the info obtained by ffmpeg.)

[TheGhost78]

Yes, it would just be an alternative to using Windows File Properties when dealing with video files.

So, I was thinking that in BRU > Tools > Preferences, you could point to the location of ffmpeg.exe (e.g. C:\Users\ffmpeg.exe) and then have an extra option under Renaming Options > ID3 / EXIF Data / File Properties for ffmpeg File Properties. You would then reference these in Add (6) for example, similar to what we can already do with Windows properties, like:

<(ffmpeg.Video.FrameRate)>
<(ffmpeg.Video.FrameWidth)>
<(ffmpeg.Video.FrameHeight)>
etc

[therube]

Well, in that regard, there wouldn't be a "ffmpeg.*" property.

You'd have to gather & parse it, something like:

C:\out>ffprobe -v 0 -of compact=p=0 -select_streams 0 -show_entries stream=r_frame_rate movie.mp4
r_frame_rate=30000/1001

Where, r_frame_rate=30000/1001, is the returned value.

[Admin]

Is Icaros not as good as ffmpeg or MediaInfo ?
Mediainfo has a library that could be integrated in BRU.

[TheGhost78]

Icaros only has 4 or 5 additional items. Importing Mediainfo's library would be great!