Hi,

I'm sure this question has a painfully obvious answer. My timecode has letters A-D at the end. I guess it thinks I'm doing 4-perf. But I don't remember setting it up as a film project. Format tab says project type 23.976 NTSC VIDEO

The letters also then come up on the timecode burn-in (see screen capture). Where do I turn off the letters?

(Also, I don't think this is related... I can't open the Timecode Window setting in my Settings.)

Thanks

How do you resize 4K sorce footage with alpha in an HD (1920 x 1080) project.  You cannot just resize because AVID is rasteriing the 4K source in HD, then scaling so it looks terrible (1/2 res)!  Im am trying to use framflex on both alpha and fill, but copying and pasting keyframes IS TERRIBLE!!  Sometimes it works, sometimes it does not.  Most of the time it does not.  On top of that, the display will eithier not update correctly of flash other frames in timeline!  We should be able to scale 4K sorces both with and without alpha with resolution independance (scale into 4k source material up to match raster size with 3d tool or scale tool in the keying fx editor)

Hello all, it's been a while; have been missing Avid, and this forum.
Now I need to upgrade in order to activate, and would love to hear any warnings or advice!

Likely way forward is MC 2018.9 on OSX 10.13.6
Likely machine is MacBook Pro Retina 13-inch, early 2015
Processor 3.1 GHz Intel Core i7
Memory 16 GB 1867 MHz DDR3
Graphics Intel Iris Graphics 6100 1536 MB
Serial number C02S914DFVH8

Here in the Northern Hemisphere the days are getting longer again, hurrah
Seasons greetings to us all - and best to the South (hope yr not ablaze)
Susi

Lately I've run into some problems with Sonicfire Pro crashing that lead me to suspect an issue with Avid's audio driver.  Whenever I preview an audio track from the SmartSound store, Sonicfire Pro crashes.  This does not happen when both programs are running, but only after closing Avid.

My guess is that the crashing results from some memory corruption when Avid’s audio driver hands off control to Apple's native audio driver.  To test this, I ran the “Free Memory” application in Parallels Toolbox after closing Avid.  I then launched Sonicfire Pro.  No crashes.  Can anyone confirm this is an issue on their system, as well?

-- 

Michael

The last release of the year has now launched.  Updates to Media Composer 2019.12 are available from Avid Link, MyAvid and the Avid Download Center (login and password required).

Status of Support Plan: The ability to launch this Media Composer 2019.12 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2019.12 has been released today, December 23, 2019.

IMPORTANT: macOS Support:  Media Composer v2019.12 does NOT currently support macOS v10.15 (Catalina) – we expect a Q1 release in 2020 to support Catalina. 

*** (macOS) IMPORTANT: If you are installing the editing application and you have a previous version of the editor on your system, manually uninstall the editing application before you try and install v2019.12. If you do not manually uninstall, you might receive a “CATWrapperConfig.cpp” error message when opening your project.   If you do experience this issue, you can manually remove the file here:

Applications/Avid\ Media\ Composer/SupportingFiles/CodecToolkit_Config/dfm/dnxpacked.lua

What’s Changed in 2019.12:  The following has changed in Media Composer v2019.12.

1. Show Bin in Sidebar 

2. Inspector Tool Update

3. OpenEXR Export Support

4. Avid Titler+ Updates

5. Media Composer and Distributed Processor Worker on the Same System

6. Media Composer | Enterprise Settings Update

7. Updated ACES Support

What’s Fixed in 2019.12:  Below is the list of items fixed….

- Bug Number: MCCET-3285. With connected IO hardware such as AJA or Blackmagic, you could not downscale monitor output on an HD client monitor.

- Bug Number: MCDEV-11345. When tools were tabbed with the Composer Window, the video displayed on top of the tools.

- Bug Number: MCCET-3374. Bin sifting was not retained after closing and opening the bin. 

- Bug Number: MCDEV-12014. Sometimes when the Audio Mixer was layered over another tool or bin, and the Timeline or Composer had focus, hovering the mouse over the Audio Mixer made the Audio Mixer the active window.

- Bug Number: MCDEV-12015. Minimizing Media Composer on dual monitors with auto hide sometimes resulted in losing Menus, Workspace Bar, and background host panel.

- Bug Number: MCCET-3210. The Source Record monitor would go black, and menus stopped working if you were working with the Source Browser and the Windows taskbar was set to auto-hide.

- Bug Number: MCDEV-12099. Thumbnails for subclips were recaching every time you opened a bin in Frame View, slowing performance.

- Bug Number: MCDEV-12347. With large projects on shared storage, updating the project after changing a bin name was slow.

- Bug Number: MCCET-3257. (macOS). When waveforms were enabled, clicking in the Timeline might have resulted in a crash and Breakpad error.

- Bug Number: MCCET-3345. (macOS) In some instances, after performing a lasso and trim, the Source monitor would display black.

- Bug Number: MCCET-3171. (macOS v10.12.6). Media Composer was not populating the second screen on a dual monitor setup.

- Bug Number: MCCET-3305. You might have received a “Cannot find bin x in Project x” when performing a Find Bin.

- Bug Number: MCCET-3108. The text to identify locked bins was not displayed in bold.

- Bug Number: MCCET-3299. Using JKL did not work properly when playing a clip with a Timewarp effect.

- Bug Number: MCCET-3355. Imported tga files were only one frame in duration.

- Bug Number: MCCET-3304. Newly created bins that were empty did not save size nor position when working with shared storage.

- Bug Number: MCCET-3206. In some instances, clip frames would rebuild on the entire sequence.

- Bug Number: MCCET-3388. You could not resize an effect +/- 10 steps using the keyboard shortcuts.

- Bug Number: MCCET-3369. French, Swedish, German, and Danish letters in Bin Script View comment field didn’t display properly.

- Bug Number: MCCET-3333. Sequential Targa (.tga) files could not be imported correctly. 

- Bug Number: MCCET-3337. When right-clicking on linked clips in a bin, the Relink to Files option might have been grayed out.

- Bug Number: MCCET-3404. (NRCS Tool) When browsing iNews database, the cursor continued showing a spinning wheel even after the result had been returned.

- Bug Number: MCCET-3292. A Transition did not play correctly in full quality if the first clip was an imported still image with XDCAM HD or AVC Long GOP.

- Bug Number: MCCET-3399. The position info did not display even if you selected Settings > Grid > Display > Show Position Info.

- Bug Number: MCCET-3372. Media Composer became unresponsive when you tried to perform a transfer to a Transfer service that was not available.

- Bug Number: MCCET-3342. If Waveforms were enabled, the Timeline responsiveness lagged when dragging or trimming.

- Bug Number: MCCET-2817. Trimming a clip with an AudioSuite Time compression/expansion effect might have affected subsequent renders.

- Bug Number: MCCET-3251. In some instances, Media Composer vaporized when extracting a segment.

- Bug Number: MCCET-3330 (Avid Artist DNxIO, Avid Artist DNxIQ). In some instances, 720p25 projects were incorrectly converted to 1080i50.

- Bug Number: MCCET-3250. (macOS) In some instances, when editing keyframes and then entering Trim mode, the Source Record monitor would appear black.

- Bug Number: MCCET-3230. Timecode Burn-in added pulldown frame info when added to V5 or V6 track.

- Bug Number: MCCET-3306. In some instances, if the Effects Editor was open, Color Correction was not always added correctly, and the wrong clip was modified. 

ReadMe:  The ReadMe for this release is attached. 

How to obtain the Media Composer 2019.12 Update: 

1.  Customers who have an active support and upgrade plan will be notified of the availability of the 2019.12 via Avid Link and it will be available via Link, MyAvid and the Download Center.

2.  New perpetual and subscription Licenses purchased on or after Monday December 23, 2019 will also receive 2019.12.

Have agreat holiday!

Marianna

On a fresh install of Avid Media Composer 2019.12 on Mojave 10.14.6 When quitting a fresh new project made in 2019.12. I get Unexpectley Quit error window. I am not using any 3rd part Hardware I/O like Blackmagic. Just a Focusrite usb audio interface connected into speakers.

Thanks,

Leo

2019.12 issue - I can import media with alpha into bin, but cannot load into composer window.  Get error show below.  Alsocannot matchframe to any imported Media with alpha, same error.  Clips can be dragged into timeline, and function properly.  

Run Length Endcoded (RLE) clips do not load into the composer window, they generate error.  

Media Composer Ultimatte 2019.12

Just wanted to share that fair offer:

https://shop.avid.com/ccrz__ProductDetails?viewState=DetailView&sku=DYNA10021&utm_content=1573664549&utm_medium

Reinstate your Update & Support plan and get access to the latest version of Media Composer and all the incredible new features everyone is talking about. 

Available for all Media Composer v5 or higher perpetual licenses (non-EDU) not currently on an Update and Support Plan.

I am still on 2018.3 and won´t take the offer, because the 'new' features and the 'new' interface are just not worth the price for my daily job basis, I think...

What do you think?

Andre.

Using MC Ultimate 18.12.7,  just noticed this in CC mode.

It also happens in new user settings.

Any ideas?

Nigel

EDIT: Rebooted client iMac and all is now normal.
MC  crashed earlier when pointing source browser at Applications folder, so may have been some kind of corrupt site settings?

I customize my DEFAULT WORKSPACES: Edit, Effects, Color, Audio and save them with Save Current.  I also make a safety copy that I drag to Site Settings.  They'll work fine for a week or so, then suddenly the Composer window will move to my second monitor (which was unchecked in Windows/Host Panels but is now checked), same with Color, etc.

When I try to save/replace the Default Workspaces with the safety copies by dragging from Site Settings I get a message saying I can't replace Default Workspaces.  I understand having a "factory default" to fall back on, but why can't we drag and replace those four predefined Workspaces?

I have just installed 2019.12 on my iMac Pro under Mac 10.14.6. I restarted and now Avid will not open, it keeps crashing when it hits the 'AvidTitlerPlus.avx' plugin.

Tried several uininstalls and reistalls with no luck. I know it was stupid to do an update on New Years day but now wanting to go back to 1019.11 to see if that works. I tried to get into the download centre but it turns out my account for the download centre is an old one and does not allow me access to download 2019.11.

Any ideas what I can do to get it working either way?

Cheers

I exported an film project AAF from FCPX/Premiere/Resolve.

I have tried each of the above with varying processes involving third-party software.

I can get the RED files to relink but audio is just plain useless with AAF for me.

The audio from the shoot is named in shot/takes. I can see the actual WAV filename in the TapeID column.

I have tried everything and I still cant get the audio to relink.

Okay this one has been doggin me for days.

Started with an AAF imported from Resolve.

It does it as well with other AAF imports.

Its really annoying and makes me want to move to another NLE fast.

I am new to AMC and have been given a project from another editor. I will be making selects and rough outlines then delivering back to the lead editor.

I first installed 2018.12.1, but was informed that PhraseFind is broken and i would need to roll back to 2018.12. I did that and PhraseFind is now activated, BUT I am have a problem where it will not index the files. I contacted support and they gave me several solutions to try -

- Delete SearchData Folder and reopen, stop indexing, restart indexing,

- Create a new project, copy over bins and try from there

No luck so far. 

I have somehow managed to get it to index one interview. There are two .pat files in the PhoeneticData folder. Another note.. the one interview that does show results in PhraseFind was one I shot last week and imported. Does anyone know any solutions to Index the entire project so I can begin using PhraseFind from every interview?

p.p1 {margin: 0.0px 0.0px 2.0px 6.0px; line-height: 20.0px; font: 12.0px 'Helvetica Neue'; color: #000000; color: rgba(0, 0, 0, 0.85)}

[Case : 03666384]

I've had a problem on 2018.10 where I can't eject a media drive (once avid has quit) because macOS says an application is still using it. It seems that the process that is still using the drive is Avid Phonetic Indexer and it's usually red in the Activity Monitor. I can quit the process there and the drive ejects. But something is causing the phonetic indexer to get stuck. Is it suppsed to stop running when I quit avid? Could there be something that got corrupted in the phonetic index on that drive that is causing the problem? Looking for troubleshooting advice. For the record I have only used this particular drive with 2018.10 and no previous versions so this isn't necessarily a 2018.10 issue. I was running 2018.5 before this.

Hello! Long time forum lurker, first time poster. I usually find the answers I need browsing through these forums, but I haven't seen this one addressed specifically. 

PhraseFind has stopped indexing any AMA linked footage inside Media Composer (2018.12.3). I've been frustrated trying to goad the system by stopping/starting the index, doing things in different orders, trashing folders, waiting it out, etc. I tend not to import or transcode footage because of the volume and turnaround times, so AMA is my workflow of choice. However, as an experiment in my latest project - I took the time to separately link AND import the same clip. For the first time in a while, PhraseFind successfully indexed, but ONLY the imported file. I know this wasn't always the case. 

Any advice is welcome as I found PhraseFind to be very useful when it was functioning! Hoping it's simple user error on my part. 

Thanks!  ---Cory

Media Composer (2018.12.3) running on a 2017 iMac (Mojave 10.14.6). 

First one is an old one. AMA linking of a file that is deep within a folder structure results in a name of "/" - I suspect related to characters used in folder naming -  fixed by copying source file name from the bin column to the name column.

Second one relates to export settings. The drop down list seems to be one off - i.e. I have to select the setting below the one I want to get the correct export settings. (Haven't tried creating new user settings yet)

I reported this problem on a different thread, but it was MC 2019.11. Essentially, whether I create a rolling title, or try to modify an existing one, the Title Tool will not save the rolling title. I have created new user settings, tried it in different projects, manually reinstalled MC, etc. I can reproduce the problem in any project, including new projects with new user settings. I can also recreate the problem in MC 2019.11 and 2019.9. If I roll back to MC 2019.6, the problem is not there and Title Tool operates normally. It is just a simple text rolling credit. Here are the steps that I went through:

1.Create a rolling title.

2.1 page worth of lines – Saves as normal

3.More than 2 pages worth of lines in the rolling title, it does not save. Screen blinks, Media Composer icon from dock jumps up, Title Tool Edit window comes back. It does not close.

4.Using Save As allows you to “save” the title by going through the screen that allows you to name it and tell it where to go, but it does not save it there, and it does not save it to the bin. However, the title tool edit window sometimes closes. Other times, it doesn't. Whether it closes or not, it doesn't save.

5.If I use a rolling title created from 2019.6 (where everything works as normal), I can access it on the timeline in effects mode, select “edit title,” which brings up the title tool window, and I can edit it. Here is where it gets really weird. 

6.I have the same problem trying to save it. It does not save, and the title tool edit window just pops back up. I can do this multiple times with the same result. Using Save As sometimes does the same thing, and sometimes goes into the “save as” screen, allowing me to tell it what to call it and where to save it. When I select save, again it does not save it to the bin, it does not update it in the timeline, and it doesn’t show up anywhere. The original title is still represented on the timeline with not title saved to the bin. 

7.If I go back into effect mode and select “edit title,” it brings me to the title tool edit screen, but shows me the modified title. Obviously, it saved it somewhere, but it is not accessible and it does not show up in the bin or on the timeline. Only the original rolling title is there.

8.If I close Avid, then restart my system and go back into the project, the original title is still represented on the timeline and the new edited title does not show up in the bin, even with the set bin display set to display titles and effects. However, I can go into effect mode on the same rolling title and it shows the revised version in the edit title mode, but again I can’t get it to save either onto the timeline or into the bin.

9.Rolled back to 2019.11, new user settings, same problem.

10.Rolled back to 2019.9, new user settings, same problem.

11.Rolled back to 2019.6, new user settings, works as normal. Accessing the same test title roll that wouldn’t save, the timeline showed the original title, but effect mode/edit title showed the revised version created in 2019.12. However, a simple save updated the timeline, as normal, with the revised title and it was saved to the bin, as normal. The revised title now shows up on the timeline. Everything with the title tool is normal in 2019.6, but 2019.12, 2019.11 and 2019.9 all have this same bug.

iMac (Retina 5K, 27-inch, Late 2015)

Mac OS 10.14.6

MC 2019.12.0

32GB RAM

Hi there,

I've come to the end of working on a short shot at 4k. I've been editing in a 4k DCI Flat 3996x2160 1.85.1 project and have applied a 1.85 mask on the timeline. We used the extra head and foot room to create pans and reframe etc.

Anticipating that some festivals may want a file without black bars (is anamorphic the correct terminology here?), what is the best way to achieve this?

Many thanks

S