Hello Avid Forums,
Working on a show running OSX 10.7.2 and found this problem in 6.0.1, 6.0.3.2, and 6.5.2. Show shooting to XDCam HD discs. We're trying to use a workflow that worked on a previous show on Avid 5.0 (or 5.5?). The workflow was:
1) Import XDCam proxies (bringing in everything with a disc label) using several different U2/U1 drives.
2) Transcode proxies to our 10:1m offline edit resolution.
3) To uprez, we would decompose the sequence with handles (so we only import what we actually need and not entire master clips)
4) Then batch import using a U2, bringing in all the clips in XDCam HD format.
This worked like a charm when running Avid 5 (or 5.5, not sure exactly which). We could plug in any U2 or U1 and since everything had a disc label, Avid knew what to do.
However, on this new show (running Avid 6), we began seeing a "PATH DELIMITER" error message when trying to batch import. We finally figured out that the source path wasn't coming in with the disc label (ex: "/Volumes/13HS0125A01/Clip") but instead the source path was pointing to the individual U2/U1 drive that originally ingested the proxies (ex: "/Volumes/XDCAM_U2_0103421/Clip".
We found that if we only tried to batch import the clips associated with the U2/U1 drive that was plugged in, it worked (although sometimes the drive listed in the source path was wrong, and a different drive was listed for the clips in the batch import menu). So, we are able to batch import so long as we have the U2/U1 drives assigned to the clips source path. Obviously, if one of these drives dies or isn't in our possession, this is a problem.
Furthermore, some discs came in with no source path listed or the had the disc label in the source path. Those clips we can't batch import at all. We have to assign them a tape name and batch capture with an XDCam deck.
So while we can batch import clips by plugging in the U2/U1 drive associated with clip's source path, or can batch capture any other clips, this is a giant pain in the neck, and Avid USED to not have any problems with this.
Has anyone else run into this problem? Is Avid aware of this?