Adobe Premiere CS6 Nightmare. Deja Vu from a FCP 7 user

[Sergio Perez]

I write this post in frustration, because I switched almost a decade ago from Premiere to Final Cut Pro and never looked back. With the recent FCPX interface change and certain fundamental omissions in terms of integration with other post processes, and since I purchased an Epic, I decided to switch back to Premiere since it Is allegedly the most Red friendly software ( and people have posted great thugs about it here). I Decided to Put the software through its paces in a serious project. Call it bad luck, but the thing is the software failed miserably in a crucial moment. This is me venting, will post details later since I'm on my way to a post house with a hard disk that Premiere corrupted after it crashed on import of some MXF media. I tell you: when Final Cut Pro gets its act together I'm going back. Frustrating. MacBook pro retina. This never happened to me when working with FCP for almost 10 years!

[Jeremy Saville]

I feel ya, Sergio. Premiere CS6 is currently completely unstable on the Mac platform. I have a feature that I'm struggling to finish since working with CS6. There's a whole thread about it on Adobe's website- http://forums.adobe.com/message/4462469
If only FCPX or AVID would offer native R3D editing with no transcoding I would switch in a heartbeat.

[Curt Pair]

I have to tell you guys... and I know you probably don't want to hear it... but I haven't had a lick of trouble with CS6 on my PC. I guess it's an OS issue? I'm not sure. I've switched to CS6, and on a laptop, I can cut 5K footage with ease...

[RivaiC]

Curt, but 3rd party SDI output still not smooth. It's not any better than CS 5.5

What is your experience ?

Rivai

[Brian Merlen]

Yea but if you use PC then the OS is unstable even if the NLE works lmfao!

[Phil Holland]

I'll also dip my hat here and say flawless performance with Adobe CS6 and PC.

[Bob Gundu]

FCPX SDI output works very well. I use both Premiere and FCPX and still prefer the direction Apple is going.

[Thomas Koch]

I have flawless CS6 performance on my Mac and my Hac.

I don't have an SDI out card though, and my rocket is in for repair.

[Wes Howell]

Hi Jeremy,

Many people are editing RED on the mac with great success (including myself)

The best (only) approach is to break things down and approach the issues systematically.

I've spent months editing 5k RED on a 2 year old Mac and a more current MBP and I have had a great experience. Great stability, and great export times as well.

I realize there can be problems, however. They can be related to many things. It could besomething as simple as the wrong driver, some video cards are better than others when crunching 5k frames (some versions of the GTX285 have seemed to be problematic for example) There have been OS issues, etc etc. Even something like SDI. Is it using an Nvidia card or a 3rd party card? There are answers and I'm willing to help people if they are willing to provide detailed descriptions of their problems, hardware configs and ideally some solid bug reports. I help people resolve issues and spend most of my time in the Adobe workflow section of this forum.

Happy to help out.

Best,
Wes Howell
Adobe Systems

[Richard Tran]

I write this post in frustration, because I switched almost a decade ago from Premiere to Final Cut Pro and never looked back. With the recent FCPX interface change and certain fundamental omissions in terms of integration with other post processes, and since I purchased an Epic, I decided to switch back to Premiere since it Is allegedly the most Red friendly software ( and people have posted great thugs about it here). I Decided to Put the software through its paces in a serious project. Call it bad luck, but the thing is the software failed miserably in a crucial moment. This is me venting, will post details later since I'm on my way to a post house with a hard disk that Premiere corrupted after it crashed on import of some MXF media. I tell you: when Final Cut Pro gets its act together I'm going back. Frustrating. MacBook pro retina. This never happened to me when working with FCP for almost 10 years!

How did you pinpoint it down to the Software corrupting the drive?
Instead of the other way around, where the Harddrive was dying, and thus crashed when you tried to import MXF media?

I guess, if I had to test it, I would import the exact same files, on a different harddrive, and see if the software still glitches it.