-
Final Cut Pro X + NEXIS | PRO
-
[Oliver Peters] “FWIW (and an edit to my previous post), it is also possible to have multiple editors open the SAME Premiere project on a SAN. However, until Adobe gets Adobe Anywhere worked out, this approach is very dangerous. “
Maybe you have more info than I do Oliver, but from video’s I’ve seen about Adobe Anywhere I’m left underwhelmed. To me it’s not really project sharing but an attempt to help automate the process of keeping multiple projects in sync. For example, if Tom, Dick and Harry are sharing a project in Avid they are literally sharing a project. They will be working out of bins (which can only be modified by one user at a time, but can be read by everyone) but there is always just one project.
If Tom, Dick and Harry are working with Adobe Anywhere (and again, please correct me if I’m wrong) they each have their own version of the project and in order to kept the projects in sync they have to push a button to push their changes to the other users and the other users have to agree to accept those changes. If there are syncing conflicts then the user has the option to keep their changes, keep the other person’s changes, or keep both (not sure what “keep both” does, makes two sequences?).
AFAIK this doesn’t address one of the major issues of working in a multi-editor environment which is ending up with work and media spread across multiple projects. If Tom goes home, but forgets to share his changes, then only Tom’s version of the project contains Tom’s work. Or Dick and Harry accidentally work in the same sequence but they don’t know it until it’s time to share and Premiere tells them there is a sync conflict that has to be resolved.
I’ve always felt that Avid’s approach of saving bins, as opposed to projects, was deceptively simple and effective. I’ve worked a lot with PPro, FCP Legend and Avid in multi-editor environments and in my experience it’s always been less work using Avid from an organizational and logistical perspective. I really want to like Adobe Anywhere, but every time I see a video for it I’m just like “meh”.
-
Instead of Adobe Anywhere I would be looking at Adobe “Team Projects”(currenty in beta) as a comparison to AVID shared projects. It works between PrPro, Ae & Prelude.
More info here:
https://helpx.adobe.com/premiere-pro/how-to/team-project.html~Myron
-
[Myron Vazquez] “Instead of Adobe Anywhere I would be looking at Adobe “Team Projects”(currenty in beta)”
Aren’t Team Projects the same as Anywhere, just without the server component? I believe you still have to have the projects in the Adobe Cloud.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Andrew Kimery] “Maybe you have more info than I do Oliver, but from video’s I’ve seen about Adobe Anywhere I’m left underwhelmed. ……
If Tom, Dick and Harry are working with Adobe Anywhere……
…..push a button to push their changes to the other users and the other users have to agree to accept those changes. ….”I’m not thrilled about it either. Basically it’s a check-in/check-out system with reconciliation. The project is in the cloud. Multiple users can access the same file. When you check back in you have the option of accepting, declining or keeping other changes.
I don’t believe the projects are actually local, as in being on that editor’s hard drive. To my knowledge, the projects are still only in the cloud. Also, I believe all editors have to be part of the same team or enterprise account. It can’t be used by editors with individual accounts. For example, you can’t add a freelancer and have them work from home on their own account. However, if that freelancer is a member of your team or enterprise group, then they can.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Andrew Kimery] “I’ve always felt that Avid’s approach of saving bins, as opposed to projects, was deceptively simple and effective.”
This is why I have thought from the beginning that FCPX’s event structure could be a way for Apple to deploy a similar sharing routine. Unfortunately their sharing track record hasn’t been good. When FC Server was in existence, it could be used in much the same way as Adobe’s sharing. However, Apple pulled the plug.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Bill Davis] “X may crack it in a different way with it’s “metadata about stored ranges” capabilities.”
I’m not at all sure I understand how you think “metadata about stored ranges” relates to the question of shared storage.
Could you elaborate?
Simon Ubsdell
tokyo productions
hawaiki -
[Oliver Peters] “Also, I believe all editors have to be part of the same team or enterprise account.”
Yes, this is correct.
I see Teams (and Anywhere) as a way of up-selling Team/Enterprise accounts from Adobe’s standpoint. I’m far from convinced that they are prioritising the end user.
Simon Ubsdell
tokyo productions
hawaiki -
[Simon Ubsdell] “I see Teams (and Anywhere) as a way of up-selling Team/Enterprise accounts from Adobe’s standpoint”
I agree. Or at least to provide some added value for these customers, considering they are already paying more per seat (at least for Teams) than the individual users.
Speaking of the CC in general, ironically enterprise customers aren’t required to link to the cloud at all for installation. I presume a sys admin has to create the installer from the cloud, but after that, individual stations can be locally installed without any CC log-in from that installer package.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Aren’t Team Projects the same as Anywhere, just without the server component? I believe you still have to have the projects in the Adobe Cloud.”
Yes. We’ve looked into it and that’s how it works. No internet, no worky.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Charlie Austin] “No internet, no worky.”
And that of course is a major stumbling block if you work in a sector where clients require your edit machines to be never connected to the internet. Which I am sure you have experienced!
Simon Ubsdell
tokyo productions
hawaiki
Reply to this Discussion! Login or Sign Up