Great news, amazing! Can't wait to try it out.

DJFioDB:

@Isaquit0 Done! Try new audio-only filter!

@DJFio[DB]: dude, that is awesome. LOVE the "Compression" column. Of course, that spawned these ideas:

1. Is there enough metadata to add these columns in Database?

  a. Bitrate - to differentiate between codecs on a finer level

  b. Number of audio channels - mono, stereo, surround

  c. Sample rate - 44.1 KHz, 48 KHz, etc.

  d. Frame rate - 23.98, 29.97, 59.94, etc.

2. If all this metadata can be displayed, what if you allowed the user to select which columns to display?

As always, amazing work. My boss said he donated. Might have to make that a recurring thing. Thank you!

@Isaquit0

a) maybe, but i do not have enough documentation and avid has too many codecs.

b) no. - because the MXF OPAtom always has one channel per file - MDVx operates at file level

c) yes

d) yes

2. ok

look for boss name at the website :)

@DJFio[DB]: One of my guys just used the latest bulld to archive some projects. Flawless backup.

Another usability note for your consideration:

When deleting, these are enabled:

1. "Create project folders" checkbox

2. "Create MXF folders" checkbox

3. Destination text label and [Select] button

Could you disable those when a user selects "Delete"? I think it'll add more clarity.

Thanks!

Wow. This all looks pretty good.

Would it be possible to find out duplicates on different media drives?  The reason I ask is that I have a project with over 12k items on my internal RAID, since I moved by the end of the edit to a better facility, I copyed the media to external HDs. I finished my edit over there but I feel like I could miss some file from my internal raid since I did make some subtitles and small stuff back home afterwards. So, would there be a way for me to find the duplicates, reserve select those, and copy the unique files to the external HDs?

Really really great app. Congratulations.

Ed.

added more codecs, bitrates, framerates.

@DJFioDB:

[quote user="DJFio[DB]"]

added more codecs, bitrates, framerates.

[/quote]

This is awesome. Thank you. It keeps getting better.

Also, can you take a look at this new issue? Seems to be an error in calculating file size. The good news is the miscalculation is consistent – it's off by around 7% (i.e. 6.9%). In other words:

1. If you filter by project in MDVx, it says "Filtered Item Size" is 100 GB.

2. But when you copy or move it, Finder reports the total amount is actually 107 GB.

3. Which means the user really needs 7% more space to backup their project.

Some real-world examples:

Project 1 (User A)

MDV/MDVx - 170.24 GB

Finder - 182.8 GB

170.24 / 182.8 = 0.9312910284

1 - 0.9312910284 = 0.0687089716 = 6.9%

Project 2 (User B)

MDV/MDVx - 172.65 GB

Finder - 185.38 GB

172.65 / 185.38 = 0.9313302406

1 - 0.9313302406 = 0.0686697594 = 6.9%

Project 3 (User B)

MDV/MDVx - 20.22 GB

Finder - 21.72 GB

20.22 / 21.72 = 0.9309392265

1 - 0.9309392265 = 0.0690607735 = 6.9%

What's really cool is MDVx stopped itself with a "copyFileData error", or something like that. The error showed up in the MDVx log for that job. Then I opened macOS' Console, which told me the destination drive was out of space.

Also interesting: running MDV in Wine yields the same file size calculations. (I just thought it was because of Wine.)

Can you take a look at this when you have a moment? Thank you!

I believe that is the difference between showing the size in base 2 vs. base 10.

The Finder changed to base 10 a few years ago.  MDV is most likely displaying the size in base 2.

Base 2: 1 MB = 1024 bytes.

Base 10: 1 MB = 1000 bytes.

(If I remember correctly.)

Eric

Thanks, Eric.

If this is a possibiity, you'd have to flip it though. MDVx is displaying the smaller file size calculation as a result, while Finder is expecting larger file sizes. So MDVx would be displaying base 10, while Finder's expecting base 2.

Plus:

1000 / 1024 = 0.9765625

1 - 0.9765625 = 0.0234375 = 2.3%

Where all of my examples consistently show a 6.9% difference:

Isaquit0:

Project 1 (User A)

MDV/MDVx - 170.24 GB

Finder - 182.8 GB

170.24 / 182.8 = 0.9312910284

1 - 0.9312910284 = 0.0687089716 = 6.9%

I'm sure DJFio[DB]'s already on it.

fixed 1024->1000

Fix confirmed. Thank you!

My son has been assisting me for years, and he's a code writer

he might figure out something, does anyone know where to find the source code?

@Mike Stewart: to clarify, MDV was rewritten for macOS. It's called MDVx.

You can download MDVx or its older (and still very functional) Windows version here:

http://djfio.ru/mdv/

Feel free to donate!

@DJFio[DB]: hey chief! Long time no hear! MDVx is in full effect here. Used it to transfer a project for another editor. Clear views of what media belonged to which project. Even used it to verify a subset of B-roll from another project had the correct project metadata after a consolidate. Again, it's awesome.

One feature request: could the user be warned if the media they'r about to copy / move is greater than the amount of storage they have on the target drive? The only way someone finds that out now is the pie chart stops progressing in the queue. Then you can see an I/O error in the log. (Don't remember the exact error, but something like "copyDataError" over and over again.)

Can that be calculated before executing the action? Or would you calculate the target disk size and present that in a panel, like previous versions of MDV?

Hope all is well over there. Take care!

@DJFio[DB]: are you out there, my friend? Has MDVx gone into hiatus again? If not, then one feature request:

Could the user be warned when the target drive doesn't have enough storage before a copy or move? Again, don't remember the exact error, but the queue log spits out something like "copyDataError" over and over.

Also, will probably be making those video tutorials over the next few weeks. Stay tuned.

Thanks!