-
adobe begins construction on the edit media deathstar
-
“Basicly, if you take any NLE and do a VPN session you’ll get the same. ”
Mm. Right.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
[David Mathis] “Tracks feel kind of awkward now and the fact you have to think in the “Tetris” type of mentality as I like to call it. :-)”
Having spent a large number of years using tracks, I’m quite happy to switch between edits on FCPX and PPro, I don’t buy into the redundancy of them just yet.
-
[Walter Soyka] “I think this is an big oversimplification of Anywhere that misses the entire collaboration architecture.”
Absolutely. I would very much like to hear the opinion of someone like Mark Raudonis, someone who is very familiar administrating collaborative workflows on a large scale. Anywhere is still a financial reach for me, but it’s looks promising.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
Yes, I know it is a BIG OVER simplification. But that was the whole point.
I get the colaboration and the other stuff.
But the main prinsiple is: you only see streams of video coming from the mainframe, and only send commands from you local machine to the mainframe.
That’s why you don’t need the best lines (connection) in the world.
And thats the whole point. You can do it on much more hardware, and use what you got, as long as it can decode incomming video fast enough.
Helge
-
[Walter Soyka] “I think this is an big oversimplification of Anywhere that misses the entire collaboration architecture.
“Perhaps I misunderstood, but I don’t think he was missing it per se; I just don’t think he was addressing that particular aspect of it.
-
[David Mathis] “Tracks feel kind of awkward now and the fact you have to think in the “Tetris” type of mentality as I like to call it. 🙂
“Mentality? It just depends on the complexity of the audio work you have to do. I’m guessing you don’t have to do a whole lot of layering.
-
[Chris Harlan] “[David Mathis] “Tracks feel kind of awkward now and the fact you have to think in the “Tetris” type of mentality as I like to call it. 🙂
”Mentality? It just depends on the complexity of the audio work you have to do. I’m guessing you don’t have to do a whole lot of layering.”
Was meant as a tongue and cheek comment and comical relief. That’s what I get for not using quotes. 🙂
Tracks are good but sometimes it feels like a game of Tetris, but not as complicated. At least that is how it feels for me sometimes.
-
But you seemed to be suggesting it was equivalent to using a Remote Desktop. The point is that is completely wrong. The software is local, and depending on circumstance, the gpu and effects processes are local. What is being virtualized is the video storage. They are operating a real time encode engine to deliver an optimized stream of all he assets to single downmuxed stream using their own codec to the client edit system. Also when you press pause they instantly insert the native media still frame – be it 5k epic or whatever.
It’s absolutely nothing like Remote Desktop or a VPN session. Those aren’t in any way accurate comparisons.
https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics
-
I’m not quite so sure about that..
From my understanding, there is nothing localy.
I.e. if you start on a timeline, prepared for U by someone else, and you sit at home with your laptop. On wifi, you will right from the start, be able to play a 5K RED epic raw file.
That is because you are only seeing a stream video in your canvas window. So you never ever have a file at you place, unless you tell the system to offload a bunch of proxies.
otherwise you’ll only get streaming of a “viewport” containing you master edit being done.
Helge
-
As explained in the whitepaper:
How it works
Source media files used by Adobe Anywhere are kept on a storage server connected to the cluster via a high-bandwidth OS-level file system mount. Local and remote users can upload source files to the storage server and can even work on the files while upload is in progress. Once the files finish uploading, they can be immediately used by other editors.
The core component in the Adobe Anywhere cluster is the Collaboration Hub. It contains the database of project information and metadata, manages user access, coordinates the other nodes in the cluster, and provides an API for integration into other Adobe Anywhere clusters.
The Adobe Mercury Streaming Engine nodes provide real-time, dynamic viewing streams of Adobe Premiere Pro and Prelude sequences with GPU-accelerated effects to your team members on their individual computers. The media is streamed from its native file formats on the storage server out to the users.
And when it’s time to export from Adobe Anywhere, the Mercury Streaming Engine can generate final files from sequences and other media.A minimum of three Mercury Streaming Engines is required for a small workgroup. But the system can easily be scaled to support larger groups or more complex use cases, simply by adding more Mercury Streaming Engines. The exact number required depends on use-case details such as the number of simultaneous users and media formats.
Adobe Anywhere does not require dedicated network cabling between individual editing workstations and the Anywhere cluster. This can greatly lower the costs associated with your network infrastructure and make it possible to create flexible workspaces for your creative team.
The viewing streams Adobe Anywhere delivers to individual team members are small and light enough to fit on shared, standard LAN/WAN networks. Adobe Anywhere does not edit, move, or delete the original media on the storage server. These functions are reserved for your media asset management system. And there are no proxy files in the Adobe Anywhere system. The server accesses the full resolution files and uses the power of the Mercury Streaming Engine to deliver exactly what is needed, given the bandwidth available. As a result, you get less complexity, lower workflow costs, and speedier production.Helge
Reply to this Discussion! Login or Sign Up