FORUMS: list search recent posts

FCPX Does not import Dual Recorded Audio Files correctly

COW Forums : Apple Final Cut Pro X

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Declan Smith
FCPX Does not import Dual Recorded Audio Files correctly
on Feb 1, 2018 at 6:21:52 pm
Last Edited By Declan Smith on Feb 1, 2018 at 10:15:50 pm

Here is the setup.

Zoom F8 recorder setup to dual record (i.e. safety track). Ch1 & Ch2 set as stereo linked, paired with 5&6 for safety tracks.

Ch1 & Ch2 TrackNames set as Boom-Mid & Boom-Side for auto iXML role assignment
Ch5 & Ch6 TrackNames set as Boom-Mid & Boom-Side for auto iXML role assignment

SD Card set to record separate files (i.e. not poly WAVS)

In FCPX, I go to import the folder with two files in for example:

Scene_35-T001_Tr1_2_D.WAV
Scene_35-T001_Tr1_2.WAV

After import, the only file in FCPX is shown as Scene_35-T001_Tr1_2_D.WAV but finder will link to Scene_35-T001_Tr1_2.WAV

If I import just Scene_35-T001_Tr1_2_D.WAV, it will show Scene_35-T001_Tr1_2_D.WAV in the browser which links to the correct file (Scene_35-T001_Tr1_2_D.WAV) in finder.

If I subsequently try importing Scene_35-T001_Tr1_2.WAV, another entry gets added in the FCPX browser as Scene_35-T001_Tr1_2_D.WAV. Now, both entries for Scene_35-T001_Tr1_2_D.WAV point to Scene_35-T001_Tr1_2.WAV in Finder, so the original reference for Scene_35-T001_Tr1_2_D.WAV has been corrupted too.

Now I remove both files from FCPX.

This time I import Scene_35-T001_Tr1_2.WAV and the browser sees it as Scene_35-T001_Tr1_2.WAV and finder links to the correct file Scene_35-T001_Tr1_2.WAV

If I subsequently try importing Scene_35-T001_Tr1_2_D.WAV, another entry gets added in the FCPX browser as Scene_35-T001_Tr1_2.WAV. Now, both entries for Scene_35-T001_Tr1_2.WAV point to Scene_35-T001_Tr1_2_D.WAV in Finder, so the original reference for Scene_35-T001_Tr1_2.WAV has been corrupted too.

Both these files have exactly the same timecode, exactly the same length, just different recordings of the same thing (i.e. safety levels), but they are NOT the same thing and I suspect FCPX is doing a cheap comparison to determine if they are the same and getting it wrong!

The tried and trust sha1 sum's are different, proving absolutely, that the files contain different content:

shasum Scene_35-T001_Tr1_2.WAV Scene_35-T001_Tr1_2_D.WAV

dcc01d003ad176c2d775ee2907f9a0f2efc5eb75 Scene_35-T001_Tr1_2.WAV
33b4c07264ae07b725de1f3c5c34e70cd247066e Scene_35-T001_Tr1_2_D.WAV

So these are different files and FCPX *should* treat them differently.

I've reported this to Apple, but thought I would share it in case anyone else has had similar problems.

Note that this seems to only be a problem with stereo files. Mono files import correctly.

Declan Smith
http://www.madpanic.tv
FCPX / Adobe CS6/ FCS3 / Canon XLH1 / Canon 7D / Reason / Cubase

"it's either binary or it's not"


Return to posts index

Jeremy Garchow
Re: FCPX Does not import Dual Recorded Audio Files correctly
on Feb 1, 2018 at 11:47:48 pm

I would suggest using wave agent and whip up a poly file (I think you’d have to mono the stereo first) and you can even mark the safety tracks for less confusion.


Return to posts index

Declan Smith
Re: FCPX Does not import Dual Recorded Audio Files correctly
on Feb 2, 2018 at 12:45:23 am

I must admit, I prefer working with polywavs, and the poly file generated from the F8 works fine. Polywavs give great flexibility under FCPX. I was running some tests on Mid-Side recording as I need to deliver separate files to a client on a location sound recording gig I will be doing. Having two separate mono files for MS creates a little more work, whereas having a stereo file lends itself much better to work with MS plugins such as MSED.

I have gone through some extensive testing scenarios with Apple to narrow down the problem and it appears to only affect stereo files. If, for example, I record 4 stereo files and import them into FCPX, only one will be imported and it will link to a different one on disk, regardless of whether they are safety tracks.

Good suggestion about marking the safety tracks differently at source to make absolutely clear what they are, although FCPX suffixes them with an instance ID, for example, I have labelled the tracks:

Ch1: Boom-Mid
Ch2: Boom-Side
Ch5: Boom-Mid
Ch6: Boom-Side

FCPX changes these to:

Boom-Mid-1
Boom-Side-1
Boom-Mid-2
Boom-Side-2

Declan Smith
http://www.madpanic.tv
FCPX / Adobe CS6/ FCS3 / Canon XLH1 / Canon 7D / Reason / Cubase

"it's either binary or it's not"


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2018 CreativeCOW.net All Rights Reserved
[TOP]