Forum Replies Created

Page 62 of 788
  • Oliver Peters

    October 19, 2019 at 8:04 pm in reply to: Bayes reports on IBC

    [Herb Sevush] “I thought the extra time came from slow coffee machines.”

    Herb, you forget. Bill never has time for coffee, because he never has to render. His system is now so blazingly fast ☺

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 18, 2019 at 7:46 pm in reply to: FCP X 10.4.7 is out

    [Ken Bennett] “Will Mojave run M$ Word: Mac 2011 and Excel: Mac 2011 as well as Adobe Suite 6.6”

    MS Office, yes. Adobe CS6, not sure.

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 18, 2019 at 6:17 pm in reply to: FCP X 10.4.7 is out

    [Eric Santiago] “Sadly, both also targetted HD for NTSC Broadcast but I always (on my own terms) keep a 4K and up version for safety.”

    When I’m grading in Resolve, I like to render clips at “source resolution” so those files are as large as they started. Then the finishing folks have the option.

    But, yes, if I’m spitting out a finished timeline from Resolve, it’s good to at least export a textless 4K to future-proof, even if the request is for an HD deliverable. The only downside is when the creative editor and director know they have 4K to work with for an HD show, they tend to get carried away with punch-ins. So the 4K textless master now includes a bunch of blown up shots.

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 18, 2019 at 5:28 pm in reply to: FCP X 10.4.7 is out

    [Eric Santiago] “I finished two features on it but rarely touched the editor since they are all pic locks from other NLEs”

    The problem I’ve run into when mastering out of from Resolve is that a perfect conform depends on two things:

    1) how diligent the front end teams (DITs, asst editors) have been in properly prepping the oddball media from the prosumer cameras with frame rates that don’t match the project rate, and

    2) how complex the effects are – specifically speed ramps and plug-in effects/filters/transitions.

    For most narrative projects, like a fairly standard feature film, finishing out of Resolve works well. However, for more convoluted jobs, it’s often best to render source clips and then roundtrip back to the original NLE. Then relink to the graded clips and re-establish all effects.

    This is why Symphony remains viable, why FCPX and Premiere Pro are beefing up color features, and why BMD is pushing Resolve into editing. It’s all to get rid of the roundtrip.

    But regarding the edit features in Resolve, right now it seems very schizophrenic with both the cut and the edit page. They offer completely different paradigms. You can go between them, of course, but common functions, like trimming, aren’t consistent between the two modes.

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 18, 2019 at 1:24 pm in reply to: FCP X 10.4.7 is out

    [Bill Davis] “The Catelina migration forced me to dig deep into my OS and clear out years of 32-bit cruft. “

    When you look at the 32-bit apps and pieces that are left over on your hard drive, many will be from old installers. For example, you’ll find old Microsoft Office and Adobe app managers, etc that have been replaced by current 64-bit versions. However, the old installers are still there, because they never got cleaned out. Truthfully, a totally clean install from the ground up is probably the best tactic with Catalina.

    [Bill Davis] “Hopefully, it too will be custom “tuned” to the new Metal environment and improve things even further. “

    I’m not exactly sure what that means. Metal is “tuning” the software to the hardware, not the other way around.

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 18, 2019 at 11:56 am in reply to: FCP X 10.4.7 is out

    [Michael Gissing] “I was beginning to fret as there hadn’t been a Resolve update for 5 weeks but they just released 16.1 . “

    Since the Resolve editor keyboard depends on 16.1, they probably wanted to get it out of beta ASAP.

    https://digitalfilms.wordpress.com/2019/10/14/davinci-resolve-editor-keyboard/

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 15, 2019 at 8:45 pm in reply to: Michael Cioni + frame io

    [Tony West] “You and Greg have been doing more flacking for the company that neither of you work for then they are.”

    There’s no reason to get rude. We fully understand your workflow, but don’t necessarily use it ourselves. We’ve be offering suggestions that might be helpful. I’ve done testing in the past two days to verify what does and does not work. There are some issues that are likely easy to be resolved and others that will likely take more engineering effort. You seem to be copying and pasting the customer service chat feedback. While their customer support folks are friendly and helpful, I’m not sure that’s an indication of what they will or will not be able to do in the future. No slam against them. Just how the business works.

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 15, 2019 at 7:33 pm in reply to: Michael Cioni + frame io

    [greg janza] “For anyone following this very convoluted thread, if you use Premiere to export a split track pro res file and then upload that file to Frame.io…”

    This also works in FCPX if you export a Multitrack Quicktime and upload through the web portal, or if you upload a camera clip as is through the extension (drag and drop, not Share). Anytime encoding is involved, you must manually control how the encoding application deals with the audio track configuration. No real surprise there.

    In my testing, I think part of the issue is the FrameIO Share Destination presets – H264 and Source. Both presets seem to only upload stereo or mono clips. Multiple stereo channels are muxed to one stereo track on the encoded file. Multiple discrete mono channels are muxed to a single mono track. The Source preset is completely wrong as it is NOT set to a “same as source” export. It would seem to me that fixing these two presets could be done very quickly if Frame addressed it.

    The second issue is Frame’s media player. Since the player is a standard media player like any basic web player, I don’t see any way that it will allow discrete monitoring or selective monitoring of multichannel content. It’s either going to be mono or stereo. I don’t see that changing anytime soon, as it would likely require an entirely new media player across all platforms that can access Frame (web, extensions, iOS, etc).

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 15, 2019 at 6:43 pm in reply to: Michael Cioni + frame io

    [Oliver Peters] “[Tony West] “One thing that might be helpful is if you post the Frame link to the test file you are talking about.”

    I’ll try to get to that later today. I’d rather do that offlist. Where can I send it?”

    Tony, I have those files if you want to take a look. Send an e-mail or ping me through the website.

    – Oliver

    Oliver Peters – oliverpeters.com

  • Oliver Peters

    October 15, 2019 at 6:34 pm in reply to: Export with video source file name
Page 62 of 788

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy