Alex, that surprises me but still, MC6 is likely a heavier application than MC5 for your system to handle. It may just be the last straw for it. Would be curious to see if more RAM would help.

That seems odd considering I spent the last year editing DNxHD 175x media with no trouble at 4GB on 32 bit. Since I installed MC6 in October I got a huge increase in the AMA h.264 porformance and switched over to it entirely. Just in the past day the over run issue has come up. And that's since having upped my RAM to the max (8GB) a month ago. I had great performance on my machine and something has caused a drag. 

Alex Walker:

That seems odd considering I spent the last year editing DNxHD 175x media with no trouble at 4GB on 32 bit. Since I installed MC6 in October I got a huge increase in the AMA h.264 porformance and switched over to it entirely. Just in the past day the over run issue has come up. And that's since having upped my RAM to the max (8GB) a month ago. I had great performance on my machine and something has caused a drag. 

 

 

I personally think its jsut a bug, they know about it and hopefully arewroking on it. I too was running fine on a core 2duo machine with 8 gigs of ram for a while in 5.5 and never had an issue with 175x.. 

 

 i am now on a i7 w/ 16gb ram and get this message all the time w/ dnxhd 36. lol  so im thinking its a bug for sure. 

Robert Goodman :

I personally think its jsut a bug, they know about it and hopefully arewroking on it. I too was running fine on a core 2duo machine with 8 gigs of ram for a while in 5.5 and never had an issue with 175x.. 

i am now on a i7 w/ 16gb ram and get this message all the time w/ dnxhd 36. lol  so im thinking its a bug for sure. 

Exactly my experience - no problems what so ever with DNx36 and 8 tracks of audio on v5.5. Now unusable with this error and v6.0. Has to be a bug.

Alright so I ran YASU on my system before getting to work this morning. I then trashed all the pmr/mdb files on my different drives. I've started editing at half resolution with only one audio track enabled at a time. Adujsting the buffer to past 8000 and overriding the internal audio sync seems to have killed the issue 90% of the way for me. I still get it occasionally but I can edit no prob in the mean time. 

I'm also having this issue when I run as software only. Log attached.

I've tried the suggested increase on the audio buffer and there is no obvious change.

Also having this problem...

Hello! Actually since I updated my MC from 3.1.2 to 6.0 nothing more works fine.

- Launching the software I encounter 21 times this error: " Error # while verifying your authorization ". After pressing enter for 21 times the software launch normally.

- If I try to link to AMA any AVCHD file it's not even possible to play it, the  ADM_COREAUDIO_UNDERRUN message appears after just a couple of seconds. I have tried to do everything was suggested in this forum, but the problem is that even with imported HDV files the message comes out too often and when it happens there is no way to keep working, I must close the Avid and launch it again. I never had any problem working for years with MC 3.1.2, no problem with HDV capture, no problem with RED files no problems at all. Now even the simple playback operation has become slow: I press space and the clip starts with a considerable delay.

I thought to get to work faster and after spending money and believing to get a big help, I just encounter problems over problems.The problem is that the ones who use Avid MC are normally professionists who work with it. It's a serious problem then. I hope Avid solves this problem soon because I already regret that I bought it.

My Mac configuration appears in the chart as a certificate configuration and the only non available function should have been the HD capturing.

I'm really disappointed.

Revert back to 5.5. and wait for the next Update.

Regarding your rant I'm absolutely with you: Even on absolutely unsupportet and underpowered machines I've been running several updates from XPro to MC over the years, sometimes with minor glitches and hickups but never with such a total failure. I'm disappointed, too. I can not believe that none of the beta-testers (if any) ran into this- and other severe issues we see with Version 6.0. As stated somewhere else I think this release is premature and may have been pushed out on the market so early in order not to be late in the dissapointed-FCP-user-fishtank, especially against Adobe.

So let's wait and see how fast AVIDs nerdies are. I see lot's of pencils flipping through fingers.

My 2c.

Thanks, the problem is that I bought directly the 6.0 version repalcing the 3.1.2 and I don't have any possibility to get the 5.5.

I am also encountering those problems, will you be so kind to check if it happens to you too, pls?

After defining the keyboard from the command palette (more or less like the Xpress default), the following commands from the keyboard don't work:

- Trim Right 10 Frames

- Segment Mode (Lift Overwrite)

- Segment Mode (Extract Splice in)

- Quick Transition

- Trim Mode

- Effect mode

- Clipboard Monitor

 

I can't believe that I bought a product to become a beta tester!

 

Lorenzo Barichella:

Thanks, the problem is that I bought directly the 6.0 version repalcing the 3.1.2 and I don't have any possibility to get the 5.5.

So you have a software license with no dongle, right? As my version ist registered with a dongle I can revert back to any version prior V6, but maybe someone can chime in here if and how it is possible to do that without dongle?

I am also encountering those problems, will you be so kind to check if it happens to you too, pls?

After defining the keyboard from the command palette (more or less like the Xpress default), the following commands from the keyboard don't work:

 

- Trim Right 10 Frames

- Segment Mode (Lift Overwrite)

- Segment Mode (Extract Splice in)

- Quick Transition

- Trim Mode

- Effect mode

- Clipboard Monitor

Yes - that's because you - like me - have an international keyboard.

See this post: http://community.avid.com/forums/t/102853.aspx

It's a mess and and for me a prove that this version has not been tested by international (non-english-speaking) beta-tester, therefore ...

I can't believe that I bought a product to become a beta tester!

... welcome to the club.

 

Thanks again.

Well actually I have the Avid dongle that I bought within my MC 3.0 System and it was all the time connected to the Mac. As you told me that, I just tried to unplug the dongle and the software can actually launch even without it.

About the keyboard, well I am using a U.S. keyboard, it's one of those "Labelle Communications" with the coloured keys made for Xpress pro. So I guess the problem is not even that.

it is sure that we are the beta testers, and If I were one of theose Final Cut users that should migrate to Avid, I would rather keep my own working software and say a last good bye to Avid.

I bought it to have a simple life and surprise surprise, i can't even use it.

Thanks a lot again for your advice.

 

If you used software activation, then no, you cannot go back to a previous version of the software.  Each paid version (x.0 or x.5) has it's own activation codes.

When you purchased, you could have opted to update your dongle instead.  That may still be an option but you'd have to check with Marianna after the holiday weekend.  But you can only have one or the other, so you'd have to decide which was better for your workflow.

 

 

The problem is clear, the were in a hurry to introduce the world the new product... the 64bit revolution!!! But it is also clear that Avid 6.0.0 is not really compatible with my Mac though it is an "Avid certified workstation".

There is probably no way to fix those problems until the next release. I use Avid for working, I lost a workday (today) and I need to give a video before saturday, I don't have time to hope that maybe in the next release they will fix the problems they didn't check before selling the upgrade.

They just play with us users, and we pay for that!!!  They use us for testing their products, and we pay for that!!! If we need some support, we must pay for that!!! And that's unbelievable from a so big firm with a so gorgeous name.

If I can't install any previous working version meanwhile they fix the compatibility problems, tomorrow I will remove the whole software from the Mac and use the right of withdrawal to get my money back. It's a shame! Everybody should do that, so they will understand the damage they gicve us.

Fortunately I got the update through the serial number and didn't update my old dongle, so that for working I can still use my old MC 3.1.2 software.

I'm so nervous that I think that I will probably learn using more Final Cut and quit Avid forever, at least I am sure it works.

Lorenzo Barichella:

About the keyboard, well I am using a U.S. keyboard, it's one of those "Labelle Communications" with the coloured keys made for Xpress pro. So I guess the problem is not even that.

I think it's more the OSX language setting (in your case italian I suppose) that is not adressed by AVIDs keyboard-settings. You may change your OSX system-settings to US to get the functions (Lift, Slip-Right, Add Transition,...) to its proper Key on your keyboard again.

it is sure that we are the beta testers, and If I were one of theose Final Cut users that should migrate to Avid, I would rather keep my own working software and say a last good bye to Avid.

The paradox is, that  - IMHO - AVID was and still is the by far best editing tool on the market. Maybe not from a technical standpoint, but definitely in terms of 'basic, intuitive and fast editing'.