[Chris Borjis]

Heck ya get the Quadro (or some kind of GPU accelerator…makes a BIG difference)

8gb of ram is not enough. even with 16gb ram we found 1080 work was sufficient
but choked it and crashed often when closing out of 4k edit projects.

32gb of ram is pretty much the minimal if you want a hassle free experience.

and the quadro will help big time too.

[Chris Borjis]

CC 2014.1 is working great. had an issue initially where projects with pro res files
were shown as offline. turned out to be a quicktime plugin (DTSHD-MA decoder) that
caused the problem.

Dave it should be working for you no problem.
I’m on a 2009 mac 8-core (OS 10.8.3) with kona3G, quadro 4000 (latest driver & CUDA version) (you didn’t mention what gpu you are running)
and fiber channel attached raid 5.

Our system runs great and even did a bunch of 4k projects lately.

have you tried disabling CUDA or openCL or removing your aja card drivers?
just to see if it has any affect.

Also, do take a look at your quicktime plugins folder. there could be
something in there being the root cause.

[Chris Borjis]

I’ve been cutting and exporting RED 4k here on a huge number of projects the
last month and my experience has been to best keep the program monitor at 1/8
resolution and yes the export to 1080P takes awhile, but I expect that.

This is with 2009 8-core mac pro towers with 32Gb ram, quadro 4000’s and Raid 5 storage
connected by fiber channel or pci-express direct.

When I queue several in media encoder, I just walk away from the machine knowing
that it will finish the exports if I leave it alone. But I never expected that
it would or should do that while I’m editing. Not with that kind of load.

Considering how much processing power it takes to deal with 4k footage, it all
makes sense that it would work this way.

[Chris Borjis]

I have the same monitor in one of my rooms and most of them do support the 48hz “24P mode”

whenever I have 23.976 sequences in that room, the monitor output doesn’t work.

Some of the black magic hardware will not output it. In final cut pro 7 it had
the ability to add the pull down to output it.

right now the only work around I’m aware of is to change the frame rate of
the sequence from 23.976 to 29.97.

This is a brand new feature in Premiere CC 2014.1 (thanks for this adobe!) as before
you could not change a sequence frame rate once set.

[Chris Borjis]

try the color correction work space…that might be what your looking for.

showing program monitor and a waveform in a separate window

[Chris Borjis]

might update your quicktime or look into any odd quicktime codec components.

seems issues like this are are some times related to quicktime.

[Chris Borjis]

I read a similar article about after effects not importing pro res with errors.

two solutions were presented:

1 update to the latest apple codecs 1.02 (I found 1.05 and updated…no change)

2. delete the dvcprohdoutput.component from the quicktime library.

That didn’t work either, but it got me thinking.

I recently installed a DTS-HDMA encoder that came with a free quicktime decoder.
It is not supported in OS X 10.8 (only snow leopard is supported)

Being that I don’t really need it anyway, I removed that component from the quicktime
library and now I can import prores and open existing projects with prores sources no problem.

so that was it. an unsupported quicktime codec was crashing qt32 server. DTS-HDMA decoder in this case.

I wanted to post this in case anyone else has the issue.

[Chris Borjis]

[Nick Schlott] “So on the same system, with the same footage, using CC 2014.0, ProRes imports just fine?”

2014.0 updates/is overwritten by 2014.1

however if I open premiere CC (still installed) yes pro res works fine and quicktime can also open them.

The issue is with adobe software, system wide pro res works otherwise.

[Chris Borjis]

Hi Kevin,

uninstalling aja drivers and aja adobe plugins has no effect.

ProRes files are showing offline or failing import for:

Premiere CC 2014.1

After Effects CC 2014.1

Media Encoder CC 2014.1

Please escalate this with someone on your end.

[Chris Borjis]

[Kevin Monahan] ” I read on another thread that AJA drivers were not working right in Premiere Pro CC 2014.1 (8.1″

The latest aja drivers work perfect on my system. Transmit is flawless.

only pro-res quicktime files are the problem. Everything else is perfect.