Replies – Forums – Oliver Peters – Page 71

Forum Replies Created

Page 71 of 788

← 1 … 70 71 72 … 788 →

Oliver Peters
August 22, 2019 at 12:50 am in reply to: Compressor, FCPX, and EVA1 footage

Don’t know on the updates for the camera. That’s the Dir/DP’s territory. He’s an outside client. I do have access to some other EVA1 footage from a different source and can double-check that tomorrow.

Compressor is the most current version, whatever that number is.

But, as I say, it’s fine with FCPX. FWIW – ProRes RAW is also treated differently in the two different apps.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 21, 2019 at 6:19 pm in reply to: Looks like the FCP X forces converted another AVID editor. Wonder who gets the toaster prize?????

The thing is, on its own FCPX is a wonderful editor. In a small workgroup, it can also be made to function in a quasi-collaborative manner through various workarounds. But it simply has too many holes for a lot of companies to make the switch. Interchange with other apps is worse and collaborative working methods are worse. Until that’s addressed, these sorts of stories will continue to be outliers. Unfortunately the sad truth of our business is that processes work best when you restrict yourself to a single ecosystem.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 20, 2019 at 6:28 pm in reply to: Looks like the FCP X forces converted another AVID editor. Wonder who gets the toaster prize?????

[Paul Neumann] “Sharepoint site”

As an FYI – FCPX Libraries get messed up with these types of services. Definitely DropBox. If you send a Library, make sure to zip it first.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 20, 2019 at 3:38 pm in reply to: Looks like the FCP X forces converted another AVID editor. Wonder who gets the toaster prize?????

[Neil Goodman] “Somehow a 30 year old program implemented a better solution to background processing than FCPX that gives the user more options.”

Not to mention something like PhraseFind!

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 20, 2019 at 12:04 pm in reply to: Looks like the FCP X forces converted another AVID editor. Wonder who gets the toaster prize?????

Well, it’s easy to say he switched, but the real proof is whether he can make headway in using his now-preferred NLE on actual jobs that aren’t projects totally under his control. Especially in series work – you use what the team has decided on.

It’s also 8 years at this point and we are still pointing to a very small number of “conversions.” Yes, I know there are large installation here and there. OTOH, there are quite a large number of post suppliers in all of the major markets around the world who readily field 80 to 100 Avid systems on long-form project rentals. And…those are often running on older hardware and software versions. FCPX has yet to come up with a competitive collaboration solution to challenge this.

So the story is nice – and thanks for posting – but isn’t it just another drop in the ocean?

BTW – some of the selling points in his video are meh. For example, compound clips are not unique to FCPX. You can do the exact same thing in Premiere using nested sequences. Works the same way, except that the timing isn’t messed up in the main sequence if you change the timing within the nest, which would be the case with the magnetic timeline and compounds in FCPX.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 19, 2019 at 2:25 pm in reply to: SNS Extension

In all seriousness, though, this is a great selling point for both SNS and FCPX. It would be nice if LumaForge, QNAP, and others would do something similar.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 18, 2019 at 9:47 pm in reply to: Digital hits, usually green blocks, on renders

I run into this constantly with Adobe apps (2013 MP, 8-core, D500). Usually when I have higher res media like 4K footage. I almost never have a problem with FCPX or Compressor. Resolve is so-so. Again more likely with higher res outputs. I also run Mac Fan Control cranked to max speed. It helps, but is not a cure.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 18, 2019 at 9:43 pm in reply to: Ain’t really a debate–rendering video?

[greg janza] “The only rendering that needs to be done these days is on export.”

There is a caveat to that if you work in Premiere, FCPX, or Resolve. If you render as you go (or cache in Resolve) and set your settings to the output codec (such as ProRes), then the export effectively becomes a file copy. You typically have to enable using this media in the export dialogue, but it can make the exports – especially in FCPX and Resolve – lightning fast, IF you are exporting to the same codec and settings.

– Oliver

Oliver Peters – oliverpeters.com
Oliver Peters
August 18, 2019 at 12:33 pm in reply to: ProRes workflow

This may be helpful.

https://www.youtube.com/watch?v=PKaK397eVLI&feature=youtu.be

– Oliver

Oliver Peters – oliverpeters.com

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
Oliver Peters
August 18, 2019 at 12:31 pm in reply to: Avid and anamorphic lenses with squeeze 1:2

[Lena Gregorian] “Why the difference between the de-squeeze and timeline?”

The de-squeezed size is the size that the file becomes after you are change the pixel aspect ratio back to 1:1. Basically reversing the image squeeze created by the anamorphic lens. This sounds like Alexa footage with a file size of 2880 x 2160. So that means the lens is squeezing the image going through the lens by 2x.

The timeline setting is a standard size used for 2K scope projects. This means that your footage will be resized and somewhat cropped on the timeline.

– Oliver

Oliver Peters – oliverpeters.com

Page 71 of 788

← 1 … 70 71 72 … 788 →