Activity › Forums › Creative Community Conversations › OT: Adobe CC 2018
-
Jeremy Garchow
October 20, 2017 at 1:43 amJust got an email that frame.io panels aren’t working in CC2018.
Frame seems to be working on a fix targeting the next few days.
-
Scott Witthaus
October 20, 2017 at 10:58 am[Oliver Peters] “Let’s see if Apple steps up to the plate with something that enables better collaborative workflows”
I would rather see Apple integrate Motion/Logic into the workflow like Adobe is doing with PS and AE. Again, collaborative workflow is probably not needed for most visual storytellers.
Finished a Pr job recently and I really enjoyed bouncing to AE for simple little things when needed. Of course, the next day one of the linked files from AE would not show up in Pr….oh well.
Scott Witthaus
Owner, 1708 Inc./Editorial
Managing Partner, Low Country Creative LLC
Professor, VCU Brandcenter -
Bill Davis
October 20, 2017 at 7:41 pm[Oliver Peters] “Let’s see if Apple steps up to the plate with something that enables better collaborative workflows.”
There are rumors floating that Arctic Whiteness (The FCP X Library Manager, folk) have been working with Focus 1st AE Mike Matzdorff and Lumaforge on some type of “temporary collaborative library virtualizations” that help in the shared workflow arena.
That would be consistent with the Apple process of letting outside entities build out functions that only a sub-set of their users are likely to need.
Sam and Mike are doing a session at the FCP X Creative Summit next week about it.
Beyond that – I know nothing.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
Oliver Peters
October 20, 2017 at 8:50 pm[Bill Davis] “Sam and Mike are doing a session at the FCP X Creative Summit next week about it.”
I’d be curious to see what they come up with. Although it’s a small subset of users, the function does apply to any place with 2 or more edit stations. NAS storage is so darn cheap these days that shared storage is no longer a rarified situation.
– Oliver
Oliver Peters – oliverpeters.com
-
Andrew Kimery
October 20, 2017 at 11:03 pm[Oliver Peters] “NAS storage is so darn cheap these days that shared storage is no longer a rarified situation.”
And everything else (computer, NLE, etc.,) is so darn cheap that having multiple people working on the same project(s) is also no longer a rarified situation. Death to Sneaker Net!
[Bill Davis] “There are rumors floating that Arctic Whiteness (The FCP X Library Manager, folk) have been working with Focus 1st AE Mike Matzdorff and Lumaforge on some type of “temporary collaborative library virtualizations” that help in the shared workflow arena.”
Is this what you are referring to, Bill?
-
Jason Watson
October 21, 2017 at 11:20 am[Eric Santiago] “Does this mean I don’t have to make layers within AI?”
You can basically set it up in Illustrator however you want. One layer, lots of layers; it’s really flexible. It even retains whatever naming you have within a layer, with options for centering, etc.
I also like the little “switch to Illustrator” or “switch to After Effects” button as well. 🙂
-
Jeremy Garchow
October 21, 2017 at 4:30 pm[Jason Watson] “And while this isn’t related to the 2018 update, battleaxe.co just released an amazing tool called Overlord which creates a two-way connection between After Effects and Illustrator. Extremely useful for working with Illustrator layers (rather than files) inside of Ae. I bought it immediately, and although I’ve only scratched the surface, it’s wonderful. “
I cannot thank you enough for posting this. Editable text from Ai to Ae without a bunch of hoopla? Amazing.
-
Bill Davis
October 21, 2017 at 7:46 pm[Andrew Kimery] “Is this what you are referring to, Bill?”
Yep.
The interesting thing is that “ephemeral copy” approach.
At least as I (rudimentarily) understand it.
The person wanting access to the Library can open, access, and even copy elements from a non-mounted outside library for use in their discrete operations – but when the access is terminated, the virtualized copy is eliminated. So the issue of constantly making new copies of existing libraries all in different states of completion – is avoided..
It’s not the holy grail of true collaboration, obviously. But it appears to solve quite a few specific collaborative issues like the need for outside vendors to constantly update the state of an evolving project for their contributions – without multi-version conflicts arising.
Theoretically, the collaborator could do a “last ephemeral update” just prior to their delivery deadline – make any needed adjustments – and then the host editor could substitute that copy of the Event or Library for their “working copy” – allowing a slightly different form of round-tripping.
This is theoretical musing – I’ll see the actual product in Cupertino next week. Until then, I’m mostly just guessing.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
John Pale
October 22, 2017 at 3:37 amIf its like you describe, that is not Avid like at all. All Avid users normally have read/write access to the PROJECT regardless of who opened it first. When it comes to BINS (and sequences contained within them), the one who had it open first has full write access, with others having read only. The way Adobe is doing this really limits collaboration on the same project. Multiple editors will still have to maintain their own project rather than work simultaneously within the same one.
-
Oliver Peters
October 22, 2017 at 12:17 pm[John Pale] “All Avid users normally have read/write access to the PROJECT regardless of who opened it first. When it comes to BINS (and sequences contained within them), the one who had it open first has full write access, with others having read only.”
Think of it based on “data units” (my term). In Avid the Bin is the basic data unit, whereas in Premiere, the Project is the basic data unit. In Avid read/write access/locking happens at the bin level while in Premiere it happens at the project level.
In Avid if you work on a film with several “reels” or acts, each might be in its own bin and multiple editors could work in the same project simultaneously, but in different bins. You can access any content from another bin (opened by another editor) as read-only when needed. In Premiere, each “reel” or act might be a separate project and different editors work in their own project. But then if you need to access material from another project, you can open it in a read-only mode.
– Oliver
Oliver Peters – oliverpeters.com
Reply to this Discussion! Login or Sign Up