[Stephen Bakopanos]

It’s definitely a CUDA issue. I was putting up with it for weeks thinking it was a PPro issue. Then, after getting fed up with the disruptions it was causing, I began googling around and discovered that it was all linked to CUDA. As soon as I removed the CUDA drivers, everything worked fine again.

Still, I’d like to have CUDA back – when it works, it has a bit of an edge over OpenCL

[Stephen Bakopanos]

Wow. How have I not come across this thread earlier??? After months of suffering through these exact problems, I was about to toss my GPU in the bin thinking it was the culprit. Instead, all I have to do is trash CUDA. Hope a fix is found soon so I can get it back though…

[Stephen Bakopanos]

Delivering to DubSat/MediaPro I take it?

I’ve had all sorts of issues getting 1080p TVCs out of Premiere and delivered to spec.

I even work in the same building as DubSat and have chatted first hand with the tech guys there and haven’t had a proper solution. In the end, I just submitted files in HD and let them work the magic.

Will investigate further as I have some more TVCs coming up…

[Stephen Bakopanos]

You’re right to an extent Oliver. If a plugin isn’t CUDA optimised (i.e. MB Looks), a CUDA card won’t help. But if it IS optimised for it, you can pile effect upon effect on your footage and get realtime playback at full resolution. I’m yet to test out how far you can push an OpenCL card on a MacBook or iMac, but I’d hazard a guess that it won’t be as far.

One other benefit of the Nvidia CUDA cards is that if you use After Effects, it will also take the load off the CPU when working with RayTrace 3D compositions. The difference between CPU vs GPU acceleration, like in Premiere, is night and day. As far as I’m aware, OpenCL based cards (i.e. ATI cards) aren’t supported.

[Stephen Bakopanos]

Lance is right. If you want Premiere to work to it’s full potential, you need to be running CUDA. The difference between the GPU accelerated Mecury Playback Engine and the CPU MPE is night and day.

I personally couldn’t be bothered waiting for Apple to bring out a MacPro (and yes, I know that they’ve been dependent on Intel releasing CPUs), so six moths ago I went and built a hackintosh specifically for Premiere/Resolve. It was cheap as chips (i7 2600k + 16GB ram + dual GTX570) and works like a dream.

So if you’re technically minded and prepared to do a bit of tinkering, I recommend giving it a shot. At the end of the day, if you find it all too hard, you’ve still got a pretty decent Windows workstation.

Alternatively, wait it out and hope that Apple don’t ditch the MacPro…

[Stephen Bakopanos]

I must say, this update does dramatically improve the usability of FCPX for my workflows.

Previously, if I modified files outside of FCPX they’d go offline with no way to relink them short of manually re-adding the files to the event and the timeline – massive pain in the ass… BUT now they seem to stay online, which means I can create and modify clips in After Effects and other such apps! You can also manually relink files, but you have to go out to the project viewer and do it on a project level to all the clips… not ideal (ideally you could do it on a clip bu clip basis), but a step in the right direction.

I’m currently sticking with FCP7 for the most part, but am dipping my toes in the PPro pool and dabbling with FCPX where I can. Both seem to have advantages and disadvantages ATM… It will be interesting to see what Adobe bring to the table with CS6…

[Stephen Bakopanos]

The easiest solution would be to copy the contents of your SD timeline to a new HD timeline. The best way to ensure the new HD timeline matches your media is to drag a DSLR clip to the “Create New…” button at the bottom of your project window (next to the trash can). Then just delete the clip from the new timeline and paste all the contents from the old timeline into it. If they don’t fill the frame, just select them all and right click and choose “Scale to frame size”.

Hope that helps.

[Stephen Bakopanos]

Suffering from the same issue here.

MAJOR BUG.

[Stephen Bakopanos]

I get the same error. I just recreated my own in Motion.

What’s more concerning for me is that some text generators seem to be reverting back to the default “Title” text if I close and reopen FCPX. Not happy having to constantly retype my titles.

[Stephen Bakopanos]

[Scott Sheriff] “Well that’s just silly. I don’t believe there are any amateur broadcast editors, so it would seem your hypothesis is wrong.
However there are plenty of amateur film editors, and the term “indie” is just a euphemism for amateur. “

I think you’re missing my point. The “pro” industry is not just limited to broadcast editing, which is what a lot of people in this forum seem to suggest. I for one consider myself a professional, but I rarely do any broadcast work any more – instead I specialise in producing videos for online delivery. Once FCPX has XML and OMF it will be more than suitable for what I do – for my mind, that makes it a “pro” app. Whether or not it’s a broadcast level app is another question.