[John Pale]

Both Mac and PC versions will appear in the download center. You can actually download and use both on different computers (not at the same time) if you wish.

[John Pale]

“The wide adoption of ProRes amazes me to this day”

I truly believe its because the names of the various Pro Res flavors are simpler, and ProRes just sounds “cooler”.

I mean, even advanced users of Avid have trouble figuring out all the crazy families and numbers associated with Avid DNXHD.

I get files all the time from people who don’t even use FCP that are ProRes.

[John Pale]

“The other 2 570’s are in an external Cyclone PCIe chassis, both in x16 slots. Though it’s definitely worth testing this without the Cyclone in the equation to see if it changes anything. Although it would seem crazy to me that it would, since I cant imagine simple JKL shuttling requires a lot of CUDA processing power, if at all, considering FCP7 can do this just fine.”

Did not know you were using an expansion chassis. I know from experience, the Mac might not be able to make that work internally.

I was not speaking about CUDA processing specifically, but actual data throughput overwhelming the PCI bus of the Mac Pro. There may be other issues, though, with your cards and CUDA, as you need a text hack to get it working in PPRO.

The comparison with FCP is not really relevant, as FCP does not use CUDA at all. So CUDA problems would not affect it.

You might also try switching to Mercury Engine software only mode, as a test.

If its at all possible, I would try testing with another graphics card. Would be good to eliminate the possibility. Hopefully, it is not the issue, as you have made a significant investment in them.

For what it’s worth, I have a kona 3 and an unsupported Nvidia gtx 470, and I do not experience this problem at all.
I had a Decklink Studio before the Kona, and had all sorts of issues with both Avid and Adobe.

[John Pale]

You have 3x 570 cards??

This may be a PCI bandwidth issue.

Try running with one card to test if performance improves. Premiere can only make use of one card for CUDA anyway.

[John Pale]

Oops. I see Dennis answered that in another thread….

“Chris, if you have an existing ‘box’ copy of CS6, that is still yours. If you started a creative cloud membership today, you would have access to CS6 apps and when the next version comes about, you would immediately have access to it. If your membership lapsed or you decided to stop, you would still have CS6 with you.”

I guess that’s a bit of a relief. But going forward…if I edit something in 7, I will never be able to open it without a Cloud membership. Adobe owns my ability to re-edit perpetually.

[John Pale]

I have mixed feelings about this. On one hand, It feels wrong…but how different is it, really…

I mean…in practical terms…do we really own it now? I use it for a year…an upgrade comes out..I fork over some money..I never use the old disk or backup file of the previous version again. Sure, I “own” it, but what’s it worth….??

But you raise an interesting point, I have not thought of……if I opt out…say, suddenly I go insane and decide to like editing on FCPX, and move to that full time…I can’t easily revisit my old edits in PPRO without reacitivating my Creative Cloud Account…I can’t just fire PPRO like I can fire up FCP 7 now when I need to revisit something I did a few years ago..without paying the piper… Not cool.

What happens to my CS6 when and if I “upgrade” to Creative Cloud? Do I not own that anymore?

[John Pale]

Straight importing will work, but slower than linking via AMA (and transcoding to your target resolution)

I would not recommend linking and editing via AMA using MC 5 and clips this long.

[John Pale]

If you bought it this week MC7 is complimentary,

[John Pale]

It’s Cloud Storage, not a time machine.

I’d pay a lot to download unreleased software from the future, personally.

🙂

[John Pale]

There really is no reason to use super high resolution photos. It’s all going to get down sampled to video resolution anyway..and as you can see, it can cause performance issues.

Make them about double the pixels of your video frame, so you can do a decent move on them. Anything higher than 72 dpi is unnecessary.