Activity › Forums › Creative Community Conversations › Avid slyly opening up at NAB for those that noticed
-
Avid slyly opening up at NAB for those that noticed
Scott Witthaus replied 12 years, 4 months ago 16 Members · 52 Replies
-
Oliver Peters
April 10, 2014 at 5:18 pmThe characterization of old film editors holding Avid back is quite far from the truth. Take a look at the make-up of the boards for the Customer Association. If anything these are skewed in favor of enterprise users.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Oliver Peters
April 10, 2014 at 5:27 pmYou can and have been able to run other NLEs for years on ISIS. Now Avid is opening up the API to do project sharing (with a license fee) to other manufacturers of shared storage.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Craig Seeman
April 10, 2014 at 5:32 pm[Oliver Peters] “You can and have been able to run other NLEs for years on ISIS.”
With the same feature set functionality on ISIS?
So FCPX would then allow simultaneous use of the same project as MC does?AFAIK one needs MC/Symphony to take full advantage of ISIS unless you’re saying that hasn’t been the case for years.
-
Oliver Peters
April 10, 2014 at 5:39 pmCurrently no. ISIS functions like any other shared storage. With the new APIs, it would depend on the way other NLEs implement it. Which would probably mean no. The point of opening the APIs is that other storage vendors can create a Unity/ISIS-style project sharing on non-Avid storage with MC clients connected to it. I realize some have already done their own solutions. This gives them an Avid-licensed and supported solution.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Mike Jeffs
April 10, 2014 at 6:25 pm“The characterization of old film editors holding Avid back is quite far from the truth. Take a look at the make-up of the boards for the Customer Association. If anything these are skewed in favor of enterprise users.”
I have to completely agree with this!
Now when it comes to enterprise which my facility is apart of a large enterprise that’s has spend hundreds of thousands in avid development. The notion that they don’t want to be on the bleeding edge is also far from the truth. I know this isn’t true with all large enterprise. It certainly is in our case, we have used just about everyone of media composers new features that have saved us tons of time and money from background transcoding to frame flex to many others. Sadly features that are a god send to some are completely irelavent to others. Such as media composers cloud editing they are showing at their booth we don’t need it but I’m sure others will love it.
There are lots of people and organizations who have sway( even more so with the ACA) that want features and updated to help us do our jobs better. But as Oliver said earlier stability and reliability are also majorly important because face it time is money and if you don’t want to have even more headaches if you don’t have to.
Obviously nothing is perfect and software is software and problems happen.
Lastly just to be clear that I’m not some koolaid drinking evangelist we use adobe and Fcp and now with BM announcment we will toy with the idea of resolve being used to edit some stuff. It’s all about the right tool for the right job.
Mike Jeffs
Video Coordinator
BYU-Idaho -
Scott Witthaus
April 10, 2014 at 7:45 pmInterestingly enough if Avid does shift more to be a profitable server and media management company, it might allow them to be a little more radical with the NLE, since it’s not the focus of the revenue stream.
As for the ACA, it seemed to be heavily management/engineering and light on the creatives. Would you say that is true Oliver?
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Andrew Kimery
April 10, 2014 at 8:50 pm[Craig Seeman] “With the same feature set functionality on ISIS?
So FCPX would then allow simultaneous use of the same project as MC does?”How could Avid give that functionality to FCP X when X and Avid take completely different approaches to what a project its? A project in Avid is just a folder that holds a collection of bins and sub-folders. A project to FCP is everything. You perform saves at the bin level in Avid where as you perform saves at the project level for X (and most other NLEs). Avid’s approach is a very simple solution to the problem.
-
Craig Seeman
April 10, 2014 at 9:03 pmJust being clear that just because other NLEs might work with ISIS, it’s not the same functionality as using MC/Symphony. Or at least Oliver clarified what I expected.
My point being there’s a good feature reason for ISIS users to to also us MC/Symphony.
-
Oliver Peters
April 10, 2014 at 9:07 pmRegarding the ACA councils, I would say yes and no. Many of the management type members there came from creative ranks or still function in a creative capacity.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Andrew Kimery
April 10, 2014 at 9:08 pm[Craig Seeman] “Just being clear that just because other NLEs might work with ISIS, it’s not the same functionality as using MC/Symphony. Or at least Oliver clarified what I expected.
My point being there’s a good feature reason for ISIS users to to also us MC/Symphony.”
Right. ISIS can be used a shared storage by anyone, but if you want the all cool things ISIS can do you need to be using it in conjunction with MC. This leads directly into my next question which is, w/o full ISIS functionality why would a non-Avid user choose ISIS over shared storage from EditShare or ProMAX?
Reply to this Discussion! Login or Sign Up