John Heagy
Forum Replies Created
-
I could not get Find and Replace to recognize any variables.
I was able to do what I wanted by first using Bulk Edit to copy the entire Name into Tape and then apply the following regex to truncate down to 6 digits:
Search for: ^(……).*
Replace with: 1
-
Mark,
Are you using SDNA with CatDV or Interplay? I’m looking at Atempo and SDNA via CatDV.
John
-
FCPX with shared storage works well. What exactly one wants to share is where it gets tricky.
Can you describe what you want to share? Projects, footage, logging…
I could hook up 40 systems and have them all editing with FCPX off the same shared storage. The broad strokes are easy, the devil is in the details. Unfortunately Apple has chosen to take control of the details in FCPX unlike FCP7.
-
[Jeremy Garchow] “Where is the XML generated from?
“We have a custom app that links disparate media based on Reel ID and TC. We use this to generate an xml that links to media on the San.
[Jeremy Garchow] ” An empty FCP7 won’t relink to anything. An empty Event won’t relink to anything either.”
Sure it can, FCP7 never looks at media in the project to link to, it links directly via path. I can open an empty FCP7 project… import the xml I describe above, and Wa La! a 100% linked seq! The only item in the project is the seq created from the xml import.
[Jeremy Garchow] “I guess I am having trouble seeing how this doesn’t work for FCPX in an almost identical way to FCP7”
If by identical you mean now needing a San Location for every project, an Event filled with aliases, and separate projects for every seq… then yes, identical 😉 You’ll agree that not using Events to assist in some way makes it an obstacle to work around and not an asset in this case? Can we make it work?… Yes… but it’s no improvement.
[Jeremy Garchow] “I do see a problem if you need to “online” though as reconnecting to other media in FCPX is terribly non-existent. “
That’s the least of my concerns because we can use FCPX xmls like we do today with FCP7 and produce a linked project. Of course we first need to create a folder point FCPX to it as a San Location then create a Event then point the xml media to it and then.. Wa La! a linked project along with 100s of pointless alias files.
Yes, I know we are in the minority here, but FCP7 flourished across the entire gamut of production from pajama editors to 100 seat collaborative productions. Apple seemed to intentionally truncate the productions FCPX could serve – or even worse – thought it would just pick up where FCP7 left off which means they were simply out of touch with reality.
John
-
[Jeremy Garchow] “How do you handle this now in FCP7 and why can’t this method be adapted to FCPX?”
In FCP7 we import an xml and if the media is on the San it links up. FCP7 can link to an entire season of footage without having it all in the project.
The workaround in X is to use “one off” events solely to support a project and not use it to search and tag media. Apple’s intent with events is to present media to all projects where one can search and tag media just like a MAM. That works fine for contained workflows, but not for un-contained.
To put the difference in basic terms: FCP7 can link to any file as long as the storage containing the file is mounted. FCPX must have media redirected into an event before it can link or even see it
I never said we can’t work around it. I am saying that events do us no good if not used as intended, and are simply obstacles to linking media directly.
Apple decided to make FCPX both an editor and a MAM. That doesn’t work well for large data sets or collaborative workflows.
The issues above are really based on finishing from an offline. Here it’s easier to only take what is needed, creating a contained environment. My head spins trying to imagine using FCPX in a truly collaborative offline workflow using events as intended. Again, from an un-contained media point of view.
John
-
[Bret Williams] “So – projects and events separate. No problem here. It seems to me that we have a perfect beast “
You describe the same project and media usage we deal with. Our pool of media is not contained to episodes but seasons and beyond. The problem I see with Events is exposing FCPX to an entire season of media via events.
John
-
[Jeremy Garchow] “With X, relinking files has to be the exact same length as the original, at least for now.”
This really needs to change in order to support not only truncated video tape captured clips but LTO partial restores. I’d like to see metadata determine linking not just UUID/filename/path. This would be user selectable. One guess what I’d select 🙂
[Jeremy Garchow] “Also, reel numbers are currently strange in fcpx.”
Not strange, just myopic as is typical with Apple.
FCP7, and another apps that see “reel” in QT, see the TC reel ID referred to as TCSource in the QT API. It’s is literally the name of the timecode track in the QT movie.
Apple decided nobody needs to read this metadata present in every file captured from tape over the past decade and still created by many third party apps. Instead they adopted the newer extended metadata QT model, not sure what it’s official name is, and excluded TCSource. The best place to see this is in Arri ProRes files. The only confusing part is Arri puts the reel number in both the extended and TCSource metadata.
John
-
[Craig Seeman] “You can do that right now in Blackmagic and I believe AJA software. Independent of any NLE. “
I was talking about restoring the file from LTO not capturing from tape.
-
Keith,
I sent you a LinkedIn message.
-
[Keith Koby] “I don’t want tape capture married to an NLE in the future. I want it separate in a centralized location and stored as metadata and exportable to other tape capture mediums in the future. “
Yes that is inevitable. The big issue for us is data granularity. If you digitize a 2 hr program, but you just need a 4 sec shot, are you willing to restore the entire 150GB file? We do historical shows that have hundreds of tape sources most only containing a single shot for the conform. Tape is great for capturing only want you need.
LTO partial store is a feature that is talked about but rarely implemented. It’s really the holy grail of LTO but until it’s bread and butter LTO tech I’m not willing to chase that unicorn. I’m breaking up large files prior to archive. That makes linking tricky but we have some clever rabbits here.
John