Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Relinking to Dual System Audio across different systems

  • Relinking to Dual System Audio across different systems

    Posted by Ben Insler on June 7, 2011 at 8:22 pm

    Hey All,

    I’ve searched this and can’t find an answer – apologies if I’m bringing up old frustrations.

    I’m working on a RED edit, dual system, sound synced in FCP. For travel purposes, I have two sets of offline media: ProRes422(HQ) for the MacPro, and ProRes(LT) for the MacBook Pro while on the road. Audio is 24bit 48K 6CH WAV. The ProRes(LT) media was transcoded directly from the 422(HQ) media, then copied to the MacBook Pro. The audio files were copied directly in its native format from the MacPro to the MacBook Pro. Both systems are essentially mirrored except for the video hardware in the MacPro. Neither Media drive is journaled.

    Passing projects back and forth between the two sets of media has been almost seamless, except for the audio. Anytime I take a project from one system to the other, all the audio reconnects with the error saying that the “media start and end” and “reel” attributes do not match the original. Picture reconnects fine. Forcing the audio to reconnect causes Final Cut to return the error that some of my out points may have been adjusted. I have hardly noticed any sync problem as I’ve proceeded passing project back and forth between two systems, but have found one or two places where sync has dropped ever so slightly.

    Can anyone explain why this is happening? The audio files are identical.

    Thanks!

    Ben

    Matt Lyon replied 14 years, 11 months ago 3 Members · 8 Replies
  • 8 Replies
  • Jeremy Garchow

    June 8, 2011 at 2:12 am

    Might be a dumb question, but how exactly are you swapping projects?

  • Ben Insler

    June 8, 2011 at 4:26 am

    Copy FCP Project file from one system to another, reconnect media, update sequence settings to match video codec and resolution.

    Ben Insler
    Editor
    Telemark Films

  • Jeremy Garchow

    June 8, 2011 at 4:36 am

    Just a suggestion, but before you reconnect on laptop, set the project to a 23.98 easy setup. Then quit Fcp. Then reopen the project. Then reconnect. Follow exactly.

    The audio was dragged/dropped to new drive or media managed?

    What was the source of double system?

  • Ben Insler

    June 8, 2011 at 4:55 am

    Copied directly through finder from one system to the next.

    Don’t honestly remember the source of the sound system. It was recorded by a recordist to a CF card and haven’t had a problem with is since when the edit has been contained to one system.

    Thinking it over, I don’t remember having the problem the first few times I passed the project back and forth, but I could be wrong about that. I thought it was a journaling issue since the media was stored on my MB Pro’s hard drive, which at the time was not partitioned. I recently upgraded the hard drive in the MB Pro, partitioned it with a non-journaled media partition. I recopied all the media over from the original media on the MacPro to the new partition. Still happens.

    Ben Insler
    Editor
    Telemark Films

  • Jeremy Garchow

    June 8, 2011 at 5:19 am

    Journaling shouldn’t have anything to do with it. No reason to partition your drive.
    Media drives are totally fine to be journaled, despite the rumors.

    Try the method outlined.

  • Ben Insler

    June 8, 2011 at 3:28 pm

    Tried the method you suggested – same outcome. Audio reconnect returned the same errors. Here’s what I tried.

    Cleaned up the project so that it contains only the media and my latest sequence. Here are all the approaches I tested:

    -Change sequence settings to 24p easy setup before reconnecting
    -Change sequence settings to match low res offline media settings before reconnecting
    -Media manage project to offline 24p easy setup before reconnecting
    -Media manage project to offline low res offline media settings before reconnecting

    I have noticed that I was incorrect earlier regarding the sequence audio setup. The sequence is set to 48k 16bit, where the source audio is recorded at 48k 24bit. I know this shouldn’t be a problem, but could it be causing any issues at all?

    Also, not to change the subject, but I’ve practiced staying away from journaled drives. They have cause me many headaches with multicam clip sync, and I assumed the situation could be the same when merging dual system sync sound with picture. But maybe not…

    Ben

  • Jeremy Garchow

    June 8, 2011 at 5:03 pm

    [Ben Insler] “-Change sequence settings to 24p easy setup before reconnecting
    -Change sequence settings to match low res offline media settings before reconnecting”

    Yeah, but did you quit FCP in between changing the easy setup and reconnecting?

    What is weird is that the reel isn’t coming over. In your orignal project, are there reel numbers for the audio files?

    Was this a 788T or similar Sound Devices audio recorder? Perhaps it’s time to find out what exact device this came from.

    Look in your original project, is the audio tc 24p or NTSC based?

    [Ben Insler] “The sequence is set to 48k 16bit, where the source audio is recorded at 48k 24bit. I know this shouldn’t be a problem, but could it be causing any issues at all?”

    It shoudn’t and can be an easy fix before you reconnect. THere is something going on before that stage, though, if you ask me.

    [Ben Insler] “They have cause me many headaches with multicam clip sync, and I assumed the situation could be the same when merging dual system sync sound with picture. But maybe not…”

    Multicam sync? Meaning a/v sync? tc sync? Genlock sync? This should have nothing to do with journaling. Running a partitioned drive that has OS on one side and media on another is asking a whole lot form that one drive. Many raid and drive manufactures recommend running journaling (although you will hear varying reports on which is best or not). Journaling helps when your computer crashes and helps to prevent corruption by returning your drive to it’s last known “good” state before things went awry. This is very important when running drives with media. Drives (even single drives) are so fast these days that journaling doesn’t slow them down enough to be noticeable. It is also selectable (meaning you can turn it on and off in the disk utility at will without reformatting, as long as it’s not a partition with an OS on it. Then journaling is on all the time).

    Jeremy

  • Matt Lyon

    June 10, 2011 at 8:23 pm

    I was reading this thread and I thought the issue might be similar to another thread I responded to:

    https://forums.creativecow.net/thread/8/1134885

    Ben, maybe it all goes back to how the FIRST import was done? As I mention in my other post … FCP has a loooooong memory for imported media attributes.

    And I have to agree with Jeremy, leave Journaling on! That being said, were you able to perform a test that specifically proved that journaling caused your issues? Then I think we’d all be interested to hear about that.

    Matt Lyon
    Editor
    Toronto

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