Quantcast
Channel: Avid Community
Viewing all articles
Browse latest Browse all 47506

RED AMA plugins on MC 6.0.5 bug.

$
0
0

On an HP xw8600 win 7 64 MC 6.0.5 I'm trying to AMA link to R3D files on an internal drive. Nothing special you would say.

The files are located in their specific folders and each clips name ends in _001.R3D, _002.R3D and _003.R3D.

Now I started with the RED AMA plugins 1.10 which are the latest. Now when I AMA link to all 3 files, it only links to one, being the file ending in _001. In the column name the _001 part of the name is missing. Trying to link to _002 results in the link to _001 being updated in the bin. It alters data in the column duration... the column file name etc... but the video stays linked the original _001 clip. Trying to link to _003 again updates the info in the bin of the original clip but stays liked to the _001 clip 

It refuses to link to the 3 individual files at the same time.

If I delete all AMA links and try again to link but now do not select _001 first but _002 it will link to _002 but now I can't link to _001 and _003.

Unistalled RED AMA plugins 1.10 and tried with 1.8. Now in the name column the _001 part is added but the behaviour is the same.

Uninstalled 1.8 plugins and tried with 1.7 which are the RED plugins that were the certified ones at the time of MC 6. Same behaviour as with 1.8.

Now I do have a clue on what might be causing this. I checked the metadata of the R3D files both in RedcineX and MC and there is one field that strikes me. It's called "Original filename". All 3 clips have the same identical info in that field which is the filename ending in _001. Now I'm not aware of an easy way of editing this metadata so I could test this is what causes the trouble.

Has anybody any clue what I'm doing wrong or did something go wrong with the metadata creation on the camera with these files?

Thanks for any help

 

 


Viewing all articles
Browse latest Browse all 47506

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>