As part of our workflow, we often move media files between MXF media file folders on different systems.  We genarally don't use a shared storage environment because of cost constraints, opting for a more low tech/ simpler approach.

For the last year or so, we have noticed that MXF media file folders no longer 'recognise' that files have been added or deleted automatically.  Sometimes they do but more often than not they don't.  In order for the new media to be 'seen', we have to manually trash the database files. Then the MC will rebuild the whole database file.  This takes quite a lot more time as the whole database has to be rebuilt, rather than MC appending the change to the existing file.  Sometimes even this will not work and only restarting the application will bring everything back online.

It would be great if the media databases worked like they used to...

I guess the question is whether the databases aren't being rebuilt when you add media, or is the issue with the system reading the updated database file.

Can you confirm that the newest file in a problematic MXF folder is the media database?

It's the databases not being rebuilt. We see no gas guage 'scanning' process unless we trash the .mdb/.pmr files.

What version of MC are you on?

Currently on 2018.11 but we have noticed this since 2018.4 on multiple ststems.  We do a lot of copying media between systems... Sort of poor man's media sharing with local drives for each system (with identical media).  We have a system to sychronize the media file folders but it relies on the MC on each system recognising that something has changed and rebuilding the databases.

Try the menu File/Media/Load Media Database and see if it scans after the new media is copied.  This works for me when brining in MXF files from resolve,

I can second this. Been happening on both Mac and PCs in our office and home office. Media Composer 8.9.4, Editshare or local drives. Seems really weird.

Not able to test on other versions yet.