I am running 8.9.4 on MAC for major projects, and 2018.12.6 on my PC laptop for short, home based gigs. So pretty much exactly the versions today's best practice (and you) suggest :-)
Regarding the technical side - I am not complaining about HW caused problems (they do occur, but relatively less often than in the past), in this field AVID made a major progress, as well as in overall SW stability of Media Composer.
My problem lays in the TRENDS Media Composer is likely to take based on what they did in 2019.6 release + the announced future plans.
I wouldn't compare MC and Computer Games. I am aware there is probably way more money in Game industry than in Media creation industry but if something fails in some game, it is not a big issue (neither your living nor your life depends on a comouter game... at least in most cases). Gaming culture is different, guys are eager to lay their hands on new releases asap and therefore much more willing to participate in beta testing etc. But for me, this is totally unacceptable for any software which is critical for my professional occupation. Regardless if it is the freshly released latest version or some well proven older version.
After all, if AVID is keen to get some pre-release and beta testers, they can easily get in touch with volunteers willing to participate and get them some raw distro and collect their comments. But sending something like 2019.6 into public is very bad idea.
Just my humble opinion... :-)
On AVID since ever.
im not a huge fan yet either but I think a combination of bug fixes, updates to make it more intuitive, and getting used to it will make me a fan. It's not THAT different once you get used to it.
I wish you were right... :-)
Honestly, when I first saw the news flash "re-imangined" I was expecting a total re-write of the interface (something like jumping from Avid 3 to Premiere 2018, a fresh "modern" look (not too loving Premiere GUI, but just an example). However the reality is not that much of a difference as most of the menus are just placed differently. Doesn't the Command Palette still has "Other" and "More" tabs? Which is kind of like a joke since the beginning... So not as "re-designed" as I expected/hoped. I'm sure once it becomes more stable and refined, I'll get used to it.
IMHO, I think a lot of the work was put in to support Bin containers. Having to try and organize a bunch of bins in the original UI could be problematic. Even having as few as 9 bins open could so you could see 10-12 clips could cover an entire monitor. Imagine the scenario where you've got separate bins for each day's dailies, graded shots, effects clips, etc. Trying to keep everything organized becomes a pretty big task.
I've now got my stuff for one project in a single bin container, organized by day. If I need to grade anything, it'll end up in a different bin container but with the same layout.
Dave S.
CAVEATS: since "retiring" I don't use MC every day, nor do I use any of the more esoteric functions. My use with the new 2019.x interface is limited to mostly import, basic cutting and F/X, filters and even more limited export.
I LIKE the new interface. To me (having used MC since the first or second iteration on the PC platform with a breif hiatus in favor of discreeet edit*) it is:
I don't agree that it looks / feels / functions "less professional" as, IMHO, it seems like I can be more productive - accomplish my editing goals in less time - which is what "professional" tools should be about FIRST AND FOREMOST with "looks" an item to be addressed when the former has been acheived to the point there is little more efficiency to squeeze out of the product. And in that regard, MC has a long way to go (which many former edit* users will tell you).
MC's biggest challenge - again IMHO - is in becoming more context aware in drag-drop and mode operations with increased "hiding" of complex operational details to allow reaching a final product faster AND / OR allowing for more simple "what if" trials and tests along the way without creating a clutter of elements in bins. As an example, in edit* changing the speed of a clip in the timeline was simply a right-click, select "motion effect" (or something like that) and enter a frame rate in the panel. Play back the result. If you were in insert or overwrite would determine if the the resulting speed change resulted in a ripple edit or overwite or a "same duration" (choice from motion effect panel I seem to recall) result.And mode switching was a quick hot-key affair, or you could change mode for a single edit with a modifier key (CTRL, I think) during the drag-drop / right-click.
Another improvement would be allowing "in- / from- bin element previews" with in-out-point setting without having to load the clip into the source viewer.
Allowing multiple bins to "open" at the same time in either separate "undocked" panes or as "tabs" in a single pane maintaing drag-drop copy / move operation for elements between bins.
But, I think I can see in the 2019.06 interface the beginnings of a "re-think" of the interface in the direction of increased intuitiveness, ease of use, and more concise / obvious organization. And that makes me happy. :^}
-----
wmc
Having now used the new software for the last few weeks I am much prefering it to the older style.
Just shows that often radical change can take a new mind set to adjust to it.
I love the features of docking and layout and now find it hard using the older versions we still have on older machines.
Would still love to have Constant or Linear audio mix switch on the transition tool rather than in audio settings as I use this a lot.
Would be great to be able to output multiple timelines in a queue and a refresh button for attached drives when using source browser.
2019.12 feels responsive and all in all its a good move forward I feel after my initial doubts.
Both my personal systems (Windows and OSX) are both now 2019.x. I prefer it over the previous versions. There are still changes and improvements that should be made by I agree that it is better. The side tab concept has grown on me.Tools windows need better integration. They still look, feel, and behave as if they are pre-2019.
DQS
www.mpenyc.com
Cunninghun:if AVID is keen to get some pre-release and beta testers, they can easily get in touch with volunteers willing to participate and get them some raw distro and collect their comments. But sending something like 2019.6 into public is very bad idea.
As this thread came back alive and I read some of the old posts in combination with the knowledge how 2019.12 functions today I would like to make a remark on the point Cunninghun made.
Avid, thanks to, or unfortunately because of, Apple's new OS Catelina you decided to release a beta 2020.x version into the public domain. Something I believe was never done before. What the outcome of that move will be we will see but while I'm no fan of Apple anymore, I applaud the move.
I believe the same should have been done with the 2019.6 through 11(or so) releases. By just labeling the same development path in the 2019.x version as beta you change the expectations of the customer base and take the argument away Cunninghun makes. If you don't like the term beta you can choose to intoduce a term like safe zone levels like Grass Valley does or something else.
While those that are in this business for years or decades might know how to manage their upgrade paths and procedures my trust levels are on average dropping with updates and new features. Yes we live in 2020 and software development business models change. I personally would appreciate if Avid stopped pretending it hasn't sometimes.
Jeroen van Eekeres
Technical director, Broadcast support engineer, Avid ACSR.
Always have a backup of your projects....Always!!!! Yes Always!!!!
A.V.I.D....... Another Version In Development
www.mediaoffline.com
Count me as a big fan of the new UI....much better, especially on smaller screens
Big fan too!!!!
Liking it also, especially on a smaller screens.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller