[Peter Price]

If the sequence originated in FCP X, I run into the same issue, but if I import the footage directly into Resolve or Premiere and rebuild the edit natively in those apps it’s fine.

I learned that FCP X has issues reading Sony Alpha cameras timecode. Apparently it’s a known issue and only appears when you import xml sequences from FCP X that contain Sony Alpha Camera footage. If they are imported and edited directly in Premiere or Resolve from the start, there is no issue as these applications have no issues with reading the Sony Alpha footage.

There are two workarounds from what I hear and have confirmed they work…

1. Once the XML is imported into Resolve, go to each clip and change the Timecode start time for each clip to 00:00:00:00 in Clip Attributes. Not too big of a deal if you’re working on a short form project. But for longer project I would go for the next option.

2. Transcode any Sony Alpha Footage in FCP X to ProRes before exporting the XML into Resolve.

Again this issue is ONLY present when exporting XML’s From FCP X with Sony Alpha camera footage and importing the XML into Resolve and is a issue with FCP X and Sony.
I usually edit directly with Davinci Resolve from the start but thought I would experiment with FCP X this time around which is why I’ve never run into this.

[Peter Price]

Cool. Thanks for the clarification!

As far as linking back to camera media via Resolve, I tried that method, and also ran into issues. I exported an AAF, from Avid, then imported that AAF into Resolve. It took in the proxy media, and when I tried relinking to High Res, or doing any type of conform, it kept giving me an error saying that the camera media and the proxy media timecode didn’t match.

What did I do wrong?

[Peter Price]

That could be the case. It does seem to work, when I don’t have the AJA or Blackmagic boxes attached. And Adobe does claim it supports Intel Iris GPU’s since CC 2014, according to this: https://helpx.adobe.com/premiere-pro/system-requirements.html#Adobe Premiere Pro CC (2014) system requirements and language versions

I just found it puzzling that it was happening to both AJA and BMD IO.

[Peter Price]

Hi Christian,

I have a facility running a Terrablock and running Mac workstations via Fiber to the Facilis, and running Premiere Pro and Avid Media Composer. As of now, I’ve set the Cache in the media tab to be placed in the same folder as the project, or something along those lines in the settings, and we haven’t had any problems so far, however Adobe has warned me that they generally suggest keeping the cache files local to the machine because it is a very chatty connection and could hinder speed and performance on the Terrablock, but we have not run into this as of yet. But yes…in saving the files on the Terrablock, the hope is to be able to open the project from another bay without having to reimport or recache material in the project….

[Peter Price]

Hey Brian,

Just wanted to chime in on my experiences so far. I have a facility running Avid Media Composer 7 and Adobe Premiere Pro CC on all of our Macs. We have one new Mac Pro, several fully loaded iMacs 27 inch, and the rest are the old Mac Pro towers.
I have run into very similar instability issues with Premiere Pro and new Mac Pro both in 10.9.2 and 10.9.3. I know that in 10.9.3, exporting pretty much got broken. But after reading exhaustive forum postings about 10.9.3, and it breaking GPU intensive tasks such as exporting, we actually had to revert to working in FCP 7 till some of these bugs fleshed out. However…we are running fairly stable on the latest version of iMacs and also on the old Mac Pros.
Also…are you running any video hardware on your workstations? I know we have run into some flacky Thunderbolt stuff with our Video I/O, but when we turned it off and used just computer monitors, we have experienced exception stability using PPro.
We still have ever intention of using PPro and love the software, but it seems with the new GPU architecture of the latest Mac Pro…we are not purchasing any new Mac Pro machines until these bugs get resolved and they do seem to be surrounded around these Mac Pro versions…

Lastly…it is true that all NLE’s have there fair share of bugs, however Avid Media Composer does run fairly well and stable, with little to no crashes. However there a TON of features that I feel are much more intuitive and accessible in PPRo. Avid feels a bit dated in it’s implementation modern features and overall UI feel. But at the end of the day if the software feels better to you, that will be the right tool. Most of our users that were on FCP 7 don’t care for Avid or the learning curve, so they have gravitated towards Adobe.

Hopefully some of these Adobe folks you are talking to can help you through some of the challenges, as this new slew of Adobe updates are pretty rad!

[Peter Price]

Yup. That’s correct. Current gen 27 inch iMacs with the 4GB nVidia G Force GTX 780M

[Peter Price]

As mentioned in a previous post, I am also currently running 10.9.4 (latest seed build) on an iMac 27 inch and tested out Premiere Pro, Prelude, AME and Davinci Resolve and did not run into any issues at all, so this sounds like it’s specific to the new Mac Pros. Major bummer…

[Peter Price]

Are users running into this issue just on the new Mac Pros, or do these issues also show up on other Macintosh models?

[Peter Price]

I second that warning. Stay far away from 10.9.3. I’ve heard that there is a 10.9.4 in the works, and is supposed to fix a lot of these issues, as I’ve heard it was OS related, and that essentially caused the breakage, and it’s not just Adobe that’s effected by it. I hear Davinci Resolve is pretty useless on a 10.9.3 machine.

I have a Mac Pro (New) at the office that we accidentally ran the 10.9.3 update, and I basically can only run FCP 7 on it with no issues, but everything else went tits up…

Hopefully 10.9.4 fixes these issues….

[Peter Price]

I had the audio set to System Default. After trashing the preferences and selecting my audio device in Audio Hardware preferences, and then setting my audio playback to Adobe Desktop Audio, it seems to have fixed the issue.

So is it safe to say that I should always directly select an audio device and avoid the System Default setting?