Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Data Loss: NAS Storage & Error Loading Adjustment Masks

Comments

5 comments

  • Michael Roessler
    Have you tried the following:
    1. Compare the checksums from e.g. shasum after copying the files (local vs NAS)
    2. What happens if you create an archive of the local session as zip or tar.gz?
    Unpack the archive on the NAS using (a) the MacOS commands and (b) the shell commands on the NAS
    3. Use rsync via ssh instead of the Finder to copy the local session, does this make a difference?

    Just trying to sort out any problems that might be caused by the Finder or the Samba implementation of MacOS.
    0
  • Michael Lake
    Well, that was quick. Just got a reply to my bug report:

    Hi Michael,

    Unfortunately this is a known software bug that should be fixed very soon in a future service release for Capture One. We apologize for any major inconvenience.



    Kind regards,

    Phase One Technical Support

    Glad they know about the issue, but this is a serious problem that needs to be remedied ASAP. :-/

    @Quintatec: I've alread tried making ZIP, 7-Zip, and TAR archives, but those all had the same issue. I was using Kaleidoscope.app to run the diff on the folders and scan for byte-level differences. I'm wondering if there's some sort of extended attribute that gets garbled that isn't being preserved properly during compression/transfer. I haven't tried #3 yet.
    0
  • Farzaan Kassam
    I have the exact same issue. Let’s hope C1 comes out with a fix soon. I’ve lost several days worth of masking work and will need to dig through the event log to figure out what’s been damaged.
    0
  • Oldan Strange
    Same issue here. I opened a service ticket Number 304.679. No resolution as of 11/7/2018. 🙄
    0
  • Farzaan Kassam
    [quote="Oldan Strange" wrote:
    Same issue here. I opened a service ticket Number 304.679. No resolution as of 11/7/2018. 🙄


    The C1 team replied to my ticket and said they are aware of the issue and are working hard to resolve it. The temporary solution is to ensure you're editing on the same drive that you created the session with. Don't copy/paste the session at this time.
    0

Post is closed for comments.