-
Editing scenario
-
Got it. That really says it all.
-
[Jeremy Garchow] “Got it. That really says it all.”
Well, great, thanks. Good to know you agree with me.
Simon Ubsdell
http://www.tokyo-uk.com -
[Jeremy Garchow] “Got it. That really says it all.”
🙂
Steve Connor
“Sometimes it’s fun to poke an angry bear with a stickl”
Adrenalin Television -
Keywording… I only use it like I would bins. Set the keyword collection and drag your clips to it. Set rejects for the clips you definitely don’t want. Edit. Keywording like it’s a DAM is a complete waste if time.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Keywording… I only use it like I would bins. Set the keyword collection and drag your clips to it. Set rejects for the clips you definitely don’t want. Edit. Keywording like it’s a DAM is a complete waste if time.”
Meaning?
Keywords can overlap. So you don’t have to be limited to a bin at a time.
People will hate this, but once you start combining this with smart collections, it becomes pretty sweet.
The smart collections don’t have to stick around forever. The biggest change for me, is using the browser as a dynamic environment, rather than a more traditional static environment. But it also has static qualities as well if that’s more suitable.
I don’t use Favorties to tag big long clips. If I do, I edit it down with a new range (but not a favorite) and simply add it to the timeline. Favorites, I use as PIOPs (thanks for that term Walter S) and also as extended markers.
But I’m a nerd.
-
[Jeremy Garchow] “Keywords can overlap. So you don’t have to be limited to a bin at a time. People will hate this, but once you start combining this with smart collections, it becomes pretty sweet… But I’m a nerd.”
Jeremy, I feel like I am always disagreeing with you lately.
Overlapping keywords and smart collections are not pretty sweet.
They are totally sweet.
I think I’m a nerd, too.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
[Jeremy Garchow] “Hmm. Not me.
The bloat still happens, but it doesn’t sky rocket quite like before.”
Guess you’re lucky, because for me it’s pretty much unchanged.
[Jeremy Garchow] “These damn AVCHD and DSLR cameras rename all the files to the same thing. 0000.mts in the case of AVCHD, and 0000.mov in the case of DSLR (DSLR is a little better, but still not good). Let’s say you have 15 cards of AVCHD, that’s 15 clips of 0000.MTS, and that’s only one project.
Now, since Pr doesn’t give you a file path when reconnecting, you can really screw this up HUGELY if you happen to choose the wrong file path, or choose the wrong files accidentally.”
Yes. It’s a huge PITA and something Adobe needs to fix. We use AVCHD cameras and I’ve already come across this exact issue.
[Jeremy Garchow] “What kind of clip and how long was it? Apples to Apples.”
Apples to Apples is a good idea so I did a new test. Here’s how I set it up:
1) I exported a FCP7 project with a single ProRes 422 1080p30 sequence as XML. The project had a simple sequence ~7:00 in length with 3 video tracks and 9 audio tracks.
2) Imported the sequence into Premiere Pro to verify the XML transfer. It worked fine with the usual substitutions.
3) Used 7toX to bring the sequence into FCPX 10.0.4. It imported fine.
4) Created a new project in FCPX on my test drive.
5) Opened the compound clip created by 7toX, selected all, then pasted into the new project.
6) Quit and restarted FCPX, then opened the new project.
7) I made the FCPX window smaller so I could open a small Finder window next to it with the CurrentVersion.fcpproject in view.
Then I did the test. First, I note the size of CurrentVersion.fcpproject is 5MB. Then select all and make a compound clip. CurrentVersion.fcpproject is still 5MB. Blade tool and one cut – 10MB. Cut two – 15MB. Cut three – 20MB. Cut four – 25MB… all the way to cut twenty where CurrentVersion.fcpproject has additively bloated to 121MB.
I quit and reopened FCPX then reopened the project. Compounded the compound and made one cut. Beachball. Three minutes later, CurrentVersion.fcpproject is 242MB.
Next, the same test in Premiere Pro. Same XML project, same media, same computer. Initial project size – 3MB. First nest with twenty blade cuts – 3.2MB. Second nest of nest with twenty blade cuts – 3.3MB. Third nest of nest with twenty blade cuts – 3.4MB. Fourth nest of nest with twenty blade cuts – 3.4MB. Fifth nest of nest with twenty blade cuts – 3.5MB.
You get the picture.
[Jeremy Garchow] “I made a 2 hour timeline of all kinds of things, compounded it, and split it up.
The Project went from 10MB to 200 MBs, it used to get in to the GBs. Once all the autosaves happened, it was running just fine.”
And you’re OK with going from 10MB to 200MB with one blade cut? Try splitting it again and watch what happens to the file size. Or compound the compound and split that.
Try my test and see for yourself.
[Jeremy Garchow] “I do test this stuff, and 10.0.4 seems to be running leaner.”
I believe you when you say you’re getting better overall performance, but I would be surprised if your test results were different than mine.
Compound clips are broken.
Each cut in a compound clip duplicates the entire database content of the clip for each cut. This makes them basically unusable for anything of scale. It’s an easily repeatable, easily verifiable issue. This is the kind of bug that should have had someone in ProApps’ hair on fire a long time before FCPX ever was released. The fact that we’re four updates and close to a year past launch and still no fix should concern everyone.
[Jeremy Garchow] “There’s no question that X needs help here. I am not worried about the end of the world and the database is DOA. Are their kinks? Yep, just like any NLE, especially new ones.”
I realize many folks like yourself are using FCPX with few problems. I have an older machine so I notice the bloat effect very quickly. But if this isn’t fixed soon, I’d start getting concerned.
Not getting a file path when reconnecting is a kink. After close to a year, the bloat issue is starting to look like a deep architectural flaw in the project database design. Let’s hope it’s fixable.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[David Lawrence] “Then I did the test. First, I note the size of CurrentVersion.fcpproject is 5MB. Then select all and make a compound clip. CurrentVersion.fcpproject is still 5MB. Blade tool and one cut – 10MB. Cut two – 15MB. Cut three – 20MB. Cut four – 25MB… all the way to cut twenty where CurrentVersion.fcpproject has additively bloated to 121MB.
“Whoa!
-
[Chris Harlan] “Whoa!”
Try it Chris!
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[David Lawrence] “[Chris Harlan] “Whoa!”
Try it Chris!
“I would much rather take your word for it.
The thing is, I’m just happy now between MC 6 and Pr 6. Especially Pr 6. And I’m working through the finer details of those things right now. I’m coming to a fairly general agreement with your glowing early review.
Reply to this Discussion! Login or Sign Up