Matt Lyon
Forum Replies Created
-
Which version of 2020 are you running? I had similar issues and it turns out there was a bug in 2020.9 … upgrading to 2020.10 fixed the problem.
-
Shane, in the past I’d agree with you about AMA, but v8 of MC finally seems to be able to handle AMA acceptably for longer form cutting with some codecs. I’ve done 2 half hour episodes now with 1080p XAVC from an FS7 via AMA linking and it worked very well. We even had some 4K shots in the show too. People have told me that AMA linked pro-res also works well. (I would never have attempted this in MC 7, fwiw)
With AMA linking, I imagine processor speed is a factor as much as hard drives. We are on an HP z820, so it’s a pretty new machine. I haven’t tried e-sata though for drives. Thunderbolt here (and in limited testing, USB3 even worked fine)
Matt Lyon
Editor
Toronto -
I agree with Nick, using nests is definitely a bad idea. The merged clip workflow is standard practice. If your sound guy is trying to re-conform the session to the original audio files, he should be able to do so based on reel names and timecode of the audio files (assuming they are present).
If you enable overlays in your viewer window, and turn on timecode overlays, you can see the timecode for all audio clips for wherever you park your playhead. Then you can match frame back on a few of your audio clips and compare the timecode of the original file to the timecode in the merged clip and make sure they match.
The main “issue” with the merged clip workflow is that it renames all your clips to match the video clips. Perhaps that is what is tripping up your sound person? It will be easier for your post sound people if your OMF uses the names of the source audio files. I posted a while back about a technique for renaming your final timeline audio back to the original source files:
https://forums.creativecow.net/readpost/8/1156962
HTH,
MattMatt Lyon
Editor
Toronto -
I had a similar issue in MC 7.0.4 w/ NITRIS DX. Since our AVID version and system setup is very different, it is very possible my solution does not apply, so take it with a grain of salt:
I worked with AVID tech support directly on this one: First step is to look in your console window to see what kind of error message you are getting. Every time I would switch between AVID and the desktop, or any other program, I would get “MSMRescan() took: 30s” errors, where the rescan time was anywhere between 30-60 seconds.
The solution was to throw away the AMA management database:
C:\Users\Public\Documents\Avid Media Composer\AMA Management
Once I deleted the contents of this folder, the rescan errors went away. According to AVID tech support, the program will rebuild these databases as needed. So far, I have seen no negative effects from throwing away these files.
HTH,
Matt Lyon
Editor
Toronto -
Before you address the ffmpeg issue, I think you need to figure out why FCP is drawing the waveforms wrong. That shouldn’t happen. It probably means the audio is being imported incorrectly (assuming their isn’t an issue with the files themselves). Incorrectly drawn waveforms might point to a frame rate mismatch issue, which I discuss in my tutorial: https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1
But for syncing, I wouldn’t mess with ffmpeg. Since it sounds like you are simply syncing the clips to the first frame of each media file, the workflow in FCP is pretty quick: Import the processed audio tracks in to FCP. Then you can strip the “bad” audio tracks off the video clips by throwing the files on to a timeline, deleting the audio tracks, then throw the “clean” clips into a new bin, then use the “merge clips” command to sync the video-only-clips with the new audio files. It doesn’t take that much longer then typing out a terminal command.
Matt Lyon
Editor
Toronto -
The only other tip I got from Red Giant was to make sure the folder I’d set for PluralEyes to use for temp storage was not the same as the media folder, and that I had full read/write permissions in that folder. But otherwise, the transcoding did the trick. Red Giant support was actually pretty helpful, I sent them the error log and they had an answer for me in a few days. Have you tried calling them?
HTH,
-MattMatt Lyon
Editor
Toronto -
If anyone is interested, Red Giant looked into the issue and confirmed that media generated via Resolve is not currently supported. The workaround is to consolidate/transcode the already imported footage, and then run PluralEyes with the converted media.
Matt Lyon
Editor
Toronto -
Happy to help Tancredi, but I’d rather not post my contact info on a public forum. You can find me on LinkedIn …. or just post on this thread and I can try to answer. EDL exports are pretty straight forward. For your purposes, I’d use: CMX 3600, sorting “master”, reel conflicts: “generic edits”, turn off all “EDL NOTES” except ‘File names’ (or clip names). Turn on “OMIT TRANSITIONS” probably. Turn off all audio too (unless you need that info).
If you’ve never read an EDL before, it will take a second for you to figure out which column corresponds to what, but once that makes sense you’ll be off to the races.
Be aware that EDLS use “exclusive” timecode numbers. Meaning the “OUT” timecode is the frame AFTER the last frame that is in the edit. This will makes sense once you compare the in and outs of a few clips in the timeline to the numbers that are actually in the EDL.
HTH,
Matt Lyon
Editor
Toronto -
You could export an EDL and read the timecodes off that.
Matt Lyon
Editor
Toronto -
I just encountered a similar issue. Try exporting using File>Export>Quicktime Movie…” then ENABLE “recompress all frames”.
HTH,
Matt Lyon
Editor
Toronto