Hello,

In the version matrix the listed Nvidia drivers only link for windows. It would be very helpful to link the proper nvidia driver for Mac as well. Which one should we use for 10.13.5 / 2018.7.1?

Thanks

Bruce

When reimporting relinked sequence in Media Composer, an error pops-up :

Source aaf and relinked aaf in attached zip file.

(Please visit the site to view this media)

Hi everyone. There's a new AvidBlog: "How Avid Media Composer Uses a Computer".

Here: http://www.avidblogs.com/how-avid-media-composer-uses-a-computer/

It is part of a group effort with Avid's Chief Architect Shailendra Mathur plus the awesome engineers on the architecture team Stephen Crocker, Markus Weber, Sharon Fincher and many others. 

Rooted in the Avid Intelligent Compute Architecture that launched in 2008 with MC3.0, this introductory-level blog covers the basics of how today's versions of Composer (up to MC 8.9.2) physically distribute the workloads of editing and playback throughout a computer.

Please post your questions below. When possible, Avid employees will step up and help answer your questions directly.

Thanks!!!

Chris Bove'

While it's relatively slow this month, I'm trying to refresh the OS and software on my 3 Mac Avid network, connected to Nexis Pro storage. All Macs (trash can, iMac and laptop) are on approved Mac hardware list.

After a fresh install of MacOS 10.13.6 and Media Composer 2018.8, Avid Background Services is not running consistently between different user profiles. I create Administrator (with admin rights) and Editor (standard, no admin rights) profiles on all machines, and make my freelancers use the Editor account. I am able to successfully start Avid Background Services on the Administrator account (green icon), it will not start on the Editor acocunt (red icon). I've installed this configuration on 2 of my 3 machines now (laptop and iMac) and this issue presents itself on both machines. 

I've tried creating a new editor profile with admin rights, and this newly created profile still does not start Background Services. Only logging into the original Administrator profile allows for successful background transcodes, renders, etc.

I'm upgrading from v8.5, where Background Services was also unreliable. I was hoping Background Services would be more stable with this release. When it works, I find it very useful for our workflows, especially transcoding media to our Nexis in the background, allowing us to organize our bins and even work on other projects while it transcodes media in the background. I don't see that many posts about it in the forums, does it generally work well for everyone else? Anyone have any tricks up their sleeves to get Background Services turn green when it goes red? Or does no one bother because it doesn't work for them? Asking for a friend... :)

Inky

win10, mc 2018.8, 1080ti, 128gb ram, 7820x cpu (but also own a 7940x)

I always get 100% cpu usage across 14cores with ama export and transcoding (love that!)

Rendering on the other hand doesnt seem to use the cpu as well..  I am still trying to dial in some settings and it does look like im getting better performance but there still seems to be room for improvement.

When rendering and I have the console open I keep seeing

DIDWriter::DoSDKHWEncodeForCapture - SDK HW encode disabled

What does that mean?  And also

Is there more gpu acelleration with 1080 project than uhd? Because I'm seeing a max render dimension in the console when i start MC

OpenGL implementation found:

vendor = NVIDIA Corporation

renderer = GeForce GTX 1080 Ti/PCIe/SSE2

version = 4.6.0 NVIDIA 390.77

This OpenGL implementation supports hardware texture render

maximum render dimensions: = 1920 x 1080 at 8 bits per pixel channel

Still curious about my questions above.  Ive been doing a little testing.  I don't think uhd gets the same gpu acceleration that 1080 does.  There are also major fluctuations on performance depending on whats being rendered, I wish there was a way to know what was being rendered so I can plan on what fx I use.   Im also no longer using same as source on render settings, switched setting to 8bit, using standard vs advanced quality rendering.  I disabled hyperthreading since it clearly doesnt help rendering. That also lets me overclock higher to 4.7ghz (noctua air cooled) on a 8 core 7820x.  Any other suggestions?  I am curious to know what a qualified quadro would do for my rendering performance.  Im using 10gbe storage which gets 800mb/s r/w with blackmagic speedtest.

Apparently the issue is with the Fusion Connect plugin and not, strictly speaking, Media Composer.

I have been told that the folks over at BMD have been notified. I have also escalated this to the BMD support team.

I'm posting this here in the hopes that a heads-up may be helpful to those who are using Fusion Connect with 2018.5 or earlier and are thinking about upgrading to 2018.7 (you might want to hold off until we see an update to the Fusion Connect plugin from BMD).

Cheers

Israel’s largest post house, Opus uses Avid NEXIS to power Reality TV and feature film applications like 4K color grading and film restoration.

READ THE STORY

A friend of mine has been invited to show a video work in Buenos Aires. They want to add subtitles in Spanish and have asked her for a "script" and a timing list.  The format they have asked for is this: 1:00:00:31,000 --> 00:00:34,000.  We cannot figure out what the comma and three zeros at the end mean.  Can anyone help decipheer this?

Thanks,

Marluc

I installed the Baselight for Avid trial yesterday.   I played around with the plug-in for a couple of hours and everything seemed to work fine.

This morning, I booted up my computer and got the dreaded "Unable to Start..." message.  Windows 7 attempted to "fix" the startup problem.  After a long wait it was unable to repair the problem and shut down my system.   I held my breath, pushed the start button again...and windows started.   But when I went into MC, the Baselight plug-in was gone.  It is also gone in my system's program files, so Windows must have done a system restore to the point before I installed the Baselight plug-in.

I want to try out Baselight, but the Unable to Start message makes me nervous.   According to Baselight's specs, it should run on Win 7.   I'm running MC 2018.4.     Before I try to re-installed, I'm wondering if anyone else experienced this problem?

Hi

Can anybody explain, why some of my MXF files show up with a linked symbol and MSP_MXF Plug-In and others as regular MXF files?

Draged database from Avid MediaFiles/MXF folder into MC.

:)

Peter Brandt

Just went to download 2018.8 and noticed that all versions from 8.10 through 2018.7 are missing.  Used two different browsers to see if that was the issue.  Nope.

Have I missed something here?

Jef

I am looking to possibly purchase a new computer for running AVID.  The one I have has been great, but it's starting to show its age (especially with 4K projects).  Here's what I currently have:

Mac Pro (Late 2013)

3 GHz 8-Core Intel Xeon E5

64 GB 1866 MHz DDR3

AMD FirePro D700 6144 MB

I use AJA IO4K to monitor video and audio (and sometimes go to tape)

and Promise Pegasus Thunderbolt 2 drives.

I want to stay with MAC.  Would I notice an improvement is I purchase a imac pro like this:

Apple 27" iMac Pro with Retina 5K Display (Late 2017)

• 3.2 GHz Intel Xeon W 8-Core
• 32GB of DDR4 RAM | 1TB SSD
• AMD Radeon Pro Vega 64 (16GB HBM2)
• 27" 5120 x 2880 IPS Retina 5K Display
• UHS-II SDXC Card Reader
• Thunderbolt 3 | USB 3.0

I find myself always bringing up the mixer for added clips and bringing up pull down menu to give it the same gain as the surrounding clips.

It would be cool if I could map "Set level on track - in/out" on keyboard without having to bring up the mixer and using mouse for pulldown menu.

Thanks

Don't get me wrong, I love Avid media management.  This suggestion is for something that's been around for decades.

I feel that rather than masterclips and renders going into folder 1.

I think it would help media managment when moving drives/systems to put master clips in 1.

and renders in a 1R or whatever you want to call it.

There are times that one has to move media around, and seeing this on the finder/explorer level would make it quicker and simpler to move things around.  Time is always an issue in post, and sometimes I need to copy media for people and not precomputes.  And yes, I am familiar with many work arounds for this, just think it makes sense to differenciate what goes into where.

Love avid though!! (:

Media Composer 2018.8 released 8/13/18

Avid is pleased to announce the release of Media Composer 2018.8.   

Location: This release is available from Avid Master Accounts, Application Manager, and the Avid Download Center (login and password required).  Note:  The Download Center goes live at 12:00 pm ET and the remaining components will follow shortly after.

Operating System Updates: The following lists the qualified Operating Systems. Depending upon your hardware the qualified Operating Systems are:

• Windows v7 64-bit SP1(Professional) and Windows v8.1 (Professional and Enterprise), Windows v10 64-bit (Professional, Creators, and Enterprise).

• Macintosh  10.11.6, 10.12.6, 10.13.6 (new Mac OS version approved) 

New MacBooks and iMac’s: The new 2018 MacBook Pros and iMac’s do NOT currently work with MC 2018.7.  Engineering has already made a fix to address this problem in Media Composer 2018.8 and with this version, you can now launch Media Composer on the new  2018 Mac’s.   However, this is a “use at own risk” scenario as Avid has just received our 2018 Mac’s and have started qualification testing but not finished yet.  Once they have been qualified, you will be notified.

Manual approval of loading Kernel Extensions (KEXTs): With the release of Mac OS v10.13.x (High Sierra), Apple requires manual approval of loading Kernel Extensions (KEXTs). (For example Avid Nitris DX, BlackMagic, and AJA IO devices install Kernel Extensions.) At installation time, you should get a dialog saying that the KEXT was not loaded. You must go the “Security & Privacy” system preference and manually approve the KEXT. Keep the Security & Privacy pane open after you install the I/O device drivers so that you will see the notice that the driver has been blocked and press the “allow” button within 30 minutes of installing or the driver will be permanently blocked.

Avid DX Driver Separate Installer:  The Avid DX Driver is not automatically installed when you install the editing application. If you need to install the Avid DX Driver to work with your Avid IO device, you can install it separately.  The installer is located:

• (Mac) /Applications/Utilities/Avid Utilities

• (Windows) Program Files\Avid\Utilities\DXDrivers

Note:  For Windows systems, there is a Win7 driver and a Win10 driver in the Utilities folder. The Win7 driver works for both Windows 7 and Windows 8 systems.

Installers:   Previously, a separate installer was required for Media Composer | First. With this release, you have a single installer for Media Composer and Media Composer | First. Note: The option to run as Media Composer | First is now include in the Avid Media Composer Activation window.

AppMan 2018.8:  There is a new AppMan 2018.8.  This version supports a single installer for Media Composer and Media Composer | First. and resolves the following:

- Bug Number: AMPT-7739. Activating a Sibelius license deactivated the Media Composer dongle.

What’s New:  The following are new features in 2018.8

- Avid Generic Plug-In:  Avid continues working to remove dependencies on QuickTime libraries.
- Launching Media Composer | First:  There is a single installer for Media Composer and Media Composer | First
- Enhanced Correlation Tracker: You can select additional export options from Export to File.
- Exporting to XDCAM Change:  When exporting XDCAM OP1a, you select XDCAM through the Avid Media Processor.
- Exporting AVC-I OP1a: This release expands our support for exporting AVCI-OP1a.
- Avid Artist DNxIP Device: This release supports the Avid Artist | DNxIP device.
- Setting Automatic HDR Conversions for SDR Media:  The editing application allows you to map the white point of SDR (Standard Dynamic Range) media for REC2020 (HLG) and REC2020 (PQ) projects.
- 3D LUTS for HDR to 709 Conversions: We have added 3 LUTs that allows you to preserve high luminance values when converting to Rec.709.

What’s Fixed: The following have been fixed:

- Bug Number: MCCET-2582. You might have received an “Avid editor stopped working” error when performing a send to playback with XDCAM media to Airspeed.
- Bug Number: MCCET-2324. In some instances, the results of Color Correction Auto Contrast on some low contrast clips was not accurate.
- Bug Number: MCCET-2563. Capturing AVC LongG media using the Capture tool created DNxHD 145 media.
- Bug Number: MCCET-2578. You might have received a “Exception: BeginWriting failed” error when exporting as Windows Media.
- Bug Number: MCCET-2565. You might have received an “Assertion failed” error when trying to link or import WAV files.
- Bug Number: MCCET-2572. You might have received a CORE_SEGMENT_NOT_FOUND error when enabling (video) Dupe Detection with “Show Effect Contents” enabled in the Timeline settings.
- Bug Number: MCCET-2561. When performing a File > Open Bin on a read only workspace, the bin did not display with a RED locked icon.
- Bug Number: MCCET-2513. (Mac) You might have received an “Exception: std::exception” error when transcoding spanned AVCHD clips.
- Bug Number: MCCET-2566. In some instances, you could not import .m2t (HDV) files.
- Bug Number: MCCET-2112. You might have received an “Assertion failed” error when linking to AVC Long GOP with the Avid Generic Plug-in.
- Bug Number: MCCET-2567. When in Segment mode, dragging clips in the Timeline might not redraw properly if the Audio Mixer tool was open.
- Bug Number: MCCET-2034. Linking to Panasonic GH5 media using the Avid Generic plug-in might have displayed incorrect duration and timecode.
- Bug Number: MCCET-2441. In some instances, the editing application would show 100% CPU usage and would lock or hang when linking to specific MP4 files.
- Bug Number: MCCET-2544. Markers did not always transfer between two systems when the same Script was opened on both systems.
- Bug Number: MCCET-2543. The image might have appeared flipped when you relinked to an exported Tiff file.
- Bug Number: MCCET-2507. You might have received an incorrect Disk full error message when transcoding multiple spanned AVCHD clips.
- Bug Number: MCCET-2551. (Audio Mixer) In some instances, while stopping play to add volume effect to a clip, the fader slider would jump back. This did not happen if you were in Narrow Mixer mode.
- Bug Number: MCCET-2276. The editing application was slow to respond when changing audio mixer levels.
- Bug Number: MCCET-2500. Markers added in the Timeline did not always appear in the Marker Window.
- Bug Number: MCCET-2494. In some instances, the editing application might have crashed to a BreakPad window if you played back using the spacebar after adding markers from the keyboard.
- Bug Number: MCCET-2532. In some instances, performing a Find did not find all clips and sequences, in all bins in the project.
- Bug Number: MCCET-2489. 1080 50p (50 timebase) media in a 50i project was shifted by one frame.
- Bug Number: MCCET-2028. In some instances, linked XAVC S media using the Avid Generic Plugin did not display Timecode in the Start column.
- Bug Number: MCCET-2341. The List Tool change log was not correct. Comparing the same sequence with itself showed changes.
- Bug Number: MCCET-2524. In some instances, the position indicator (blue bar) was not in sync with sound and picture when using 3rd party I/O devices.

“What’s New” Guide and “ReadMe” Documentation:  As is normal practice, these documents have been uploaded to the Knowledge Base.  For the list of limitations, please refer to these documents.

How customers will obtain the August Media Composer 2018.8 Update:  The latest update to Media Composer and Media Composer | First will be made available on Monday, August 13, 2018 @ 12:00 noon ET.

1.  Customers who have already installed the latest version of Media Composer will be notified of the availability of the upgrade via the Application Manager. The Apps tab also provides a link to download and install the update when desired. 

2.  New customers who purchase Media Composer will receive the update in their Avid Master Account.

3.  Customers on current Update plans can download the Media Composer update either from their MyAvid Master Account or the Avid Download Center (login and password required.) 

4.  Customers NOT on a current Upgrade & Support contract must purchase either a new Media Composer Subscription Crossgrade or a new Perpetual license to receive this update. 

Reminder: This release of Media Composer requires an active Upgrade plan. Please remind customers of this before suggesting they install this update. 

ENJOY!!!!!!!!!!!!!!

Love the new live timeline feature.

(Can I say ‘About time!’?)

But I am stunned this doesn’t apply to audio mixer adjustment.

I mean you could, for quite a while, click on the mixer and hit play and adjust a track.

But why can’t you, in the middle of playback,

realizing an audio track needs a little nudge,

just click on the mixer and adjust a fader without it stopping?

What was this simple thing not added to the new feature?

There is no doubt my plugin suite would be larger if I was able to finance them.

I prefer it to subscription, and much easier than paying 1,700 at once for boris continuum.

Of course there are credit cards, but lately it seems easier to get financing for things ive purchased on affirm (just got a 7940x, 64gb ram, and much more hardware with them.)

thx

Media Composer 2018.8 released 8/13/18

Avid is pleased to announce the release of Media Composer 2018.8.   

Location: This release is available from Avid Master Accounts, Application Manager, and the Avid Download Center (login and password required).  Note:  The Download Center goes live at 12:00 pm ET and the remaining components will follow shortly after.

Operating System Updates: The following lists the qualified Operating Systems. Depending upon your hardware the qualified Operating Systems are:

• Windows v7 64-bit SP1(Professional) and Windows v8.1 (Professional and Enterprise), Windows v10 64-bit (Professional, Creators, and Enterprise).

• Macintosh v10.10.5, 10.11.6, 10.12.6, 10.13.6 (new Mac OS version approved) 

New MacBooks and iMac’s: The new 2018 MacBook Pros and iMac’s do NOT currently work with MC 2018.7.  Engineering has already made a fix to address this problem in Media Composer 2018.8 and with this version, you can now launch Media Composer on the new  2018 Mac’s.   However, this is a “use at own risk” scenario as Avid has just received our 2018 Mac’s and have started qualification testing but not finished yet.  Once they have been qualified, you will be notified.

Manual approval of loading Kernel Extensions (KEXTs): With the release of Mac OS v10.13.x (High Sierra), Apple requires manual approval of loading Kernel Extensions (KEXTs). (For example Avid Nitris DX, BlackMagic, and AJA IO devices install Kernel Extensions.) At installation time, you should get a dialog saying that the KEXT was not loaded. You must go the “Security & Privacy” system preference and manually approve the KEXT. Keep the Security & Privacy pane open after you install the I/O device drivers so that you will see the notice that the driver has been blocked and press the “allow” button within 30 minutes of installing or the driver will be permanently blocked.

Avid DX Driver Separate Installer:  The Avid DX Driver is not automatically installed when you install the editing application. If you need to install the Avid DX Driver to work with your Avid IO device, you can install it separately.  The installer is located:

• (Mac) /Applications/Utilities/Avid Utilities

• (Windows) Program Files\Avid\Utilities\DXDrivers

Note:  For Windows systems, there is a Win7 driver and a Win10 driver in the Utilities folder. The Win7 driver works for both Windows 7 and Windows 8 systems.

Installers:   Previously, a separate installer was required for Media Composer | First. With this release, you have a single installer for Media Composer and Media Composer | First. Note: The option to run as Media Composer | First is now include in the Avid Media Composer Activation window.

AppMan 2018.8:  There is a new AppMan 2018.8.  This version supports a single installer for Media Composer and Media Composer | First. and resolves the following:

- Bug Number: AMPT-7739. Activating a Sibelius license deactivated the Media Composer dongle.

What’s New:  The following are new features in 2018.8

- Avid Generic Plug-In:  Avid continues working to remove dependencies on QuickTime libraries.
- Launching Media Composer | First:  There is a single installer for Media Composer and Media Composer | First
- Enhanced Correlation Tracker: You can select additional export options from Export to File.
- Exporting to XDCAM Change:  When exporting XDCAM OP1a, you select XDCAM through the Avid Media Processor.
- Exporting AVC-I OP1a: This release expands our support for exporting AVCI-OP1a.
- Avid Artist DNxIP Device: This release supports the Avid Artist | DNxIP device.
- Setting Automatic HDR Conversions for SDR Media:  The editing application allows you to map the white point of SDR (Standard Dynamic Range) media for REC2020 (HLG) and REC2020 (PQ) projects.
- 3D LUTS for HDR to 709 Conversions: We have added 3 LUTs that allows you to preserve high luminance values when converting to Rec.709.

What’s Fixed: The following have been fixed:

- Bug Number: MCCET-2582. You might have received an “Avid editor stopped working” error when performing a send to playback with XDCAM media to Airspeed.
- Bug Number: MCCET-2324. In some instances, the results of Color Correction Auto Contrast on some low contrast clips was not accurate.
- Bug Number: MCCET-2563. Capturing AVC LongG media using the Capture tool created DNxHD 145 media.
- Bug Number: MCCET-2578. You might have received a “Exception: BeginWriting failed” error when exporting as Windows Media.
- Bug Number: MCCET-2565. You might have received an “Assertion failed” error when trying to link or import WAV files.
- Bug Number: MCCET-2572. You might have received a CORE_SEGMENT_NOT_FOUND error when enabling (video) Dupe Detection with “Show Effect Contents” enabled in the Timeline settings.
- Bug Number: MCCET-2561. When performing a File > Open Bin on a read only workspace, the bin did not display with a RED locked icon.
- Bug Number: MCCET-2513. (Mac) You might have received an “Exception: std::exception” error when transcoding spanned AVCHD clips.
- Bug Number: MCCET-2566. In some instances, you could not import .m2t (HDV) files.
- Bug Number: MCCET-2112. You might have received an “Assertion failed” error when linking to AVC Long GOP with the Avid Generic Plug-in.
- Bug Number: MCCET-2567. When in Segment mode, dragging clips in the Timeline might not redraw properly if the Audio Mixer tool was open.
- Bug Number: MCCET-2034. Linking to Panasonic GH5 media using the Avid Generic plug-in might have displayed incorrect duration and timecode.
- Bug Number: MCCET-2441. In some instances, the editing application would show 100% CPU usage and would lock or hang when linking to specific MP4 files.
- Bug Number: MCCET-2544. Markers did not always transfer between two systems when the same Script was opened on both systems.
- Bug Number: MCCET-2543. The image might have appeared flipped when you relinked to an exported Tiff file.
- Bug Number: MCCET-2507. You might have received an incorrect Disk full error message when transcoding multiple spanned AVCHD clips.
- Bug Number: MCCET-2551. (Audio Mixer) In some instances, while stopping play to add volume effect to a clip, the fader slider would jump back. This did not happen if you were in Narrow Mixer mode.
- Bug Number: MCCET-2276. The editing application was slow to respond when changing audio mixer levels.
- Bug Number: MCCET-2500. Markers added in the Timeline did not always appear in the Marker Window.
- Bug Number: MCCET-2494. In some instances, the editing application might have crashed to a BreakPad window if you played back using the spacebar after adding markers from the keyboard.
- Bug Number: MCCET-2532. In some instances, performing a Find did not find all clips and sequences, in all bins in the project.
- Bug Number: MCCET-2489. 1080 50p (50 timebase) media in a 50i project was shifted by one frame.
- Bug Number: MCCET-2028. In some instances, linked XAVC S media using the Avid Generic Plugin did not display Timecode in the Start column.
- Bug Number: MCCET-2341. The List Tool change log was not correct. Comparing the same sequence with itself showed changes.
- Bug Number: MCCET-2524. In some instances, the position indicator (blue bar) was not in sync with sound and picture when using 3rd party I/O devices.

“What’s New” Guide and “ReadMe” Documentation:  As is normal practice, these documents have been uploaded to the Knowledge Base.  For the list of limitations, please refer to these documents.

How customers will obtain the August Media Composer 2018.8 Update:  The latest update to Media Composer and Media Composer | First will be made available on Monday, August 13, 2018 @ 12:00 noon ET.

1.  Customers who have already installed the latest version of Media Composer will be notified of the availability of the upgrade via the Application Manager. The Apps tab also provides a link to download and install the update when desired. 

2.  New customers who purchase Media Composer will receive the update in their Avid Master Account.

3.  Customers on current Update plans can download the Media Composer update either from their MyAvid Master Account or the Avid Download Center (login and password required.) 

4.  Customers NOT on a current Upgrade & Support contract must purchase either a new Media Composer Subscription Crossgrade or a new Perpetual license to receive this update. 

Reminder: This release of Media Composer requires an active Upgrade plan. Please remind customers of this before suggesting they install this update. 

ENJOY!!!!!!!!!!!!!!

I edit a novel where they use Sony f55 cameras and managed through silverstack. We use Glookast to import and Interplay to make master-clips available to publishers. The Bin FPS column is empty, however in the SIlverstack .pdf report, the value is there, 24fps, 60fps etc.

How do I get the fps information to appear in the fps column of the bin?

Thank you.

hi there

My system is windows 10 / HP Z840 / NVidia Quadro P4000 .

I am using 3rd party i/o = AJA Kona 3g. All the latest drivers and software. I just installed the latest AVID MC 2018.8.

i get an unpleasant screen glitch on the player window, when (and only when) i use the mouse to shuttle through a multicam clip. In normal play mode things are fine. SDI out is fine. when play stops i get the ugly glitch ( see thumbnail) on the player window.

when i resinstall MC 2018.4 this behaviour goes away.

could be like a buuuuug! maybe ...

best regards