CTM Solutions

Avid is pleased to announce the release of  Media Composer 2023.3 today. This will be available in the customer's MyAvid Master Accounts, through the Avid Link application itself, and from the Download Center. 

 

Location at Launch: The Media Composer 2023.3 (Mac and PC) will be available in the customer's 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 2023.3 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2023.3 is released on Tuesday March 28th, 2023.

 

New in Media Composer v2023.3: The following are new for Media Composer v2023.3.

 

- Copy Media from a Remote User to NEXIS Workspaces

- Improvements to Pro Tools Session Export

- New “Protect Project Bin” Command Added to Bin Context Menu

- Right-Click to Add a Folder Within a Folder

- New User Profiles and Workspaces for Editors Transitioning from Adobe Premiere Pro

- Update to Creation Date Column in the Marker Tool

- Choice of File or Folder in Relink Dialog

- Live Link Support for UME

 

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

 

·         Bug Number: MCCET-4850. Opening another sequence while in the Color Correction workspace caused the Edit workspace to load and altered the layout of the original Color Correction workspace.

·         Bug Number: MCCET-4507. When switching between working and target settings for Dynamic Relink in the Timeline, the Source Browser window turned black and did not refresh properly until clicked.

·         Bug Number: MCCET-4843. Floating bins changed position and size each time a project was closed and reopened.

·         Bug Number: MCCET-4569. Color Correction panel disappeared when scrubbing in the Timeline with the Color Correction workspace activated and “Clicking the TC Track or Ruler Disables Smart Tools” option enabled in the Edit tab of the Timeline Settings window.

·         Bug Number: MCCET-4512. "Assertion failed" TimeWarp error caused Production Management check-ins to fail when the Neat Video plug-in was installed.

·         Bug Number: MCCET-4720. Keyboard shortcuts for parameter values in the Effect Editor did not work as expected after using sliders.

·         Bug Number: MCCET-4948. In some instances, Media Composer would not relink all partially restored audio files when using Dynamic Relink.

·         Bug Number: MCCET-4760. (MediaCentral | Production Management) In some instances, logging out of Production Management with media status indicators for Resolution enabled (black "dots" in columns within the Production Management Window) caused the application to hang.

·         Bug Number: MCCET-4521. (MediaCentral | Production Management) The media status indicator in the Production Management Window, represented by a black dot in the corresponding format column, did not display properly when media was online and available.

·         Bug Number: MCCET-4960. (macOS) Some user interface elements would disappear from the bottom row of the Markers window when the window or its columns were resized.

·         Bug Number: MCCET-4738. Media Composer crashed while scanning and rebuilding the. database for UME folders containing a large number of MXF OP1a files.

·         Bug Number: MCCET-4913. (MediaCentral | Production Management) Some audio tracks were offline after using portions of master clip in a sequence and delivering with Production Management Delivery Service.

·         Bug Number: MCCET-4628. AAF files exported from Media Composer and opened in Pro Tools caused some values to change for fades, clip gain, and other audio parameters.

·         Bug Number: MCCET-4784. Spanned media did not link properly and would revert to media offline when Dynamic Relink was enabled.

·         Bug Number: MCCET-4870. Labels were inverted in the surround sound pan controls of the Audio Mixer for tracks panned between the front and rear (f/r) speaker positions. Although the labels were incorrect, pan controls for the Y-axis position of the panner were not affected.

·         Bug Number: MCCET-4961. (macOS) Media Composer 2021.12.6 would not allow the creation of projects and bins on shared NEXIS storage.

·         Bug Number: MCCET-4409. Users were prevented from creating more than 999 bins at the root level of the project folder.

·         Bug Number: MCCET-4816. Group clips were incorrectly scaled in the Record monitor if a gap existed before the clips in a sequence and the resolution of clips did not match the project settings.

·         Bug Number: MCCET-4882. MultiGroup clips with audio waveforms enabled caused Media Composer to crash.

·         Bug Number: MCCET-4915. When performing a Dynamic Relink operation, audio was offline for clips with audio tracks not starting at A1.

·         Bug Number: MCCET-4957. Adding a Baselight or Magic Bullet Looks effect to a sequence caused "an unrecoverable error has occurred" or "a serious error has occurred" message to appear when relaunching a project with that same sequence already opened.

·         Bug Number: MCCET-4977. Enabling "Show Target Availability" or “Show Mismatches” for Dynamic Relink caused a decrease in performance while working in the Timeline.

·         Bug Number: MCCET-4976. The "Override all Bin font sizes" option in User Interface Settings did not work when applied.

·         Bug Number: MCCET-4587. (MediaCentral | Cloud UX) In some instances, the MediaCentral |Cloud UX panel would not load after logging out and logging back in with a different user.

·         Bug Number: MCCET-4895. (MediaCentral | Cloud UX) In some instances, the MediaCentral |Cloud UX panel would not load after logging out and logging back in with the same user and a different project.

·         Bug Number: MCCET-4503. Audio clip gain values were lost and returned to unity gain if the clip was re-rendered, after making an adjustment to any plug-ins that were already applied and rendered.

·         Bug Number: MCCET-4970. (MediaCentral | Production Management) Ingesting P2 files and creating sequences of clips using third-party MintUpload software caused an "Assertion failed: *expectedBytesRead" error.

·         Bug Number: MCCET-4706. Enabling Dynamic Relink caused linked .mov QuickTime files with a Matte Key (DNxHD with alpha) to go offline.

·         Bug Number: MCCET-4602. Master Caption List was out of order when the SubCap effect was placed on two tracks and some captions were muted.

·         Bug Number: MCCET-4803. Linking or Importing Apple ProRes 4444 Mov files created with an Arri Alexa Mini caused Media Composer to quit unexpectedly if QuickTime was installed.

·         Bug Number: MCCET-4407. Selecting multiple lines of dialog in the Script window and pressing the spacebar (or right-clicking and selecting "play" from the context menu) caused the incorrect line of dialog to play back.

·         Bug Number: MCCET-4814. (macOS) When loading a subclip in the Script window, an in point was automatically marked at the end of the clip.

·         Bug Number: MCCET-5029. When using “Transcode on Send to Playback" with a sequence that has Group clips, the Send to Playback would fail.

·         Bug Number: MCCET-4953. (MediaCentral | Production Management) Audio waveforms for linked clips were very slow to draw, which significantly impacted performance and the ability to work within the interface.

·         Bug Number: MCCET-4573. Media Composer was slow to launch when using the Floating License backup server.

·         Bug Number: MCCET-3909. Media Composer appeared to hang on launch when using a checked-out license with no VPN connection to the license server.

·         Bug Number: MCCET-5027. The Timecode Window, accessed via the Tools menu, would not redraw properly after changing the size of its font, which affected the amount of black space in the window.

·         Bug Number: MCDEV-17005. Splitter in Effect Palette changed position after a restart.

·         Bug Number: MCDEV-15381. Highlighted text in the Comment field of the Marker tool was white on white and difficult to read when using dark interface skins.

·         Bug Number: MCDEV-15832. Track names containing dots caused a triangle to appear on the Track Selector panel.

·         Bug Number: MCDEV-16738. "Sync Lock All Tracks" button command did not work if Timecode (TC) track was hidden.

·         Bug Number: MCDEV-17162. The Lock/Unlock Sequence commands, activated by Option+Right-Clicking (macOS) or Alt+Right-Clicking in the Track Control panel, did not lock all tracks and displayed inconsistent messaging.

·         Bug Number: MCDEV-16680. Fast Menu and Quick Find Field were not always visible in the Markers tool or Timeline Clip Notes windows, until windows were resized to show scrollbar.

·         Bug Number: MCDEV-15189. Source Browser would not attach as expected to other tools and windows via its tab in the vertical title bar.

·         Bug Number: MCDEV-17579. Double-clicking on a search results multiple times in the Find window caused the bin containing the clip to eventually float and close.

For details on the complete bug fixed, see the attached document and the final update will be uploaded to the Knowledge Base Media Composer 2023 Documentation page at launch.

 

In a quest to see what files will work in MC (or in MC after conversion) leaves only one file type that is a problem....HEVC file with alpha.   They link fine and can be seen fine but there is no alpha.

The only other file that was an issue was GoPro.  MC will not link or transcode them.  But Shutter Encoder will output GoPro files with alpha just fine to QT animation (or MP4 if alpha is not needed).  Then its easy to use them in MC.

Is there an answer to this small HEVC w/alpha problem?

BTW...meanwhile, RGBKeyer in MC is making a nice alpha cut with the HEVC files.....so, its really not a problem for MC with any file type...it just takes a little work for GoPro and HEVC files with alpha.

Don't know exactly if there's a workaround, or if this is a new feature request.

From time to time I need to rebuild from 0 a series of dynamically timewarped clips, so I use AMC Timewarp, editing using the Position window, together with awesome Blend-X plugin using Difference as key option.

That's good, sometimes needs a lot of time but results are 100% as the original timewarps.

My question is: why data (keyframes) edited in the Position window cannot be passed and modified in the Speed window?

I mean, if I open both Speed/Position, both are displaying the same data in a different way, but if I switch the edit mode from Position to Speed, all keyframes disappear and the curve is completely deleted.

Personally I think that this interchangable feature could be very useful to refine curve using Speed window, doing the same in Position is not so intuitive.

 

Max

Hey people

 

I have been editing for over 28 years now and recently discovered the advantages of audio ducking. But right from when the key frames were intoduced for audio gain I stuggled to work with them. I found them way too fifddly for quick audio adjustment and as I often lasso my cuts to enter trim mode, I found them in the way and being slected rather than the cut point ...etc... Also found I neede to expand the audio track so I could adjust the levels but on busy timelines with 24 audio tracks, the timeline realestate was being eaten up too quickly... SO I did not stick with it.

BUT there must be a better way. So Can anyone advise me on the best way to quickly an easily use the audio keyframes. Aslo a quick way to reset the track so that the audio ducking keys can be removed at once. 

 

Thanks

 

John

Right mix of 17 cams.  I need to work in i as the majority are i and seem to get artefacts when exporting if working in P.

Its music so need to output P really - what the best way to achieve that from within Avid and without any Saphire plugins etc?  Been a while since I did it as always have to work in i for TV!  Cheers.

 

Did my first Phrase Find search today. Is it possible to Filter out Linked clips from results? Or to only search one MultiGroup?

Creating a title page in Avid titler, I am pretty sure I was once able to change the font color on selected words within a sentence or paragraph. Now, if I try to change the color on a word in a sentence the entire sentence changes.  Is this normal?

Hi everyone, my company upgraded to avid 2022 a few months ago, and this problem keeps on happening. Whenever I click on a dated folder to make a bin, the first bin opens in the folder, but when I make a second one (we do AMAs and MD (transcoded) separately) it opens in the project instead of the selected folder. Usually i have to delete the bin or move it over, but I'm wondering if anyone else has this issue or if it is a specific bug, I would just like both bins to open in the folder. Thanks

I'm a little frustrated, because after updating to Avid 2022.12, Media Composer will no longer launch on my machine. When I click the icon, it throws up a useless error box and asks me to send the error to Avid (I have). I'm at a loss - can anyone help me figure out what steps to take to even know what's happening?

Here are my system specs:

Processor Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz   3.60 GHz

Installed RAM 64.0 GB (63.9 GB usable)

System type 64-bit operating system, x64-based processor

nVidia GeForce GTX 1070 Ti 8GB

Edition Windows 11 Pro

Version 22H2

Installed on ‎9/‎30/‎2022

OS build 22621.1413

Experience Windows Feature Experience Pack 1000.22639.1000.0

Also - and I'm not sure this is related - but Avid Link will no longer download anything. Every time I try to update Link or MC, it starts to download, and then tells me that the download failed while providing zero other information. This is, as you can imagine, not helpful. I've had to visit the Avid download center through my web browser to download update files.

 

 

We have had this problem for awhile.  Color correct all the clips.  Everything is fine.

Go to export out the sequence....and after the export is done....certain clips have this Red Black Red stripes.  No video...just these colors.

 

I found another string that talked about it...but no solutions other than...match the footage and re-insert it and re-color correct.  But why does the export blow it up ?