Adobe Premiere CC & RED DRAGON HELP!!

[Donnie King]

I recently upgraded my Scarlet X MX to Scarlet Dragon. Shot some 5k footage yesterday and tried to import it into Adobe Premiere CC and continuously got this message "Unsupported format or damaged file". I cleaned the Memory Cache and still no go! I am able to import all of my old files shot with Scarlet X MX whether 4k or 5k but nothing so far that was shot with Dragon. I am also able to open the files shot with the Dragon sensor in Red Cine X no problem so I don't think the files are damaged. Has anyone encountered this problem and has a resolution? I would appreciate any help at this point. Very Frustrating!! Im using PC windows 8.1 don't know if that matters but just to give you a heads up.

 

[Stefan Scherperel]

Hey Donnie, are you running CC? or CC2014. While CC should be able to open Dragon files as well, you might try updating to 2014 and see if that fixes the problem.

 

[Donnie King]

I am currently running CC but I'm looking into upgrading to 2014. However, as you mentioned doesn't make sense that regular CC won't import these files. Thanks for the information. Only one reply so far so maybe this is a rare case that I'm going through.

 

[Stefan Scherperel]

Well, for what it's worth, I'm running Windows 8.1 with cc2014 and I have no problems with Dragon footage. CC2015 should also be releasing soon. Again, I don't remember exactly which update gave you access to dragon footage, so I would say the 2014 release would be worth checking out, especially because it won't cost you anything.

 

[Stefan Scherperel]

An update to this today. I used my laptop today that still has Adobe CC (not 2014) on it, and it would not open the Dragon files. I think Dragon support might have come after Adobe CC.

 

[Daniel Keywan Hollister]

Dragon support was available in CC, but not out of the gates -- it came along with one of the bigger updates, but this happened well before CC 2014. So even if you are on CC, you should be alright, provided that you've been doing your updates.

And with both Premiere and cameras improving as fast as they are, now is the time to start doing your updates. The days of ignoring them for months (or forever) are gone. So at least get CC updated, but I'd recommend going to 2014. There is absolutely no reason to ever want to go back to an older version of Premiere, especially if you're upgrading your camera format.

For what it's worth, it's considered a horrible idea to upgrade to a new major version of your editing software while in the middle of a project, but on Video Game High School we did exactly that -- and we had to. We had so much Dragon footage in resolutions above 4K that even though an updated CC technically supported it, stability became practically nonexistent once we had four hours of it on a timeline. Carefully upgrading to 2014 made pretty much all of those problems go away immediately.

 

[Mark T Workman]

I recently upgraded my Scarlet X MX to Scarlet Dragon. Shot some 5k footage yesterday and tried to import it into Adobe Premiere CC and continuously got this message "Unsupported format or damaged file". I cleaned the Memory Cache and still no go! I am able to import all of my old files shot with Scarlet X MX whether 4k or 5k but nothing so far that was shot with Dragon. I am also able to open the files shot with the Dragon sensor in Red Cine X no problem so I don't think the files are damaged. Has anyone encountered this problem and has a resolution? I would appreciate any help at this point. Very Frustrating!! Im using PC windows 8.1 don't know if that matters but just to give you a heads up.

This is very interesting to me as the same thing happened to me in Pr CS6 on the PC side of my Adobe "Plan" LOL. So far Ae CC playback of MX files were not effected. I solved my CS6 problems initially simply by doing an update. However, although this worked for accessing my R3D files, I now found I was on a 30 Day Trial version of CS6 after the upgrade. After another 3-4 hours on the phone with Adobe technical, letting them run the machine, the problem was solved...