[Ed Torr]

So far N/G across the board, at least in our world here.
As best as I can tell Hard Links are not supported on ISIS
and Symlinks crashed the system

[Ed Torr]

HD-only.

[Ed Torr]

This would probably work. I think for this particular project your Hard Links suggestion (in the other post) is probably the fastest.

[Ed Torr]

Unfortunately we inherited the project structure. I suspect the AMAs are somewhere, in a different project the assists prepare everything in, where they are in a bin inside a folder of a folder of a folder, differently from episode to episode. So the challenge is actually to get all this up and running in less than a day without asking the assistants help because they are “too busy and stretched way too thin”. They’re called “AE” because once upon a time they assisted editors, but now they assist post producers, and APP is already being used by Apple.

[Ed Torr]

I’d been clued into the symlinks / hard link options thanks to a Avid Editors of Facebook response but I can’t test until Monday. Thanks for all the AB testing!

What happens if instead of removing the original you remove the newly-created hard link? I would expect Avid to not to be able to find the original.

[Ed Torr]

I wish I were overthinking this, Dave. From your lips to the God-of-Deliverables’ ears. This is a series going out texted and textless, with an array of texted elements tagged at tails on each textless reel. One reel might have 15 isolated texted elements, each one with it’s own slug or card (you’re right, not really a “slate”) with title, and time-codes referencing its place in the textless program. Info goes in the slugs, as a master menu before the slugs, on paper, and on labels. It’s a lot of numbers that change a lot, a lot of repetition, and everything must be accurate to the frame. I can argue they’re overdoing it, but rather than fight a losing battle with oblivious and faceless network execs, we built solutions. Each time there’s a change, we export data from the edit, apply it to a central data sheet which regenerate all the cards, and voila: unreasonable deliverables requirements are dutifully accommodated in a few automated seconds.

Like I said, this is something we’re already doing, and this is hardly the only context dynamic texted elements come into play. Stylized lower thirds naming reality contestant, complex stats in game shows, we do a lot of this stuff in a lot of different ways for a lot of different shows. Adobe automation has been the life saver throughout, and I’d love to expand on what we’re already doing.

[Ed Torr]

Actually dynamic content is precisely the goal, even if that results in a certain amount of unreliability.
Our particular interest in this is not screen grabbing a website, though that would be a outcome many would find valuable.

What we’re dealing right now involves an array of complex and stylized slates. The information in those slates is based on data coordinated between a number of different people, calculated externally, updated frequently. We don’t want to burden the AE artist with a bunch of changing text. She focuses on making things beautiful, and whenever she renders the data is ready, template, complete, no extra work.

Currently they way we handle it is to either push data through ExtendScript and update AE text fields, or auto update a series of Photoshop and/or Illustrator files that are referenced in the AE file. It already works great, creates a very efficient workflow.

In the same way we’re using ExtendScript and reference external Adobe-based files, we’d also like to reference local HTML files. That would allow us to take advantage of the distinctive qualities of html/css/js and give us a additional options and workflow fluency.

[Ed Torr]

Thanks Peter. Spot on. Of course, no sooner did I post than I found the very same.

[Ed Torr]

I’m on Premiere CC 2014 and do not see Gang options available in the pulldown menu. Did I miss something? Did the feature go somewhere else? Go away? Not available in CC?