Good news!!! Media Composer 2022.10 is live on the Download Center at noon today.

Location at Launch: The Media Composer 2022.10 (Mac and PC) is available in your MyAvid Master Accounts, through the Avid Link application itself, and from the Download Center. 

Status of Support Plan: The ability to launch this Media Composer 2022.10 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2022.10 will be release on Thursday October 20^th, 2022 at noon ET.

Media Composer Notes:

• MCDEV-11537 If you intend to use full-frame stereoscopic with an Avid Artist DNxIQ, you may want to remain with Media Composer v2018.12.x until the issues with Stereoscopic support are resolved in a future version.
• Match Frame results for the subclip of a Group or MultiGroup clip created in Media Composer v2022.7 and later will load the original subclip of the Group or MultiGroup clip.If using subclips of a Group or MultiGroup clip created in an earlier version of Media Composer, the same Match Frame operation will load the Group or MultiGroup clip.

What’s New in Media Composer 2022.10:  

The following are new for Media Composer v2022.10:

• Working with Proxy Media in an Avid NEXIS | EDGE Environment
• Media Cache Dialog Update
• Multiplex I/O Support for Multiple Open I/O Plug-ins
• New Relink Menu and Linked Media Dialog
• New Sequence Templates and User Setting
• “Choose For Me” Options Added for New Projects
• Keyboard Shortcuts to Switch Focus Between Windows and Tabs
• Bin Metadata Tooltips
• FreeType Font Support for Titler+
• Support for Two or More Ganged Groups in the Audio Mixer

For details see the What’s New document uploaded to the Knowledge Base Media Composer 2022 Documentation page at launch.

What’s Fixed in 2022.10: The following has been fixed.

• Bug Number: MCDEV-15479. Timeline would center around the blue bar (current position indicator) while zooming in and out during playback and did not retain the position selected by user when “Timeline Movement During Play” was set to “Scroll”. Media Composer now retains the position selected by user and the blue bar is centered when playback is stopped.

• Bug Number: MCCET-4799. Naming a Custom Preset with Japanese characters resulted in text that was not properly decoded.
• Bug Number: MCCET-4775. In some instances, clips created via Interplay Capture using Airspeed generated a Structured Exception error followed by a crash report dialog when dragging to the Timeline from the Source monitor.

• Bug Number: MCCET-4233. Titler+ was very slow to render titles in a 1080i/50 sequence, especially when compared to a 1080p/25 sequence.

• Bug Number: MCCET-4779. Using Preview in the AudioSuite tool played a portion of the original media beyond the end of the clip as edited into the timeline.

• Bug Number: MCCET-4580. When adding markers to an audio track using the Source monitor in a 1080p/24 project, the marker position jumped to a random location in the Timeline. When using different project settings, the current position indicator jumped to a random location after clicking on a marker in the Marker window.
• Bug Number: MCDEV-15844. Creating and starting a new project opened the default bin as a floating Bin Container window.
• Bug Number: MCDEV-14054. Making changes in the List Tool did not affect the appearance of corresponding settings name.
• Bug Number: MCDEV-13183. Dragging tabbed bins from the Bin Container window created a floating bin with the Bin Container sidebar.
• Bug Number: MCDEV-16494. Media Composer host panel did not retain its maximized state after a project was closed and reopened.
• Bug Number: MCCET-4634. When the comments column in the Markers window was too large, entering comments caused text entry to scroll off the screen.

• Bug Number: MCCET-4772. Bins without changes were saved to the Attic when closed, causing the Attic to grow larger than necessary.

• Bug Number: MCCET-4726. In some instances, the Media Composer splash screen would not show option and license date information.
• Bug Number: MCCET-4661. Sequences loaded into the Source Monitor from the Production Management window had their names appended with ".copy.01", if the sequence already existed in an open bin. Media Composer now appends their name with ".AutoCopy.01" (with consecutive numbering) to indicate that this happened automatically.
• Bug Number: MCCET-4768. Option to "Skip Existing Transition Effects" was unavailable when using keyboard shortcuts to navigate the Quick Transition dialog box, even though "Apply To All Transitions" was selected.

• Bug Number: MCCET-4592. Switching from the Edit workspace to the Effects workspace put Media Composer into Segment mode.
• Bug Number: MCCET-4736. File129 output for an EDL did not allocate the correct number of characters and could not parse correctly.
• Bug Number: MCCET-4567. Top menu bar was cropped on dual monitors after toggling workspaces.
• Bug Number: MCCET-4236. Switching quickly between workspaces linked to custom bin

layouts caused Media Composer to crash.

• Bug Number: MCCET-4728. Intermittent clicks were heard when playing back audio through a Dante interface and video was played through NDI.
• Bug Number: MCCET-4637. Workspace layouts did not restore properly and made docked bins become undocked.
• Bug Number: MCCET-4710. (Windows)(MediaCentral | Production Management) “Exception: Structured Exception” error appears when starting Media Composer and "Connecting to MediaIndexer" status is displayed on splash screen.
• Bug Number: MCCET-4687. Selecting "Send to Export" in the Output menu reset some Motion Effect parameters and unrendered the effects.

• Bug Number: MCCET-4629. Adding an Audio Track Effect to a track with Group clips on it resulted in the audio in the Group clip not switching or displaying properly.

• Bug Number: MCCET-4549. Some users in a MediaCentral | Production Management environment experienced long delays and, in certain instances, crashes when logging in, opening projects and checking out media in projects.

• Bug Number: MCCET-4537. Send to Playback did not work for "AVC Long GOP 50 1080p 50" media.
• Bug Number: MCCET-4695. Projects opened slower after adding MediaCentral Production Management Folder settings to Site Settings in MediaCentral.

• Bug Number: MCCET-4644. Exporting subclips from a bin or the Source monitor to an MXF OP1a file caused an “invalid trim” error.
• Bug Number: MCCET-4771. (Windows) In some instances, bins were very slow to open.
• Bug Number: MCCET-4782. Enabling waveforms caused general sluggishness and slower performance when working in bins and sequences.

• Bug Number: MCCET-4211. Titler+ created unwanted keyframes when text was deleted from a text box with existing keyframes.
• Bug Number: MCCET-3408. (macOS) Title Tool caused Media Composer to crash when saving a title with Full Screen Playback enabled.

• Bug Number: MCCET-4540. In some instances, after moving a bin or closing a folder, items above it were automatically selected.
• Bug Number: MCCET-4705. (macOS) Right-clicking in Script window caused Bin Fast Menu options to appear.
• Bug Number: MCCET-4717. In some instances, Media Composer would crash to the desktop when working with Dynamic Relink and "Show Target Availablity" was enabled.
• Bug Number: MCCET-4585. Audio Punch-in did not work properly after Film option was selected during project creation.
• Bug Number: MCCET-4516. When live capturing with the Capture Tool, the Extra Field Selection did not populate the corresponding custom column in the bin, but worked when logging only.

• Bug Number: MCCET-4184. There is a delay from the time a letter is typed to it being displayed on screen when using Chinese characters in Titler+.

• Bug Number: MCCET-4620. D-Verb settings reverted to default values when they were nested with a clip that had Audio EQ applied.
• Bug Number: MCCET-4674. Media Composer created a floating bin by default for new projects, even when this option was not selected.

• Bug Number: MCCET-4242. When working with some AudioSuite plug-ins, rendering stereo audio was slow in a Production Management/Avid NEXIS environment.
• Bug Number: MCCET-4658. Export Settings were not retained when using custom presets to export media.
• Bug Number: MCCET-4306. In some instances, toggling the "Override Working Settings with Target Settings" option when using Dynamic Relink caused audio and video tracks to become out of sync.
• Bug Number: MCCET-4462. Linking AVC-I Class100 1080p50 media was unsuccessful and returned "The media is unsupported" or "ExceptionUNKNOWN horizontal subsapling error" message, depending on the version of Media Composer.

• Bug Number: MCCET-4702. (macOS) The Enter key did not always work when entering values in the Audio Mixer tool

For details on the complete bugs fixed, see ReadMe document uploaded to the Knowledge Base Media Composer 2022 Documentation page at launch.

ReadMe: The new ReadMe was uploaded to the Knowledge Base Media Composer 2022 Documentation page at launch.

I have Windows 10 Pro 64 bit v. 10.0 build 19043.2130, nVidia GeForce RTX 2080 Super, driver 461.72.

The compatibility chart says, MC 2022.10 needs driver 513.46. When I try to install, the message "driver not compatible with my system".

A search inwww.nvidia.com/de-de/geforce/drivers/ shows driver 522.30 (2022.10.18) as newest driver for my system. Driver 513.46 is not mentioned.

Will this driver be compatible with MD 2022.10?

Riddle me this Avid,

Why is Copy Media in Media Composer 22.10 a Nexis Edge only function? This feature reads as the new Media Mover tool people have been begging Avid for for over 10 years. This feature sounds amazing. Release it from Nexis Edge. Let me use this on prem to copy bins to drives. So WOW!

Just to be clear, although it seems pretty clear from the documentation, you would require the Enterprise version remotely to use the new Nexis/Edge workflow? That excludes Ultimate and full Perpetual? It doesn't really seem to be a Teradici/Z Central killer does it, in that even facilities are unlikely to invest in remote Enterprise seats either? Are we likely to see a roll-out to the other licences?

Mercer:

Just to be clear, although it seems pretty clear from the documentation, you would require the Enterprise version remotely to use the new Nexis/Edge workflow? That excludes Ultimate and full Perpetual? It doesn't really seem to be a Teradici/Z Central killer does it, in that even facilities are unlikely to invest in remote Enterprise seats either? Are we likely to see a roll-out to the other licences?

Yes, MC Enterprise license is required for remote users to have access to the proxy media.

I have voiced this issue to every level of Avid internal since 2021. This might be okay for NBC or Paramount. But, a total no go for smaller companies like us. I'm willing to invest in Enterprise in house but no way I can require remote independent contract editors or producers to make their own personal invest in Enterprise.

I'd also like to point out that the Read Me for 22.10 states that v12.4 or higher of BlackMagic's Desktop Video is required for use with Blackmagic-based hardware. However, the latest version available on Avid's website is v12.2. Checked under "My Products" and checked in the download center. BlackMagic Desktop Video v12.4 is not available for download from Avid!

For AJA-based hardware the required version of AJA's Desktop Video ,v16.2.2, is available on Avid's website.

ck123:

I'd also like to point out that the Read Me for 22.10 states that v12.4 or higher of BlackMagic's Desktop Video is required for use with Blackmagic-based hardware. However, the latest version available on Avid's website is v12.2.

Haven't installed 22.10 yet because of this.
Avid, please release updated BMD drivers! Thanks.

Rihafilm:

ck123:

I'd also like to point out that the Read Me for 22.10 states that v12.4 or higher of BlackMagic's Desktop Video is required for use with Blackmagic-based hardware. However, the latest version available on Avid's website is v12.2.

Haven't installed 22.10 yet because of this.
Avid, please release updated BMD drivers! Thanks.

Just to be sure, has everyone tried right-clicking on the hardware button (far right of the timeline tool bar) and making sure your BM hardware is selected? I had to do that after installing 2022.10 in order for it to use my hardware.

In the meantime I'm running BMD's v12.0 drivers with my UltraStudio Mini Monitor and Media Composer 2022.10, and it seems to be running fine. I don't know if there's some crucial capability I'm missing, or if there will be problems with other BM hardware, but this config seems ok.

Roland Achini:

The compatibility chart says, MC 2022.10 needs driver 513.46.

It is also not supported for the 513.46 driver for the Quadro P2000 card.

According to the specification on the Nvidia website.

Nvidia offers driver 517.40.

V.

EDIT:

So I managed to click through to the correct driver 513.46 for Quadro cards on the Nvidia website.

nVidia driver 517.40 also does not work with my system.

camoscato:

Just to be sure, has everyone tried right-clicking on the hardware button (far right of the timeline tool bar) and making sure your BM hardware is selected? I had to do that after installing 2022.10 in order for it to use my hardware.

This is exactly what I suggested in another thread. Here with DV 12.4, works as expected and I didn't have to do anything. Existing Nvidia driver was OK too on a Quadro.

Vilem:

Roland Achini:

The compatibility chart says, MC 2022.10 needs driver 513.46.

It is also not supported for the 513.46 driver for the Quadro P2000 card.

According to the specification on the Nvidia website.

Nvidia offers driver 517.40.

V.

EDIT:

So I managed to click through to the correct driver 513.46 for Quadro cards on the Nvidia website.

You have the wrong driver. That's DATA CENTER not Desktop.

https://www.nvidia.com/download/driverResults.aspx/191342/en-us/

NVIDIA RTX / Quadro Desktop and Notebook Driver Release 510

Version:	R510 U8 (513.46)  WHQL
Release Date:	2022.8.2
Operating System:	Windows 10 64-bit, Windows 11
Language:	English (US)
File Size:	640.74 MB

ck123:

Yes, MC Enterprise license is required for remote users to have access to the proxy media.

I have voiced this issue to every level of Avid internal since 2021. This might be okay for NBC or Paramount. But, a total no go for smaller companies like us. I'm willing to invest in Enterprise in house but no way I can require remote independent contract editors or producers to make their own personal invest in Enterprise.

IMHO, the whole Edge server is stupid. Or at least limiting the workflow to Edge + Enterprise MC.

This should be a simple addon to a Nexis server and that is it.

My company can benefit from this, but I refuse to recommend it because of the added complexity and cost...

The bandwidth demand will be much higher than Teradici, zCentral, Jump, Splashtop. MC Enterprise licenses. Edge hardware and license. etc. etc.

Dom Q. Silverio:

The bandwidth demand will be much higher than Teradici, zCentral, Jump, Splashtop. MC Enterprise licenses. Edge hardware and license. etc. etc.

Yes another badly thought out move by Avid. No editor (the real end consumer for MC that matters) cared about or wanted SRT either. In the UK the vast majority of facilities and broadcasters are on 2018, 2020 at most, QC testing and stability prevent anything else and they will not buy Enterprise licences for freelancers. Together with subscription all these things seem like, as one prominent industry CEO called it, 'treating your loyal customers like prisoners'.

You can't just add NEXIS Edge to a NEXIS, you install and it requires a set of services to run the streaming proxy service, remote bins and collaboration, distributed processing (which assists in the proxy creation), the web browser streaming service and the Media Composer Licensing service. All of these services have to be installed on a server. 

Dave

Dom Q. Silverio:

ck123:

Yes, MC Enterprise license is required for remote users to have access to the proxy media.

I have voiced this issue to every level of Avid internal since 2021. This might be okay for NBC or Paramount. But, a total no go for smaller companies like us. I'm willing to invest in Enterprise in house but no way I can require remote independent contract editors or producers to make their own personal invest in Enterprise.

 

IMHO, the whole Edge server is stupid. Or at least limiting the workflow to Edge + Enterprise MC.

This should be a simple addon to a Nexis server and that is it.

My company can benefit from this, but I refuse to recommend it because of the added complexity and cost...

The bandwidth demand will be much higher than Teradici, zCentral, Jump, Splashtop. MC Enterprise licenses. Edge hardware and license. etc. etc.