Michael Phillips
1
COW Coin
Forum Replies Created
-
If you want to send me a link to download one of your R3D files, I can see if it works for me. It may be something system wise that Media Composer is not happy with, but hard to tell seeing as MC can link to it and play it somewhat while other applications have no problem with it.
What resolution is the file?
what is your project type?
Have you set Media Creation settings to be half good, half, 1/4, etc. to decode a little easier?
Are you working with proxy setting in Project window?There are a lot of different places to look which makes it confusing, but once you know where to look these settings may help.
Michael
-
If you open the R3D file in RedCineX Pro and select “Metadata” from one of the menus it will tell you camera, version, codec, compression, etc.
As far as the overall experience, Media Composer is much happier with native file formats and external dailies process. Over the years it has opened up to more formats, but there is still what is considered “native formats” and not native. If you can transcode/consolidate to it, it is native. That being said, AMA’s promise is to be the conduit of externally supported formats but can be hit and miss in some cases.
Also, I may have missed it the first time, but there are mixed frame rates in which Media Composer has changed the best methods of handling over the years. Legacy wise, you had to create a project that matched that rate, transcode, open bin in the native project, etc. In more recent versions, it is handled in transcode settings whether to preserve native rate, etc. I can’t recall off the top of my head whether it allows keeping frame rate, but changing resolution.
But, making your DNxHD proxies externally should just work. Are you syncing double system audio in Resolve or just transcoding the camera originals? I have to admit that I prefer using RedCineX Pro to make proxies. It automatically creates an ALE and AAF in additon to all the proxies. Move proxies to MediaFile folder, drag and drop AAF into bin, and optionally merge ALE.
Michael
-
The Sony XML should be part of the AMA plug-in to ready and support unless it is another file I am not familiar with this particular file. The same with the .cine file.
Michael
-
Nothing automated that I know of – where is the XML and TEXT files coming from? If it’s a sequence XML then there’s a chance that Resolve might be able to do something with it.
Michael
-
Users are reproting successful BRAW transcoding with v1.6 of the BRAW AMA plug-in released yesterday at Blackmagicdesign.com
Michael
-
Also, how long are your clips? Something to test and might be telling is to break your linked masterclip into two subclips and try transcoding those to see if that succeeds or not.
Michael
-
As I mentioned it may be a contributing factor. You make a good point about others not experiencing this so unclear what the actual problem may be. I don’t have any insight into Avid development and release schedule but it seems that this may be something to open a support ticket.
Do you know what camera and codec version and specs is being used?
Michael
-
I just did a quick check on RED R3D SDK versions available from the RED development page and the version declared in the Avid RED AMA from the Avid AMA download page and the latest Avid RED AMA version is listed as 7.0.7. According to the RED development page, the latest version is 7.1.0. The previous version is 7.0.8 which was released 7/20/2018, meaning 7.0.7 is almost a year out of date.
This may or may not be a factor, but certainly being a year out SDK wise for any camera/codec updates released since that time could be a factor.
Michael
-
I’ll try some files myself later today, but what camera version or other info can you give on your RED files? My test files are at least a year old and some are older. I can download some from RED as needed.
There are a few issues to track here and they are slightly different. Avid’s AMA strategy is to let camera manufacturers and third parties (like Nablet for Sony) create codec support as needed. In the case of BRAW, Blackmagic’s camera team develops the AMA plug-in. In the case of RED, it is AVID who creates the AMA plug-in based on their SDK and will update from time to time as new versions of RED’s SDK get released. It should also be noted that Avid’s implementation does not offer the full feature set or all of the parameters available to them.
So in the RED R3D scenario, it is an Avid controlled pipeline and filing a bug with support “may” help get to the bottom of the issue faster.
In the case of BRAW, it’s sort of middle ground at this point – the codec clearly decodes the file as you can play them. They updated the plug-in to properly handle the timecode, but now it doesn’t transcode. Transcode is on the Media Composer side of things – as far as I know, a third party cannot control that part of the process. So there is an issue between the decode handoff and the transcode process which could be a BMD issue, an Avid issue, or both. Now as a customer of both, you’re stuck in the middle while two customers who are partners, as well as competitors, work it out.
In order to get up and running now, the only solution is to use Resolve for BRAW transcoding to make your DNx versions for editorial – and optionally the same for RED RAW. Or you could use RedCineX Pro to create DNx media. In both cases, you have access to all the parameters for color/exposure/gamma management at your disposal.
I’ll update as I try RED files in latest version of 2019.
Michael
-
Sometimes that means the hard drive can’t keep up either. What drive type and connection are you using? Can you move one of the files to another hard drive and try again?
Do they play with any other player such as Red’s own player or RedCineX Pro, Resolve, Premiere Pro, etc?
Michael