-
Back to FCPX From PP (Rant)
-
[Bob Woodhead] “just that every time it’s gone POOF on me, I’ve never lost a single edit. Never had to ditz around with prefs or files. Just relaunch, and there’s the last thing I was working on.”
One of my favourite things about FCPX
-
I agree that the auto backup has been really good for me. but I have lost stuff that only a backup saved. again may be more computer file based than specifically X.
maybe you can up your ram if you want the thumbnails to load faster?
would a SD system drive speed up things loading within the app or just booting the app gets sped up?
Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.
-
Thanks. Understood. Obviously haven’t done any RTing. But its on my to learn list. Really doesn’t make sense that motion isn’t well integrated though it’s so cheap that it really doesn’t offer Apple much incentive. Maybe FCP X sold (helping sell computers) but not too many bought the $50 motion?
But you can create an effect in motion and import it into FC right? Then use it in FC on-goingly?
Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.
-
[Craig Alan] “Really doesn’t make sense that motion isn’t well integrated though it’s so cheap that it really doesn’t offer Apple much incentive.”
In the “classic” days FCP7/Motion enabled a roundtrip. You could highlight one or more clip on the FCP7 timeline and “send to Motion”, leaving a nested Motion project in that place on the timeline. Anything you did to these clips in Motion was then updated within the FCP7 timeline. So it worked a lot like Dynamic Link between Premiere Pro and After Effects.
With FCP X, Apple seems to have changed what they wanted Motion to do. It is the under-the-hood effects engine for FCPX. Even if you don’t buy Motion, you have a lot of Motion installed. FCPX has no native effects. Instead, all effects are Motion templates based on effects in the Motion engine. Plus, Motion adds more effects power for users who want that. For many folks, Motion has become an effects building tool, rather than their primary compositor. I presume that Apple is perfectly fine with that.
[Craig Alan] “But you can create an effect in motion and import it into FC right? Then use it in FC on-goingly?”
Yes.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Lillian Young] “I switched to Premiere Pro last year….The deal-breaker is that projects MAY open if you hold Shift and Option for 8+ minutes…multiple people like me online having the same issue…I can work on my FCP X projects on any (same version of) FCP X. Only once since I’ve started using it (around 2012) have I had a project not open…Premiere won’t even open on my workstation. It crashes on my laptop. I literally have to go back to my office on the weekend to make revisions on a project…I do not want to go back to FCP X. It feels amateur after using Premiere. But I want reliability…”
I have used Premiere for years and currently use both CC and FCPX. If I had a dollar for each time either had crashed, it would pay for a nice meal at a five star restaurant.
After the difficult adjustment, I really like FCPX — it is super fast, especially on H264 4K material. Adobe has a real problem there and it will be interesting to see what they do in the near future.
From a reliability standpoint I think the current FCPX is overall a bit better but I have had many FCPX crashes and apparent memory leaks leading to unexplained slowdowns.
I definitely don’t view FCPX as iMovie+Motion. I think it was Mike Matzdorff (assistant editor on “Focus”) who described the interface as deceptively simple, hiding deeply powerful functionality.
If at this point you are invested in Premiere, your problems can probably be resolved one way or another. My advice is pursue that vigorously before you ditch Premiere. It is easy to get frustrated at whatever your current software is, but this can happen with any editing software.
-
I’ve got 64GB in my Tube, so can’t be RAM. I really think it X building the thumbnails. I’d wager that if the devs would allow a text display of filters/etc, it would be like After Effects plugin window… instant. And while I sometimes appreciate the roll-over preview of filters, most of the time I’d be very happy without.
SSD – anything from that drive speeds up. So boot, app launch, that sort of thing. I can’t even sit in front of a machine that doesn’t use a SSD for the system disk any more. SAST. Short Attention Span Theatre.
-
I’ve posted numerous times about why it was a pain to go back to Premiere after a long stint in FCPX.
My job expects me to jump from all three NLEs time to time so I have some experience in all the “bugs”.
Sure the one bug that I hate from FCPX is the “all of a sudden projects slow down”.
That goes away after awhile.
My biggest peeve with Premiere is the “I cant find the files since you moved the entire project into a different volume”.
Now explain to me why that loses the path so easily when the project is still intact within the parent folder.
This may seem trivial to some but when working with other editors/directors, they look at this as my issue when I tell them Im missing files all the time.
One bug which only relates to me for some reason is this full feature I’m grading and facilitating (Pro Tools, sfx and finishing).
On a specific nMP audio from the proxies went missing but still intact on the clients workstation.
This went on for months me accusing the client that he’s removing files here and there.
In the end it was all my fault due the nMP and Premiere.
Opened the the project on a cMP and it was fine.
Then I tested the same project on numerous nMPs and they were fine.
Just that specific tube and Premiere install.
Couldnt fix it with an update to 2015 so I had to do a complete reformat of the system and start again.
Never had to that with FCPX. -
Lillian Young : “When I could be pirating it li like so many others do”
Actually that would make you a thief. And how do you know that “so many others do that?” I’m sure Adobe’s intellectual property lawyers would love to hear what you know.
-
[Andy Field] “And how do you know that “so many others do that?” I’m sure Adobe’s intellectual property lawyers would love to hear what you know.”
If Adobes lawyers are unaware of this they should check out the torrent sites. Hundred of thousands of seeders for Adobe products. They probably already know though…
-
[Lillian Young] The deal-breaker is that projects MAY open if you hold Shift and Option for 8+ minutes. Orrr, you may have to sign out and sign back in only to have it crash. There are a ton of workarounds that don’t always work and multiple people like me online having the same issue.
Hi Lillian,
Sorry you are having trouble with Premiere Pro. First of all, you can get more help with Premiere Pro issues in the Premiere Pro forum here at Creative Cow or at the Adobe Forums (I run the Adobe forums for digital video).Regarding the issues that you are having, it sounds like project corruption. Projects may become corrupt if you update Premiere Pro (or OS X) mid-project, or work on the same file over and over again each day without working from a backup.
1. It’s not a good idea to update your project file to a major new version of Premiere Pro while working on a project, especially if you have a complex project with dynamic links, nested sequences, imported graphics, multiple formats, media on multiple drives, etc. You should strive to remain on the same version of Premiere Pro throughout the life of your project. The most recent version (9.1) is a major version, so if you updated recently, that is why your projects might be corrupt.
2. Do not update a major version of OS X while working on your project. Wait until you are between projects.
3. Do not work on a single copy of your project for months and months without working from a copy/duplicate/backup.
As was suggested by Andrew Kimery, you can sometimes import a misbehaving (corrupt) project into a new project, which can “rewire” it into working much better.
[Lillian Young] “Premiere won’t even open on my workstation. It crashes on my laptop. I literally have to go back to my office on the weekend to make revisions on a project.”
It sounds like you have the problem of OS X corrupting the functioning of Premiere Pro by changing the Adobe folders’ permissions to RW to R (Read Only). This can happen when updating OS X from one major version to the next using certain updating methods, like via Time Machine or system migration.
This blog tells you how to fix that issue and what to do the next time you update OS X: https://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-crashing-while-working-mac-os-x-10-9-and-later/
For help with this, feel free to contact our support agents. Start a chat here: https://bit.ly/adobe-support Then, ask for the “video queue” to make very sure that you are connected with our top video troubleshooting staff. Do not let a baseline agent assist you with these issues. Insist on speaking with the video queue. They are open M-F 5AM to 7PM. If you have any trouble beyond that, contact me.
Other editors you may run into, might have similar issues. I feel it is because of the above issues. Feel free to share this info with your colleagues for a smoother experience with Premiere Pro and the other Adobe applications.
Thank you,
Kevin MonahanKevin Monahan
Support Product Manager—DVA
Adobe After Effects
Adobe Premiere Pro
Adobe
Follow Me on Twitter!
Reply to this Discussion! Login or Sign Up