Tangier Clarke
Forum Replies Created
-
No I don’t. Nothing that would make this happen. I saw this happen when FCP X first came out, but not since then. That it’s happened to others tells me it’s not just an isolated thing.
Tangier
-
I am certain I didn’t delete anything, but can’t explain how the entire folder just disappeared and was replaced with a fresh event in the Finder and in FCP X. I was in FCP X, did a “reveal in finder” on a clip, and it went nowhere. I checked and the entire event folder was gone. Waited a few seconds and a new one appeared.
Tangier
-
And that’s exactly it, I think I am using an FxFactory plugin and possibly MagicBullet from Red Giant too.
-
ProRes 422
Tangier
-
Is there at least a way to see the original name as a column in the event browser (list view)? That would help me in a lot of situations.
Tangier
-
I concur Bill. You’ve expressed my sentiments about FCP X as I’ve been telling others so well. If you try to shoehorn FCP X into the old way of doing things it will be terribly frustrating. I too had to have light bulb moments to really understand why Apple made the decisions it did. Fortunately I have a computer science background and really see how the media/data management will be HUGE. More and more I am seeing how Apple rolled in features from it’s killed-off apps.
I’m for FCP X for the long-haul. It’s potential are becoming more and more apparent and I’m using it regularly now. Going back to FCP 7 is painful now, but I still love my old workhorse. I tried MC6 went running back to both FCP 7 and FCP X.
For the record, I grew up on Avid starting in the mid-to-late 90s, then transitioned to FCP.
Tangier
-
Herb, that’s why I added “feature-merging”. You are correct about the destruction of these apps, but they some of their features were rolled into other apps and now FCP X in some ways. I am not saying that our current toolset is a replacement for those now gone apps, but rather acknowledging how Apple tends to (even outside the production and post world) bring high end features to the masses in ways sometimes I am sure we all don’t appreciate in some way shape or form.
My fault for not making that clear. Perhaps I was trying to be too concise with commas, and run-ons. It’s something Apple has done across their entire hardware/spectrum for some time and I was pointing to that to try and make some connection to the way things are going with the controversial release of X, subsequent updates, and our projections for it’s future (features and perhaps another app).
Tangier
-
In one way or another everyone’s covered all I want to say, particularly Walter. I’ve dealt with the growing pains and still use FCP 7 alongside X. The first week of X’s release I saw my editorial productivity skyrocket – no comparison. I could edit and organize faster in X. Within months FCP 7 felt old and lethargic. I recently downloaded PrP 6 and MC6. I ran back to both FCP 7 and eagerly want to cut on FCP X more.
I consider the scope of what Apple’s been doing in recent years – Core Animation, Core Graphics, Core Audio, Core Data, GPU leveraging, cleaning and streaming code with OS updates and FCP [classic] updates, mobile devices and their desktop-software counterparts, buying, rebranding/repackaging, improving, feature-merging (Shake-Motion, Logic-Soundtrack), and the massive undertaking of AV foundation and frankly I think we’re starting to see the fruits of a lot of labor that we hadn’t yet had the chance to fully exploit; thank you 64-bit.
I follow the developers as they find hidden gems of FCP X yet to be “activated”, it’s color capabilities, the awesome relational database structure it uses and how that metadata will help us later (when more hooks are available to get it out) and I see a bright future for X. I do believe that there’s “one more thing” perhaps we’ll see this year or early next; either a feature or separate app.
Someone demoes PrP6 on a massively beefed-up system recently at an LA event and it occurred to me. Apple seldom demos (publicly) on a MacPro. We all know the MacPro’s gonna shine. They demo on things like…wait for it…iMacs. That speaks volumes when you consider when you look at the performance based on their code, the core technologies, and what can be done on non-extended hardware.
My perception has changed since the release of X. It went from “this is fun, let me see how i can use it” to I want to cut everything in X now.
PrP6 is really nice, but it is very much like FCP7+ (and I mean that in a very positive way for Adobe).Though now I find myself not looking for a FCP 7 or anything like it. In my personal recent test, just a basic AVCHD (from Af100) open archive, edit, draw the thumbnails for the skimmer/hover, playback and skim/hover playback, transcode (to ProRes), etc., FCP X outperformed PrP6 by a huge margin on one of my older systems (Mac Pro 2×2.26 Quad-Core Intel Xeon/ 16 GB RAM/ ATI Radeon HD 5770/Blackmagic Multibridge Pro 2).
At the end of the day we’ll vote with our dollars. FCP 7 still works for me. FCP X is increasingly working out for me. Cutting my first 4K RED project in it (ProRes of course for now). I am looking forward to checking out the new Smoke too.
Tangier
-
I synced in 7. bing that it was manually done, I could have done it in X. Though I’ve used X before somethings I am still faster in FCP 7 on some things.
Tangier
-
Nope. I was shocked. Word on the street is that the rental house didn’t provide the adapter to record audio into the Red One MX. Otherwise I would have used pluralEyes or tried to see how good FCPX’s sync feature is. Oh well. Had to do it old school.
Tangier