Lets see,
the ability to work with 4k material in HD projects, very interesting, esp. for documentary interviews. But will it work on existing hardware?
Background transcoding of longgop material into non longgop. Really nice
AMA management along the lines of the robust native media management. I want that
Master audio fader and cached audio waveforms. Well it took 12 years but finally there
Direct audio clip gain. Great, hoping it will work with the various hardware offered smoothly
AS-11 will be good if implemented by the broadcasters as universal archive system
Native support for XVAC through AMA... hmmm ok if implemented well, but I'm still not sold on AMA
But on the whole, color me very interested, now where did I put my credit card?
"Software bugs are impossible to detect by anybody except the end user"
No AAX support? You'd think that with Avid trying very hard to push AAX as the new standard that this would have made into MC7, it's certainly existed long enough...
for those who asked, other than " a few small tweaks" nothing done to optimize open i/o according to the live chat last night.
As it was suggested (and I know it doesn't make folks happy) the Open I/O issue is still a work in progress. Once we see the software with new drivers from the various manufacturers, we may be able to report of some improvement.
But as of now, there's nothing earth-shattering in this area of performance in MC v7.0.
-- Kevin
Robert Goodman :other than " a few small tweaks" nothing done to optimize open i/o
Well that's a mayor failure to meet my expectations to say the least.
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
Jeroen van Eekeres: Robert Goodman :other than " a few small tweaks" nothing done to optimize open i/o Well that's a mayor failure to meet my expectations to say the least.
quite the bummer.
the new stuff is largely welcome. Lets hope those few small tweaks, coupled with new 3rd party drivers will get us where we need to be with open i/o.
I am still very much waiting to hear whether or not the CC and trim sluggishness issues are also present with the Nitris DX and Mojo DX hardware. This question has been posed on various recent webinars but HAS NOT BEEN ANSWERED. Our engineering group is looking to upgrade, but if this is a bonified issue with Avid hardware as well, we would be shooting ourselves in the foot with the resulting major slowdowns to our momentum and workflow in a daily "race the clock" environment.
I would like someone from Engineering or Design to please weigh in on this specific issue. ASAP.
Larry Rubin
Senior Editor
The Pentagon Channel
www.pentagonchannel.mil
Larry
I have heard of this issue. Are you on local or shared storage? Please elaborate.
Thanks,
DQS
www.mpenyc.com
Dom:
We are running Interplay/ISIS 2.3 with 32 Newscutter 9.5.3.5 Nitris DX based edit suites. No local storage. We simply cannot afford a situation where our momentum and productive workflow has a monkey wrench thrown into the works with these sluggishness issues, if indeed they are present with 10.5.2 and 11.0.
Just moved from FCP after being a user for 10 years, been using MC for 3 months and now I see why MC is the way to go, can´t wait to see the new features in MC7.
Have you tried modifying your ISIS client to "high-res" mode?
Other times I have seen this was with a bad connection to the ISIS switch. Be careful, even with a 1Gb connection it does not guarantee trouble free editing. I recently had a client with high latency even though the computer and switch indicated 1Gb connection. Moving it to another port, removed the latency.
Let me clarify. We are not having any sluggishness issues now running NC 9.5.3.5. IMO, NC 9.5.3 and MC 5.5.3 are the most stable and reliable builds I've ever experienced in 20 years of using Avid software. I'm concerned that if we upgrade to NC 10 or NC 11 we will start experiencing this sluggishness and the extremely negative effect that could have on our workflow, if these issues are present using Nitris DX as well as in the 3rd party I/O boxes. I would have dozens of editors angrily howling at the moon if that's the case.
As a side note from reports on these boards, it appears that AJA - Kona card users are not having these sluggishness issues.
Hi,
Am I the only one who feels that this 7.0 announcement is lame? 7 new features, of which 2 are paid upgrades, and several are so small they're barely not worth mentioning (is clip gain really a Top 7 feature?).
Unfortunately, I'm one of those who is now finally leaving Avid after 15 years as a loyal editor. I need to work on a project that's the equivalent of editing 5 movies in the same project, all multi-cam footage, and I was holding out for some NAB announcement of improvements for Avid's multi-cam, which is right now unworkably bad for mixed-media footage with cameras that start and stop, and apparently will stay so.
We've been doing extreme stress-testing Premiere Pro for a couple of months, and have been unable to bring it to its knees. This is with 25,000 physical clips, half the clips on timelines and half of those with effects. It didn't even blink.
With the new announcements for Premiere Pro (multiple projects open, audio based multi-cam sync etc.), my last hold-outs have been taken care of. I'm already as fast or faster in Premiere Pro, the interface is snappier (this is actually the fastest editor I've ever used). The Trim mode is as good or better as well. Oh, and SpeedGrade integrated on the timeline.
It's been a long journey with Avid, and I've defended it to everyone, as my (almost) sole editor for 15 years. I had a 1 year stint on FCP, which I didn't like.
But the NAB announcement seals the deal for me personally.
It sounds really lame to leave Avid for Premiere Pro, but in practice, it's actually a step up for me. Everything that I need to do is better in Premiere Pro. The only thing I worried about was stability (and 800 MB project files), but since CS7 allows you to partition projects, that fear is gone.
Best,
Per
Will Frameflex work the same way with 1080 footage in a 720 project?
My workflow with AVCHD is either File Import or AMA link then put on a sequence and do mixdowns and keep the fragments before failure and stitch them back together. GIGANTIC waste of time. If they could fix this I would be very confident in upgrading our other 4 licenses and replacing the machines, but our userbase would not be able to cope with the AVCHD workfllow ISSUES.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller