Forum Replies Created
-
Always impressed, Kevin, good to see you here on the Dark Side again. 😉
I think my computer screen would crack if we saw an Apple rep on the forum. Yet here you are, not even staying on your side of the pasture. Well done!
-
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.
-
[Craig Alan] “Yeah I’m not buying the FCP X never has problems summary.”
Lol… didn’t say it never has problems, 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. And yeah, that story from last week, the OS locked up. But 1 minute reboot & I’m back to where I was, nothing lost or corrupt.
I’m quite ready to bash parts of X I don’t care for… eg, how long it takes the filters window to list. ugh. stupid thumbnails is my guess. Inability to custom window interface.
-
[Oliver Peters] “Using Automatic Duck, FCPX plus AE make a good combo.”
Yeah, I really should give that a spin. I still do the manual go-around.
-
I’ve stopped being interested in about what others think of X.
And I don’t think my producer gives a damn, either, as Friday he was literally dancing with joy after the big cheese watched the edit and gave a thumbs-up, no revisions to that morning’s work. The edit was completed in about… 60% ?…. sort of hard to actually say half, of the time it would’ve taken me on other NLEs. Keywording, mag timeline, connected clips all major contributors in that time savings.
Back to the issue, though, I’m going to agree with both Lillian AND Andrew, et al. Over the years, IMHO, PPro has always been more “flaky” than the others. Reading the forums, there seems to be a never-ending stream of issues. Many are user-created for whatever reason, but the overall vibe seems to be a house made of bamboo, not steel. (yeah, sucky analogy, but only 1 cup of coffee so far today) If you get your house in proper shape, and don’t poke at the foundations, PPro will be pretty solid (linking, ahem), only sometimes requiring things like cut n’ paste of project info. FCPX, on the other hand, just works. (yeah, after initial fiasco) Going back to the little scenario above, I’m working on some final tweaks to that edit, maybe moving a bit too fast, as my commands are starting to buffer, then execute, and X goes POOF. System needs a hard reboot. General gasps from producer & others, while I calmly go for a stick of gum. No concern, because I’ve never had a project get corrupt in X. About a minute later, full reboot, back editing (man, I SO love SSDs). Now, had that project been an effects heavy one, I very well might have been considerably slower than linking PPro/AE. Still shaking my head that Motion is left adrift from X.
We’re just still not a point where we can deal in absolutes in which NLE is, in all cases, better. Hammer vs screwdriver. Right tool n’ all that.
More coffee now.
-
Bob Woodhead
January 16, 2016 at 1:09 am in reply to: Way OT: Stone Age editing, no use of the “D” wordSome of my first edits were on Ampex VPR-2B, 2″ quads. No controller, ran it through a switcher.
My edit today was on my MacPro tube, 8TB RAID, all in my backpack.
Still makes me shake my head.
“Constituo, ergo sum”
Bob Woodhead / Atlanta
CMX-Quantel-Avid-Premiere-FCPX-AFX-Crayola
“What a long strange trip it’s been….” -
OK, I understand that workflow.
But I’m still wondering why an “master” library wouldn’t work well for multiple editors working on parts of a larger production.
Thinking:
Any editor adding clips to their “work” library first creates a new event for new clips. After that’s done, they open the “master” library and copy their new event to it. They then close the “master”, so it’s available to the other editors for the same purpose. That way, any editor can ingest without waiting for the “master” to be available. Also, editors can copy others’ new events into their own local “work” library. When the production is complete, editors can sequentially open the “master” library and copy their projects into it.
Thus, at the end, all media referenced by all editors exists in the “master” library, and all final projects are also in the “master” library.Flaws?
-
[John Rofrano] “All modifications are done on a local copy of the project. You only copy it back to the shared library when you want to share it again..”
Say 3 edit stations. Edit A wants to add some broll to Library-MASTER. Edit A announces “I want to use MASTER, please close it if you have it open.” Edit A proceeds to ingest & keyword new broll, then closes the library. Edit B now opens the library, wants to add the new broll to their local library ( Library-EDIT_B). How do the editors quickly add new broll, that gets added frequently, to their local libraries? Does the ingesting editor use a whiteboard to list import times, so others can sort clips by “added to library” timestamp? Another method?
On projects, would the best method be for the modifying editor to add a version # to the project when copied back to the MASTER library, so the original MASTER shared is not overwritten?
-
Bob Woodhead
November 30, 2015 at 6:23 pm in reply to: Editing RGB 4:4:4 footage from Canon C300 MKiiWell, spit. Not sure what happened before… ME appeared to be “stuck” on the first frame, but no error, and the time remaining was running. Just did it with your setup, and it worked. Still seemed to hang for a few seconds (ie, the blue progress bar wasn’t moving) but then it took off. I was messing with a few more encode settings, beyond the default after selecting ProRes 4444, so maybe it was op error.
Right, now just need Canon/Apple/someone to give us a native import for 444.
OT – anyone know which external recorder works with Canon RAW? That is, it records RAW. We have a Atomos Shogun, which sees the RAW, but records as ProRes 422.
-
Bob Woodhead
November 30, 2015 at 11:39 am in reply to: Editing RGB 4:4:4 footage from Canon C300 MKiiDan, I tried this, and Media Encoder seems to hang when I start the transcode. It can scrub the 12 bit 444 clip OK, so I know it can “see” it, but it just doesn’t move forward on the transcode. Could you export/zip up the preset you’re using & send it to me? Perhaps there’s something wonky with the custom preset I created. I’m editingfx@gmail.com Just shot a bunch of test footage, and didn’t realize I’d be stuck on the FCPX connection. Thanks!
“Constituo, ergo sum”
Bob Woodhead / Atlanta
CMX-Quantel-Avid-Premiere-FCPX-AFX-Crayola
“What a long strange trip it’s been….”