Forum Replies Created

Page 5 of 222
  • Michael Hancock

    April 2, 2019 at 5:27 pm in reply to: Relink

    Everything is on the QNAP. Libraries and media.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2019 at 5:13 pm in reply to: Relink

    Interesting! Hopefully Ronny will chime in with some more info and insights. Bob Z set our system up and it’s been great so far. But we also make extensive use of proxies for a lot of our edits, which might help with overall performance?

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2019 at 4:41 pm in reply to: Relink

    In general, or in regards to relinking and file tracking? We haven’t had any problems with it yet, but our read/write speeds are slower on the Macs than our PCs (all over 10G).

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2019 at 3:48 pm in reply to: Relink

    [Joe Marler] “Within a given drive volume, relink is not normally necessary. You can shut down FCPX, rename every media file, move each file to a different location, go inside the library package and delete all the symlinks to the media, start FCPX and it will find all the files and rebuild all symlinks with the new filenames and locations. It is apparently storing the inode or other locator within two SQL tables inside CurrentVersion.fcpevent.”

    I am not seeing this behavior for files stored on our QNAP. When the storage was local I could rename a file at the finder level with FCPX open and it would keep it linked to the file. On our network storage any change in the file name/location throws the file offline and a forced relink is necessary.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2019 at 2:23 pm in reply to: File deletion

    I had this happen with a png file the other day. The original png was deleted and a new one was put on the server with the exact same name – FCPX kept showing the old png (which didn’t even exist anymore). I shut FCPX down and reopened it – old png was still there. Went into the library to delete the alias for it – didn’t fix it.

    I ended up having to import the new png and overcut it into my sequence. I never did figure it out.

    —————-
    Michael Hancock
    Editor

  • Michael Hancock

    April 2, 2019 at 2:20 pm in reply to: Relink

    I don’t think so. And I agree 100% that it wastes more time than it saves.

    —————-
    Michael Hancock
    Editor

  • [Robin S. Kurz] “I’d actually like to see any if not all of a clip’s VIDEO parameters be accessible in the event, too, yes. Not just audio. So you can do stuff like scaling, stabilization, applying effects etc. etc. in the event as well, instead of doing the “Open clip” spiel there, too. At least you batch apply LUTs if needed, so there’s that.”

    YES! YES! YES! YES!

    —————-
    Michael Hancock
    Editor

  • [Robin S. Kurz] “Sure there is. “Open Clip” and change it there. If that’s in fact worth the effort…”

    Totally forgot about Open Clip. Nice. Does this break relinking to the original clip though? Do you know if it causes any issues with XMLs to Resolve or another program?

    [Robin S. Kurz] “That’s not a shortcoming of FCP (especially since every other NLE will do the same), it’s how THE CAMERA is recording. “

    In Premiere you can change the playback rate in the browser. But it’s not recommended because of relinking issues (unless that’s changed – I inherited a project where it required a ton of manual relinking and overcutting). I believe in Avid you can also change the playback rate of the source clip, and this doesn’t break relinking. So it can be done in other NLEs since it’s just the software using clip metadata to affect the playback rate. Resolve can change the playback rate too, but again – not sure about relinking since I haven’t tested it.

    I’d love to see a checkbox in the inspector in FCPX where you can tell a clip to playback back at XXfps, and it will play back at that speed in the browser and will default to cutting it into your sequence at that playback rate. So 50fps footage would playback at 25fps in the browser and when you cut it into your 25p sequence it cuts in at 50% speed. If you decide you want it at 50 you just untick the box or change the speed settings back to 100%.

    —————-
    Michael Hancock
    Editor

  • [Rikki Blow] “So is there a way to force the browser to play everything at 25?

    Unfortunately, no. In the browser it will always play back at the native frame rate.

    A workaround is to create a new sequence at 25fps, drop all your 50fps clips into the primary, select all the clips and set the speed to Automatic to slow them down to 50%, then use that as your selects reel and copy/paste clips into your actual working sequence. Not elegant at all, but it works!

    I’ve sent this as a feature request a couple times to Apple (allow us to set playback rate in browser). You should send one too.

    https://www.apple.com/feedback/finalcutpro.html

    —————-
    Michael Hancock
    Editor

  • [Tangier Clarke] “It makes sense to provide students with what will make them more marketable and/or get a job.”

    Definitely. And as you can see from Ronny’s post, each market will be different. FCPX seems to enjoy much deeper penetration in Europe than it does in the US. I’m not sure why.

    Personal example – I work for a production company that uses FCPX for 99% of our projects, but we’re the only ones in town that I know of who do. Everyone else is on Premiere, and we’re proficient on Premiere if clients request it. If I was teaching at one of the local universities or high schools and wanted to prepare my students for this market – I would teach Premiere.

    —————-
    Michael Hancock
    Editor

Page 5 of 222

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