Matt Trubac
Forum Replies Created
-
The dead pixel only appears to be moving because of the stabilization. I had tried the “open in timeline” from the angle editor idea thinking maybe I could fix the dead pixel inside the “complex clip” timeline and then use the built in FCPX stabilize function back in the angle editor so that the repaired (covered) pixel would move with the rest of the shot as it is stabilized. It didn’t work. When I “opened in timeline” the stabilization on the video links through into the timeline, and I had the same problem.
My trial of Lock and Load had expired and the old version wouldn’t do anything. I installed an updated version that still showed as being expired, but worked with a watermark. Adding Lock & Load after DH_Reincarnation allowed me to fix the dead pixel, and then move that fix with the rest of the shot.
Solved!
-
This is awesome thanks!
I always hit home to jump to the beginning of a clip with a range in the event browser.. and I am constantly jumping to the first clip in my event. Its a habit I still need to break from FCP 7.
-
Drives me crazy too. Does the USB 3 drive respect the system preference to not put drives to sleep on your 2013 MBPr?
The fact it works fine on one of your systems and not on others makes me think it is a hardware problem.
-
I don’t know if you’ve experienced it, but USB3 on the 2012 and newer macs has problems. It ignores the system preference to put hard drives to sleep when possible. Even with the setting unchecked my USB 3 drives will spin down every few minutes. SUPER ANNOYING! USB 3 also has problems with disconnecting, especially after a system sleeps.. You get messages the drives were improperly disconnected and to eject your drive before disconnecting it. I’ve had a few corrupt drives from this. I get a message when the drive mounts that it’s damaged and cannot be repaired. I reverted to USB 2 for bare drive docks on my 27″ late 2012 iMac. Since the 10.8.5 update I’ve had similar problems with USB 2 though. I installed the supplemental update which I thought would solve it, but it is still happening… Less frequently. I’ve heard reports on apple user forums that it happens with thunderbolt drives too but I have not experienced it yet. The only thunderbolt drive I have is a Pegasus R4.
Apple needs to get their act together. I think they’ve gotten a little too comfortable riding the iPhone wave. Waves don’t last forever.
-
I’m wondering how the FCPX XML workflow will interact with multicam audio.
-
Not to the original clip of a multiclip. I believe in legacy I could collapse the multiclip and match frame back to the original clip. In X you have to hunt it down in the angle editor.
-
Stabilization and Rolling Shutter on Multicam and/or the option to collapse and uncollapse multicam clips, and match frame to the original clip.
-
Roles and Keywords
-
I’ve had a pegasus r4 for about 3 months. I bought a refurb unit. The first week I had it I received several bad sector warnings, and then the drive completely failed. I called Promise, and had no issues with their support. They answered the call quickly, identified the problem within a few minutes. They shipped a replacement drive, I swapped it in and the raid automatically rebuilt. No problems since.
I’ve been happy so far. I keep a spare drive handy. I’ve received other DOA drives from multiple manufacturers.
-
Mixed news. I still don’t know exactly what caused this, but exporting and importing an xml brought all of my media back online! The downside is that the filters on the clips that were missing have all been reset (native and third party).
Filters are still set on the original project.. so I guess I might be doing a lot of copy and paste of my color and curve settings from the missing clips in my original project to the recovered project.
I’m working with Apple and am hopeful they can at least determine a cause and it gets fixed someday.