Hi all,

Avid has released the following new editors today, November 3, 2009.  

*              Avid Media Composer v4.0.3 (Mac and PC) 

*              Avid NewsCutter v8.0.3 (PC)

These are full installers.

Customers with a valid Avid Support Contract can download/upgrade their editor(s) (v4.0.x/v8.0.x)  on the Download Center (login and password required) and any customers who purchased Avid Media Composer v4.0.x and Avid NewsCutter v8.0.x are entitled to download/upgrade from the avid.com Download Site. 

Note:  Any Academic system that is currently at v4.0.x/v8.0.x can be upgraded to v4.0.3/v8.0.3.

Download Locations:

The download files will available in two locations:

-    Avid Download Center for support contract holders (http://esd.avid.com/Login.aspx?ReturnUrl=%2fDefault.aspx ).  The new editors will be listed inside there respective folders.   Login and password required for access to this site.

-    avid.com Download Site. The editors will be located here:  http://www.avid.com/register/mcsoft_dl.asp

SW Licensing and Dongle Upgrade Codes:

The v4.0.3/v8.0.3 editors are an update to the existing v4.0.x/v8.0.x products and do not require a dongle or SW licensing update.

Fixes and ReadMe Files

Avid Media Composer v4.0.3 and Avid NewsCutter v8.0.3 are update releases to the existing v4.0.x/v8.0.x editors.   There are many fixes to this release so customers are encouraged to read the ReadMe document provided with the download and also located on the Knowledge Base prior to upgrading. 

quicktime 7.6.4 is supported

but if you install that, in sorenson 5.1 you can not load the Quictime presets...

I stick with 7.6.2

You found a problem before even the new version is well released.

Maybe if you try to reinstall Sorenson?

Usually I wait a bit before catching up with upgrades.
Today is an exception.

I downloaded and installed 4.0.3!

I notice that the "Read Me" is for MC 4.0 and not for MC 4.0.3
I have informed Marianna.

Regards,
Douglas

From the Readme

Fixed in v4.0.3
The following have been fixed:
➤ Bug Number: UDevC00128226. The v190.38 NVIDIA driver has been qualified. This fixes
the “Unable to install fonts” error that occurred on WinXP SP3 systems.
➤ Bug Number: UDevC0090818. You might have received an “Exception: FILE_Other” error
when exporting AAF to a network shared drive. This has been fixed.
➤ Bug Number: UDevC00128607. Playing back the Timeline when in MultiCamera mode
with the DV device attach resulted in an “Exception: ADM_DIO” error. This has been fixed.
➤ Bug Number: UDevC00129441. Using Audio Punch-in to create filler at the beginning of
the timeline would sometimes fail with an error. This has been fixed. This has been fixed.
➤ Bug Number: UDevC00130505. Performing a DV capture with the Panasonic AJ-SD755
deck might have resulted in “ADVAudioDev: TransferSample” errors. This has been fixed.
➤ Bug Number: UDevC00131178, UDevC00131974. XDCAM batch imports occasionally
failed to accept the correct disk. This has been fixed.
➤ Bug Number: UDevC00130028. Some AAF sequences did not successfully import into the
editing application. This has been fixed.
➤ Bug Number: UDevC00130757. The Timeline would freeze for approximately 5 to 10
seconds when performing an audio scrub. This has been fixed.
➤ Bug Number: UDevC00130658. After canceling a sequence export and returning to the
Timeline or Source/Record monitors, you might have received a “Core_unable_to_do” error.
This has been fixed.
Fixed in v4.0.2
5
➤ Bug Number: UDevC00129841. When performing a checkin from the editing application
to Interplay, reference assets were not always checked in. This has been fixed.
➤ Bug Number: UDevC00105760. Media appeared as offline when sending to playback.
This occurred when a P2 clip was placed in the Timeline after an in-progress clip. This has
been fixed.
➤ Bug Number: UDevC00128958. When working in Segment mode, when moving a
long GOP format clip to a new location, there was a delay in updating the sequence. This has
been fixed.
➤ Bug Number: UDevC00129064. Media received during a transfer while the Audio Punch
In tool was recording to the Timeline, appeared offline in the Transfer Bin. This has been
fixed.
➤ Bug Number: UDevC00129581. Channel rotations might have occurred when performing
HD SDI audio capture on the Symphony Nitris. This has been fixed.
➤ Bug Number: UDevC00129784. If you made a change to a User setting and then closed the
project, the User setting change would not stick. This has been fixed.
➤ Bug Number: UDevC00129809. The clip gain in the Audio Mixer tool displayed incorrect
gain values when Command 8 was attached. This has been fixed.

the full readme is here

http://cdn.pinnaclesys.com/SupportFiles/attach/README_AvidMediaComposer_v4.0.3_Nov_2_09.pdf

sverkalo:

You found a problem before even the new version is well released.

Maybe if you try to reinstall Sorenson?

yes, tried that... default presets of the Sorenson don't even import anymore with 7.6.4

GO back το 7.6.2 as they say.

yes, did that. Everything fine

.. as they say... who are 'they'?

Those who are in 4.0.3.

Don't worry. They are earthed.

This is my first time updating AVID and am wondering if I need to deactivate the software before I uninstall? Or can I just uninstall everything (Currently 4.02) and then install the latest build?

You must deactivate the software before installing the newer version.

Just to re-itterate the Read Me in the download is for an earlier version of Avid 4.  Bit of a clanger really - as it suggests older video drivers etc.

D

I have to keep using the 182 driver for 4.0.3 as I found that the newer driver completely destroyed the OpenGL shader 4 for one of my apps (Vue 8 Infinite). Admittedly, there are many settings that I could have tweaked in the display driver to (perhaps) sort this out but for now, the driver shipping with 4.0.2 seems to work just fine. Mind you, this sort of thing is entirely dependent on the particular card you're using, etc.

Anyone else have any problems with the driver shipping with 4.0.3?

caused open GL shader related crash in AE8

BarkinMadd:

I have to keep using the 182 driver for 4.0.3 as I found that the newer driver completely destroyed the OpenGL shader 4 for one of my apps (Vue 8 Infinite). Admittedly, there are many settings that I could have tweaked in the display driver to (perhaps) sort this out but for now, the driver shipping with 4.0.2 seems to work just fine. Mind you, this sort of thing is entirely dependent on the particular card you're using, etc.

Anyone else have any problems with the driver shipping with 4.0.3?

I actually did a separate post yesterday, but re-reading this think maybe this was my issue.  Even though the Avid indicated that I need to upgrade the Nvidia driver to 190.xxx I think maybe I should have stuck with 182.xxx.  I had massive lag in the CC and my wacom went sluggish as well.

Already wasted 3 hours yesterday and had to roll back to 4.0.2.  No more time for testing.

Ra-ey