What would you recommend guys?  Have an older K2000 but as I'm doing a lot of UHD it may be good to get a more recent faster one?  Specs are a bit confusing as my K2000 is stillfully approved and listed. 

Dont want to spend too much for minimal video editing gain (as rigthtly/wrongly I just think these cards provide 2D video and dont computer game light/shade/3D CAD anything).

Have found a K4000 for a very good price - will I be twice as awsome with that ;)

Thanks for any advice.

Could somebody with Mac and PC workstations do me a favor and test this? Make a timeline on a PC. Drop an Avid Titler on some filler. Type something out. Then open that same sequence on a Mac workstation and let me know if it works. 

I have a timeline with a bunch of Avid titler filters on it then went to a Mac workstation to do an output and none of them were working. 

Thanks in advance for your help. 

MC 2018.12.3 on both workstations.  

This is for people who run MC on custom built computers, I will NEVER buy a qualified system, please do not reccomend or warn me of doing this.

I've been building my own computers and running Media Composer for about a decade now.  I get flawless performance, but lately ive been considering upgrading to a prosumer cpu such as a 6900k, 6950x, possibly Ryzen 1800x, or wait for future Skylake-X.

My current setup is intel 4790k @4.4ghz  32gb ram, asus z97 gryphon motherboard, nvidia 980ti. And running Media Composer 8.8.1, windows 10 home.

When I do a mixdown it looks like im getting 68% avg across 8 threads.  What average are you all getting?  Id be interested to know about kabylake 7700k, skylake 6700k, 6900k, 6950x, AMD Ryzen,  and other current cpus.

Im wondering if I built a computer with a 6950x @4ghz would Media Composer utilize all 10 cores/20 threads?  If so, that would be a substantial performance upgrade over these mainstream gaming cpu's.

Also im going to start paying close attention to how Media Composer uses all my cores while performing different tasks. Mixing down, rendering, exporting, importing, transcoding, etc.

Due to the discontinuation of Sorenson Squeeze by Sorenson, Avid can no longer offer Sorenson Squeeze either for purchase or as part of a Media Composer | Subscription or Production Pack bundle.

Customers who have purchased Sorenson Squeeze can continue to use it while the license is valid.

Customers who have purchased the Production Pack can continue to use Sorenson Squeeze while the license is still valid. They will not receive any software updates to Squeeze, however, and cannot receive support from Avid on issues related to Squeeze.

Customers who have a Media Composer subscription that includes Sorenson Squeeze can continue to use it until January 31st, or the next time they renew their subscription in 2019, whichever comes first, at which time it will be disabled (will cease to run) and will be removed from their Avid Master Accounts.

For further questions, please refer to this FAQ

FAQ:

What’s happening to Sorenson Squeeze?

Due to the discontinuation of Sorenson Squeeze by Sorenson, Avid can no longer offer Sorenson Squeeze either for purchase or as part of a Media Composer | Subscription or Production Pack bundle.

Customers who have purchased Sorenson Squeeze can continue to use it while the license is valid.

Customers who have purchased the Production Pack can continue to use Sorenson Squeeze while the license is still valid. They will not receive any software updates to Squeeze, however, and no support from Avid will be available on issues relating to Sorenson Squeeze.

Customers who have a Media Composer subscription that includes Sorenson Squeeze can continue to use it until January 31, 2019, or the next time they renew their subscription in 2019, whichever comes first, at which time it will be disabled (will cease to run) and will be removed from their Avid Master Accounts.

Why is this happening?

Earlier this year, Sorenson Media announced that Squeeze was no longer part of their portfolio and ceased all licensing, development and support of that product line. Avid is therefore no longer able to sell or support the product.

Can I still get help with issues?

Customers who require support for Squeeze should refer to the Sorenson Media website. Avid cannot provide any support for issues related to Squeeze.

When will I stop being able to use Squeeze as part of my Media Composer subscription?

Sorenson Squeeze installers will be removed from accounts on January 31st. Starting January 1st, the next time a subscription license is reactivated – either as part of an annual renewal, a monthly payment, or a monthly “call home,” – Squeeze will stop running as part of a subscription license.

What about an alternative software solution?

Avid will not be replacing Squeeze with an alternative software option.

Questions, let me know

Marianna

Good news! Media Composer 2018.12.5 is now available. This is a patch release, and is only available through the Download Center. You will not see it in your My Avid account or on Avid Link.

The Windows version of Media Composer v2018.12.5 is a patch release. You must have v2018.12.3 already installed. Then use the 2018.12.5 patch to update to this release.

Fixed in Media Composer v2018.12.5

The following has been fixed:

➤ Bug Number: MCCET-2999. You might have received an Exception error when deleting an asset from a bin.

Fixed in Media Composer v2018.12.4

The following have been fixed:

➤ Bug Number: MCDEV-10783. You might have received errors when trying to log into the MediaCentral Cloud UX server.

➤ Bug Number: MCCET-2822. In some instances, the .mxf extension was not appended using Send to Export, therefore “Auto Launch” could not open mxf files.

➤ Bug Number: MCCET-2927. Intermittently, saving bins resulted in Exception errors.

➤ Bug Number: MCCET-2902. In some instances, a video mixdown included the effects from an upper nested layer.

➤ Bug Number: MCCET-2897. After importing, certain WAV files may have had an incorrect start time.

Fixed in Media Composer v2018.12.4

2

➤ Bug Number: MCCET-2748. If a sequence with media from a P2 card was loaded into the Source or Record monitor, relinking to add an extra clip would take too long.

➤ Bug Number: MCCET-2867. In some instances, rendering some effects on linked H264 media resulted in mixed up frames.

➤ Bug Number: MCCET-2862. (Windows 10) The Audio Tool was not updating when scrubbing with CAPS lock enabled.

➤ Bug Number: MCCET-2937. In some instances, if you captured with a single track that was not A1, the capture would abort immediately.

➤ Bug Number: MCDEV-10869. Clicking the yellow bin lock icon maximized bins that were minimized.

➤ Bug Number: MCCET-2967. (Avid Artist DNxIO and DNxIQ) Audio meter levels were not displayed in the Audio tool when recording.

➤ Bug Number: MCCET-2952. The Audio Punch-In Tool did not remember the last bin selected.

➤ Bug Number: MCCET-2914. In some instances, when exporting JPG, if you changed the name of the export, the file may have been unusable.

➤ Bug Number: MCCET-2942. You could not perform an insert edit export of DNxHR HQX media.

➤ Bug Number: MCCET-2946. (Interplay) In some instances, Media Composer would crash during check-in of sequence.

➤ Bug Number: MCCET-2910. Importing a non-shared user profile created a duplicate and prevented the application from closing.

➤ Bug Number: MCCET-2913. The Property Merge window would inadvertently appear when checking in a clip for first time into Interplay.

➤ Bug Number: MCCET-2901. Media Composer would hang when playing back an Avid Titler+ title in the effect editor.

➤ Bug Number: MCCET-2729. You might not have received the correct find results when searching group clips in PhraseFind.

➤ Bug Number: MCCET-2931. After upgrading from Media Composer v2018.12.1 to v2018.12.2 or v2018.12.3, batch re-import of Matte Key clips was not working.

Fixed in Media Composer v2018.12.4

3

➤ Bug Number: MCCET-2878. The UHD video output is converted to HD when consolidating HD media in a UHD project.

➤ Bug Number: MCCET-2859. Switching camera angles in Multicam stopped playback if the group contained mixed frame rates.

➤ Bug Number: MCCET-2857. If you were working on a system using Chinese locale, you might have experienced consolidate and transcode audio issues.

➤ Bug Number: MCCET-2957. Insert Edit Export failed if only video tracks were selected.

➤ Bug Number: MCCET-2966. You might have been unable to import an EDL.

➤ Bug Number: MCCET-2915. The metadata might have been incorrect after importing an ALE.

➤ Bug Number: MCCET-2841. Saved presets did not always retain the last keyframe.

➤ Bug Number: MCCET-2805. The Raster Dimension column in a bin was incorrect for thin raster media.

➤ Bug Number: MCCET-2925. In some cases, after performing a render operation, the green dot remained in the Timeline on PNG clips including a Matte Key effect.

➤ Bug Number: MCCET-2930. You might have seen performance issues when editing a long AVC Long GOP 25 clip.

➤ Bug Number: MCCET-2973. Changes to Audio Reference Level settings changes were not properly reflected when you switched between Normal and Narrow Mixer View.

➤ Bug Number: MCCET-2960. (Mac v10.14.x) When linking to media on a shared network drive, the UNC path in the Drive column might have had the network user name in the path.

➤ Bug Number: MCCET-2732. When consolidating AVC Long GOP subclips created new master clips that were too long. A new check box has been added to the Consolidate/Transcode dialog

boxes. Select the “Re-encode AVC Long GOP media to ensure shortest subclip durations” option when you consolidating AVC Long GOP subclips.

➤ Bug Number: MCCET-2923. (Mac) You might have received “not authorized” errors when trying to use PhraseFind or ScriptSync.

➤ Bug Number: MCCET-2947. You might have received errors when trying to set target the Dynamic Relink settings in an SD 25i PAL project.

Fixed in Media Composer v2018.12.4

4

➤ Bug Number: MCCET-2936. If Dynamic Relink was enabled, imported DaVinci Resolve AAF media was offline.

Hello,

I have a very strange error that appeared after installing MC 2018.12.2.

The error is that you can not transcode video clips that have been AMA linked on a different computer than the one where you want to transcode. On the other PC, this error is shown as on bottom.

Interestingly, the case concerns only clips, which in our case come from cameras like GoPro or DJI OSMO.

All clips that come from Sony PMW-300 cameras and are recorded as XDCAM 422 50Mb do not show the problem described above.

Additionally:

- The duration of the clip is double on clips linked with GoPro and DJI OSMO

- When an error occurs, it is NOT POSSIBLE to transcode on the first PC (AMA Linked on the one where the clips have been), AMA LINK needs to be re-enabled

- When I want to view the clip on the second PC, which is there, the MEDIA OFFLINE in the PRV window has an image but no sound

Procedure:

- clips from the card are copied to the network share

- network share is visible on PC through Symbolic Links (aka Symlinks)

- after copying the clips are AMA Link in Composer

- clips are described and sorted

- Then on the second PC the same project and the same bins are opened (BINs are previously closed on the first PC) and

- the transcoded option of selected clips, which are AMA Linked on the Avid ISIS 5500 workspace, is run

and then an error occurs.

Specification:

1. Both PCs are HP Z440 Win 7, Intel (R) Processor Xeon (R) CPU E5-1660 v3, 32 GB RAM, NVIDIA Quadro K2200

2. Both PCs are Media Composer 2018.12.2

3. Avid ISIS 5500 Workspace

4. Network - Intel (R) PRO / 1000 PT Dual Port Server Adapter

5. The format of the project is HD 1080i50

6. The codec of the project is XDCAM 422 OPAtom

7. Source codec AVC Long-GOP High (HD1080p)

8. Automated AMA Plugin - Avid Generic

Information from the console:

18.12.2.51455

* Can not consolidate master clip with offline media.

Error on DirectQtDrawing: QPaintEvent was ignored for BARTEK TEST, rects: 2 (org: 0, 1 size: 1435, 20) (org: 1, 26 size: 1415, 547), due to suspension update events for this window.

Error on DirectQtDrawing: QPaintEvent was ignored for * EXPORT CONTROL, rects: 2 (org: 0, 1 size: 118, 20) (org: 1, 26 size: 117, 283), due to suspension update events for this window.

DIDWriter :: DoSDKHWEncodeForCapture - SDK HW encode disabled

Exception:

@ Wed May 15 15:01:52 2019

I am asking for help, because in previous versions of Media Composer, for example 2018.11, this problem did not occur.

So I'm finally taking the plunge and going to monthly subscrition because I will be editing some 4K projects. Can I keep my version 7.04 dongle license and just deactivate it and install the new subscription version? So I could atsome point go back to it.

Another option I might try would be to move the dongle V7.04 to another computer and put the new license on the other?

Thanks Greg

Getting a PGLUE IMPOLITE PORT NUMBER error when exporting. Haven't had this issue before with previous version of Avid. Running current version. Exporting 4k project. Footage was AMA. Have transcoded and run all sorts of ways to export including running mono channel of audio (based on issue in version 6). Any work arounds? Waiting for support call with Avid and needing this exported hours ago for client deadline.

Thanks!

Michael

We just upgraded all of our systems to W10 along with MC 2018.11 and we're randomly encountering weird UI issues. Wondering if others have seen this and found a solution.

Our systems are dual monitor, and without warning various regions of the UI will become unclickable with the mouse. The keyboard will still work and other regions of the UI will still work.

For example: the project window will be all the way on the left of the left monitor. Can double click to open a bin. The bin will open in the center region of the left monitor and nothing in the bin and the bin itself cannot be clicked on. Avid isn't locked up because I can still click on menus and I can still open other bins from the project window. If the bin opens elsewhere, say on the right monitor then it is clickable. But, when a bin has opened in the region of the interface that is unclickable we have no way of interacting with that bin. If the bin is half way in the unclickable region I can usually grab the bin and move it and then the whole bin is clickable. Close Avid and re-open fixes it for a while.

Have tried clean uninstall and re-install of the video drivers, have deleted the MCState file, but nothing seems to be a permanent fix. Anyone encounter this?

Hi,

Running Media Composer 2018.12.3 on HP Z820 with Interplay | Production

When we are linking to P2 cards from within the Source Browser we are consistently getting the following error:

Assertion failed: bAAFProcessorOK

File: s:\coresw\ame\src\ama\ama_manager.cpp, Line: 3082

It is possible to click continue but with a large number of clips it becomes tiresome.

Has anyone seen this error before? I have checked and have the latest version of the P2 plugin from Panasonic installed.

Thanks,

Jonathan

Hello,

I have a serious problem with the opening time of BINs and Sequences.

BIN can open up to 20 minutes.

The attempt to open the sequence is up to 15 minutes.

BINs are not so big, they are from a few to several sequences.

Sequences that open long are in very small BINs

(1 sequence)

From what I was able to find, I did it:

1. http://avid.force.com/pkb/articles/en_US/troubleshooting/Ways-to-speed-up-Media-Composer-bin-save-load-switching-between-applications-and-startup - nothing it helped

2. http://avid.force.com/pkb/articles/en_US/troubleshooting/en397171 - also without a positive result

3. https://forums.creativecow.net/docs/forums/post.php?forumid=345&postid=373&univpostid=373&pview=t - also without a positive result

4. Fresh installation of WIN 7 PRO on Z440 avid 2012.12.5 - without improvement

SPECIFICATIONS:

1. The problem began to occur at Z4 Avid 2012.12.3

2. Project data and media are on AVID ISIS 5500 workspace

3. Connected by the Intel (R) PRO / 1000 PT Dual Port Server Adapter

I have the project files archived and the drive ready. I tried copying the old project file, Avid 8, into the 2018.12.3. It's not showing up in Avid but does appear in the harddrive folder where the projects are stored. 

Any thoughts or workarounds?

Thanks!

I love Avid but I am starting to reach my limit. I am very fed up with how much I struggle to simply export my footage from avid media composer!

I shoot on GH4s and GH5s, 4K and 1080 H.264 .mov’s. Avid’s video column says: AVC Long-GOP High.

I link to the footage and edit with proxies.

The issues arise when I’m exporting the sequences linked to the masters. I usually export animation, DNxHR, but compression type doesn’t seem to have any part in the issue.

If I am linked with the Avid generic plug-in my colours are all wrong and clearly change when switching between quicktime and generic linking. The Quicktime linking is closest to what I see in camera. also with the generic linking I get random skipping of frames at the end of  some shots, it is very oticeable and throws of the edit completely!

But if I am linked with QT it is even worse, the export will have random flashes of comppletely green frames through out the whole export.

So far my only work around has been to transcode the QT linked sequence so the colours are right and when exporting the transcodes the other issues do not occur.

This is not good for me as I export a lot of projects, all the time with 1 hr plus runtimes! Transcoding it all just to export it is not a good workflow, it takes up so much space and time! And is adding rounds of compression or alteration I’d prefer to skip!

This can’t be acceptable from an editing program. I should be able to get my project out of the program with out such a plethera of issues and unsatifactory work arounds!!!!

Hello,

Does anyone have this going on? 

Everytime I insert a clip into my sequence avid says its "Loading media file information" with a progress bar that takes about 2 secs and then "relinking to media" progress bar. Does anyone know whats causing this? And how I can get it to not do this?

I noticed it only does this with clips that have 4K footage. 

I am using transcoded footage (DNxHRx) and the media is on an Internal hard drive. I am using PC and Avid 2018.10. My project settings are 23.976, 3240x1080

Thank you for your time!

Whenever I export a single frame (Windows Image NTSC) as a screenshot, it includes all the video tracks, even if some of the tracks are not selected.   For example, if I want to export a shot on V1 without overlaying graphics on V2, I have to temporarily delete V2 before exporting a screenshot of V1.  This is different from a video mixdown, where only the selected tracks are included in the mixdown.  Am I missing something or is this the way it is supposed to work?

I've come to accept that Media Composer is a little slow. It can't keep up with me. I'm a fast editor. But I always get ahead of my own keystrokes. I'll make an insert edit, and I have to wait anywhere between .5-2 seconds before the edit happens.

Does this happen for you? In Final Cut, Resolve, or Premiere, this is not an issue.

I wonder if it has to do with the project being hosted on shared storage. I'm using an Avid-certified computer. A Lenovo P710 with a Quaddro M4000. 

The footage is 1080p23.98. 

There is nothing terribly taxing about the work I'm doing. 

The project is also pretty small. 

Any thoughts on this? 

Hey everyone,

Anybody run across this error recently?  VDM3BobVideoOut::Setup:Unexpected state

Shows up in the source window as I'm logging clips, usually when shuttling video.  Effectively freezes MC and sometimes causes it to crash.  It's annoying as all get-out, and the only way to avoid the error is to restart avid with my Blackmagic Device disabled.  Of course, that makes it sort of hard to work with any efficiency...  Seems to run normally without my BM hardware connected.

I've experienced this running MC2018.10 and 2018.8, but not prior to those versions.  I ran 2018.3 for months without this issue.  I have reason to believe that this has something to do with my Blackmagic Mini Monitor and newer versions of MC, but as far as I know I'm running the Avid recommended BM drivers (most current 10.11.4, and previously I ran 2018.8 with BM 10.11.2 and experienced the same problem).  Now running on a clean install of Windows 10 Pro with dual GTX1070 cards and a newer GeForce driver.

Got any ideas what this could be caused by?

EDIT:

I got one more error just now, one I hadn't seen yet:

"Exception: Fatal Open I/O Error - Callback consistency check failure"

Just wanted to add that.

Any time I use pillarbox/letterbox in my frame flex settings to reformat media I'm getting a single pixel black vertical line along the left edge of picture. 

Current work around requires a slight blowup to our delivery master to pass QC. Has anyone else run into this issue?

Hey

having an issue, I can't seem to remove all the audio effects from my timeline without removing the audio itself. 

Usually I would open the effects editor, select everything right to left and press the remove effect, but in this verions its removing everything inc the audio.

I assume they have changed how you can do it, but I can't figure or find what I need to do in order to do it.

Regards

Every so often when closing MC, it gives an error message that it has encountered a problem and has stopped working.   I'll force MC to close with Windows Task Manager.  I don't lose any saved work, but it's annoying and there seems to be no cause & effect pattern dictating when and why this happens.