[John Godwin]

I have a much bigger trust issue with cloud apps. As long as I have software resident on my computer I can access my work and at the minimum rescue it and get it into a form I can use elsewhere. If someone in “the cloud” decides to shut something down that’s a lot more troubling to me than stopping development on a program that I can still use for months or years if necessary, because its still available.

Best,
John

[John Godwin]

Call me Tuesday, shooting Monday.

Be good to see you.

Best,
John

[John Godwin]

I’ve got a 1200 in the basement I’ll loan you. Just test it with a throwaway tape first.

Best,
John

[John Godwin]

Sure did. But it was a valid question anyway. ;))

Best,
John

Best,
John

[John Godwin]

Bret,

So far the benefit to my clients is that I can do more in the same amount of time. So I have more time to polish and add fit and finish and finesse and stay within their expectations. The drawback there *could* be mine … If the client said “Well, just finish faster and lower the bill”. So far everyone has been happy with both the invoice that meets their expectations and the product that exceeds those expectations, for more or less the same amount.

Best,
John

[John Godwin]

I usually charge by the hour. This particular stuff is on a project basis. So I can take on another project or two with the time saved.

I suppose if you work for a post house or you always have all your time booked it matters not, not so much. (I do work almost constantly, shooting or editing.) Knowing I can finish a project faster means not having to allow more time for a given project (theoretically) and not having to turn other work away, which means keeping clients happy because I’m available, and similar intangible benefits.

Best,
John

[John Godwin]

Paid. That’s important.

But more to your point, they’re personal stories with interviews, narrative, music and b-roll. I’ve done these for several years for this particular client on an annual basis … Lost track of how many years but when I started I was using Liquid Chrome. When Chrome was discontinued I gave up and bought Macs and FCP. After Liquid I never quite got used to some of the differences (limitations, in my mind, but I’m not trying to be snarky there) I encountered in FCP. But I’ve certainly had far fewer computer issues with Macs.

FCPX feels much like editing in Liquid, actually, to me, which may explain at least MY comfort with it. But it’s smoother and takes far less rendering once I start layering on effects and such.

So, if I can do an edit of the same quality (or better) faster in FCPX and either charge the same or have time to work on other projects it’s certainly a net gain for me.

I wonder what job the OP was taking on?

Best,
John

[John Godwin]

What a coincidence. I finished three today, on FCPX, for which I’m getting paid the same as last year on FCP7. In half the time.

Best,
John

[John Godwin]

I always feel vaguely dissatisfied replying to myself …

Anyway, about the glitches, I think I know the cause. I was copying all the data on the 4 TB firewire Graid onto my new 8 TB Thunderbolt drive. Apparently that does something somewhere that just strains the resources and causes the green glitches. I’ve been editing much of today using the new drive (it IS blazingly fast) and no glitches at all. No problems with plugins or anything else. Maybe this tidbit will help someone else.

Best,
John

[John Godwin]

Back on the original subject of this thread – I got the first green frame glitchy renders today that I’ve seen. These are on clips without any third party filters at all, only FCPX color correction, and a couple under FCPX standard titles.

I’ve been using the iMac internal drive (to see how it handles the load) and a Graid firewire drive. Today I received an 8TB Thunderbolt Graid, and hooked up and copied over the events & projects due today, and worked on them, then exported them to vimeo, both rendered and unrendered.

That’s when the green flash frames (2 in one project, 4 in another) started showing up. The 2 that appeared and alerted me to the problem were on a video that was unrendered on the timeline and rendered on export and upload.

The variable is the Thunderbolt Graid (and I also updated Coremelt SliceX today to their new version, but was only using it on a couple of clips in the 4-glitch project, and thats not where the glitches occurred. Had I seen the issue before I would have waited on the update.)

So, no issue before the TB drive. For full disclosure I have the TB drive copying much material over from the firewire drive in the background, and maybe that has *something* to do with this, but still. Never saw this before today.

Dropping an unaffected adjustment layer over the offending glitchy section almost always forces a rerender and fixes it.

This is all on the latest FCPX and new 27″ iMac, maxed out.

Best,
John