Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro X SMB / Catalina / Moving Libraries off a share

  • SMB / Catalina / Moving Libraries off a share

    Posted by Jeremy Garchow on January 18, 2020 at 4:21 am


    Do you any of you on new Mac hardware, SMB Shares, that move libraries off of shares have any issues with FCPX libraries that remain on the share?

    I’m having issues when a Library is moved off of a share from new Catalina based hardware, reopened on the share (to be clear, this is the original Library, NOT the transferred library). Open opening the orig library on the share, after scrubbing and playing, the Mac will shut down the entire 10Gb connection (obviously SMB share disconnects, internet will do down, etc). After a recovery period, and remounting the share, the library, even though it hasn’t moved, will not stabilize on any Catalina machine (lots of Console errors and faults about a “ BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode revoked while in use: ”

    Some times clearing cache will fix it, sometimes it won’t.

    I can open this exact library on a machine with Mojave, and it works. It’s confounding.

    Library and Media is on the SMB share, cache is on local SSD drive of MBP.

    Steps to reproduce.

    1) Library on SMB share. Quit fcpx.

    2) Copy that library off of the share.

    3) Go back to share and open the library (still in its original location)

    4) Scrub around and play for 10 or so seconds. Share ejects.

    This happens on new 16” MBPs, but MacPro Tubes with Mojave (same storage, same
    Library) hold stable and work just fine.


    Jeremy Garchow replied 4 years, 4 months ago 1 Member · 1 Reply
  • 1 Reply
  • Jeremy Garchow

    February 10, 2020 at 6:32 pm

    To update this, it looks like there’s a fix.

    Studio Network Solutions was able to get a fix together until there’s an official fix from Apple in the OS.

    As of MacOS Catalina 10.15.3, there is still not a permanent fix from Apple.

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