Field Recorder "Select Areas to search"

[domilik]

I know, this has been discussed here years ago, but once again the question:

I have a single edited guide track (shortened downcut version of a documentary), with cryptic file names, BUT with correct TC information regarding the long project. I have a seperate folder with the original DME stems, 3 wave files, and I want PT to reconfirm the new Guide track with this three files.

I should select this folder in "Select Areas to search", and then apply "Expand to new tracks based on TC information" on the guide track.

But when I do so, PT creates dozens of new tracks with a huge amount of files he finds in audio files folder as well, ordered in chaos.
There should be just 3 new tracks, with the confirmed DME, right?
Why is there a "Select Areas to search", when it searches everywhere?

Am I missing something in workflow?
Thanks for a hint!
Dominik

[Frank Kruse]

If you base the expansion only on TC it will match every file it finds with overlapping TC that's already in your session.

Best to expand in a separate session with just your guides and then point the areas to search to your wanted audio only.

It's also better to expand my match criteria not just TC. You have more control over stuff that way.

There's still no way to make PT ignore the clips already in your session and use the "areas to search" only. It's been a decade or more that we've been asking for it. Might never happen.

[Farhoof]

I don't think you are missing something. PT always looks in it's own bin on top of the selected area's, which is the dumbest thing ever and I wish it was optional.

I have my workarounds, but it's not intuitive at all.

[smurfyou]

^ yes you can't stop PT from looking in the session Audio Files. Yes it's really stupid.

I hate FRW and avoid it whenever possible. It's only use for me is after conform when I want to look at alternate channels. And even then it shows me every iteration of the take when I only want it to search the specified folder

[mfranken]

Hi Dominik,

If you do this often and you're willing to purchase a 3rd party app, EdiLoad can import the edit info from your PTX file containing the guide track and then with the Assembly window use this edit data to match your DME files by TC only and export a PTX file with just these tracks. Contact me if you'd like more info.

Best regards,
Mark

[domilik]

Thank you guys for your comments!
I already own and use conformalizer/matchbox for reconforming to EDL or AAF, but I did not try EdiLoad until now (yet an EdiCue user since many years). I'll give it a try, seems to be a smart thing.

But still - this simple task which I described, a single mono guide and a small hand full of wave files to confirm - should be so easy to do onboard with FRGT.

[Reckless Erik]

A nice piece of software called "Kraken" will also do what you want. Well worth checking out if you haven't already

[kosmokrator]

this behaviour is also driving me crazy.

However, in my world the need to reconform to original audio rushes is coming up so rarely that I up to this point didn't invest into 3rd party software.

However, on an upcoming feature doc this is - again - rearing its ugly head, especially since the data management on the shoots and during ingest was non-existent, which is driving me and the assistant editor who 'herited' the project completely mad.

So my question for those doing this more regularly:
Can you please point out the differences and pros and cons between EdiLoad and Kraken for the usecase of finding alts in an ocean of badly organized original footage from all kinds of sources, with no a lot of metadata and no sound reports?

Thanks a lot!

[smurfyou]

Originally Posted by kosmokrator

So my question for those doing this more regularly:
Can you please point out the differences and pros and cons between EdiLoad and Kraken for the usecase of finding alts in an ocean of badly organized original footage from all kinds of sources, with no a lot of metadata and no sound reports?

Thanks a lot!

EdiLoad is amazing but for this use I would go for Kraken. Follows along with your session and can match by metadata, EDL or transcription.

Now if you were trying to make sense of the edit and conform to the production BWF's EdiLoad has the bag of tricks to figure it out. (Kraken can also conform via EDL but EdiLoad is more mature and can load XML & AAF too)

[Tobi Adam]

Ediload's new match by timecode and guide track align is pretty powerful...