Probably will need support for this but does anyone have any ideas behind these issues?

Its my tried and tested workflow on XAVC UHD and 50P media - been using it years really.  On Latest version Avid Symphony its crash city though.  Doing a full re-install now...

It crashes all the time and especially during a render.  Green screens come up and flicker as you edit. 

Here are screenshots of my symptoms and if anyone has any idea I'd appreciate it.  Its nothing trick and no workflow I havent been using for 2yrs plus :(

Can anyone who uses Frameflex and Symphony confirm they too get a green screen in the sourcve viewer if they try to adjust a Frameflex with a Symphony colour correct active too?

Full of green eyed monsterly yours!

Hi Guys,

I have been working with avid for over 20 years now in post production house in london. I have now decided to get a system of my own up and running. I have runa  trial version of 8.4.4 which i had floating around and worked fine. I decided to purchase a years subscription and found i could only use the new versio 2018.12.3. Fine, i thought, will be nice to use a new updated version.

Not so! i cant even scrub through audio without it sticking on the timeline. When you play any video it jumps and stops randomly. Its all very strange. Thing is, i now cant use my licience to roll back to an earlier version as i dont have a 'Perpetual' licience, apparently!

My system details are below. Whilst i admit they are not from the offical workstation supplier list (hp, dell etc.) , i think you can see that the spec is more than suffienct. So whats going on? I have never had this problem even using an older version on laptops  connected to a unity system!!

Any advice would be much appreciated.

SYSTEM: Intel i7-8700@3.70ghz , Asus Z370-G Motherboard ,Corsair 64GB 3000mhz RAM, QUADRO P4000 GFX CARD. 1TB solid state media drive. 2x AOC 23inch Widescreen Monitors. Water cooled system.

Thanks!!

PHIL

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.

Hi,

there's a short film edited in MC (camera footage AMA linked and transcoded to DNxHD36) which soon goes to a coloring facility. They will get an AAF and the original camera files, but is there a way to give them only the files which are involved in the final timeline?

Thanks.

Been having this past few days - hit stop and yet audio keeps repeating in a loop over and over again and you have to repeatedly hit stop and play a few more times to get it to shut up.  It loops maybe the last couple of frames of audio.

Anyone know what it is, what it is, what it is, what it is , what it is?!!!

I've have been asked recently on numerous occasions at what bit depth do Media Composer and Symphony process color correction.

I've heard all sorts of answers, like 12-bit, 16-bit integer, 32-bit float. Does anyone know for sure? Thanks so much.

Antivirus essential from my Synology NAS has quarantined "SetSecDescBG.exe" and "SetSecDMF.exe" from the 2018.12.3 installation folders (unzipped Avid download), threat = Win.Trojan.Refroso-12582: I guess/hope these are just false positives...?

I have ran into this issue 3 times now and wanted to post this to see if anyone else has seen this before. I have to master my sequences in 1080i for the networks. I have an original sequence offlined in 720p from linked xdcam 35mb footage. These are simple 2 channel two microphone interviews. The example is as follows. If I have a sequence that has both mics on channels one and two respectivly and I lift out just a portion of one of the audio tracks, when I go to my final sequence conversion to 1080i and AVID makes a new sequence out of the 720P footage the audio sounds like it is off. I have tried to slip the track that I lifted just a protion of the audio our 1 frame forwards or backwards and it gets worse. It's almost as if the audio track that I have lifted a portion out of is off by half a frame. I am running 2018.12.3 of MC.

Richard Riley

Madstache, Inc.

I find it very frustrating that you can drop a marker on a clip, cut that clip in, and that marker will show up in your timeline. However, if you do the same thing with a spanned marker, nothing shows up--not even the in-point of the spanned marker. 

This seems like an inconsistency with the feature. 

The span of the spanned markers should show up in a sequence on the clips the same way they show up in the source monitor. 

Further, when they show up on the clips, they should also be listed in the Marker window.

+1 if you agree

Everytime I try to enter full screen playback both monitors go white and Media Composer goes unresponsive. Have to end task and re-launch. Full screen playback used to work with version 7.0.4 and an earlier version of 8 (I believe 8.4 but I'm not sure).

Has anyone else run into this issue and found a workaround?

Have tried:

-NVidia drivers 340.84 / 353.82 (Windows 10 only, failed to load) / 385.08

-NVidia control panel solution as listed in thread http://community.avid.com/forums/t/183957.aspx

-Enabling Windows Desktop Composition http://avid.force.com/pkb/articles/en_US/How_To/Enable-Desktop-Composition-in-Windows

-Switching the playback monitor between the main (Displayport connection) and the 2nd (DVI connection)

System:

HP Z840

Windows 7 SP1

Quadro K4200

Media Compser 8.10

Dual monitor 1920x1200 (1-DVI, 1-Display port)

I’ve been very happy back on Avid (2818.12.3), using AMA linking to replace Premiere Pro workflow for fast turnaround where sources are typically Sony F5 and Sony A7s files from a variety of shooters.

This week the A7sii files would not link in Source Browser, or if Alt-dragged to bins. Pretty sure I’ve had media from the mk2 before.

Is there some recording mode that the plug-ins don’t work for?

I tried transcoding, to DNx MXF / ProRes mov, in EditReady but neither of those would link either. Ended up using Resolve to get DNX MXF OPATOM files but would like to identify what is causing the non linkage.

I feel like I’ve reported this before... TL;dr - refreshing groups doesn’t refresh currently switched angle.

Ive been using the new grouping features (2018.12.3) extensively, with AMA linked files, and they work well for the most part.

This week I got the audio files transferred to me straight after shoot while the camera files were being hand carried back.

So I built a 4 camera sync map with the audio files & 4 dummy video clips and ‘created group’

Cut the group into a timeline, with ‘C4 dummy’ as the angle, and cut for audio content.

Camera files arrived, edited group, overwrote 4x dummy clips, updated group and right clicked on edited sequence and ‘refreshed groups’

C4 dummy clip remained the source on the timeline. I could right click and choose from the 3 other cameras but C4 was the dummy clip.

Match frame brings up correct group, with correct C4, so had to manually overwrite the sequence clip by clip.

Seems like this might be a safety ‘feature’ in that the sequence current clips can’t be changed with the refresh, but this is wrong in my opinion.

This is on a Mac running high Sierra, but I suspect PC will be the same.

(Edit: http://community.avid.com/forums/t/196578.aspx is last time I tried this)

 Media Composer 2018.12.3 – Launching 4.2.19 @ 12:00 Noon

Avid is releasing Media Composer 2018.12.3 today, Tuesday, April 2nd, 2019 @ 12 PM EDT to address several issues.   

Location at Launch: Updates to Media Composer (subscription and perpetual), and Media Composer | Ultimate will be released at the same time, and will be made available from Avid Master Accounts (MyAvid), Avid Link, and the Avid Download Center (login and password required).

What is fixed:  The issues Media Composer 2018.12.3 addresses are:

- Bug Number: MCCET-2892. In some instances, playback would stop after adding an Audio Mark IN/OUT. 

- Bug Number: MCDEV-10686. Clicking on the checkbox for “Enable Mask Margin” or “Include Inactive Audio Tracks” in the AAF export dialog did not enable the options. 

- Bug Number: MCCET-2772. Clips may not have updated properly if you batch imported with Dynamic Relink enabled. 

- Bug Number: MCCET-2895. On some systems, the memory usage would increase until the editing application became sluggish.  

Limitations in this release:

- Bug Number: MCDEV-8641. (AMD Graphics). Systems with AMD graphics cards might display tearing when performing Full Screen playback. 

- Bug Number: MCDEV-9460. Windows 7 systems with Nvidia Maxwell or Nvidia Pascal cards might experience playback issues that could result in “Play Consumer timeout” errors. Workaround: Select “Disable GPU Effects” in the Render Settings dialog box. 

- Bug Number: MCDEV-9269. (Media Composer | Cloud) After performing a remote download operation on a sequence containing AVC-I 100 remote media, the downloaded media appears as XAVC-I 100. Workaround: Download the entire master clips. 

- Bug Number: MCDEV-9011. Intermittently, when working with the XDCAM Nablet Plug-in, you might see “Failed to get the sample position from the AMA Plug-in” errors if you have waveforms enabled in the Timeline. 

- Bug Number: COGS-2560. While working in the Script Window, text operations (cut/copy/paste/delete/editing) can only be done in edit mode. See “Editing a Script” in the Help. 

- Bug Number: MCDEV-5650. When working with Panasonic LongG media, you might receive an “SFPlayConsumer Timeout” error if audio waveforms are enabled. Workaround: Turn off audio waveforms. 

- Bug Number: MCDEV-5385. MultiCam editing with Panasonic LongG media is not supported 
with this release. 

ReadMe: The “ReadMe” document for this release of Media Composer 2018.12.3 has been uploaded to the Knowledge Base Media Composer 2018 Documentation Page at launch.

Qualified OS: 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). 

How to obtain Media Composer 2018.12.3 Update:  Listed below are the ways to obtain the new software.

1. Customers who have already installed the 2018.12.x version of Media Composer will be notified of the availability of the upgrade to 2018.12.3 via Avid Link. 
2. Customers on current Update & Support plans can also download the Media Composer 2018.12.3 update either from their MyAvid Account or the Avid Download Center (login and password required).

Location at Launch: Updates to Media Composer (subscription and perpetual) will be released on the Avid Download Center (login and password required) only.

Installer/Patch:  Installing the Editing Application:  The Windows version of Media Composer v2018.12.4 is a patch release. You must have v2018.12.3 already installed. Then use the 2018.12.4 patch to update to this release. 

What is fixed:  The issues Media Composer 2018.12.4 addresses are:

-  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.

-  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.

-  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.

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

Where did they move the command for freeze frame?

Hi Guru's,

I could use some help from a few members in the community to test if they can reproduce an issue I encountered today with MC 2018.12.3. and dynamic relink. It might be that the issue only occurs in an interplay environment but I'm currently not able to test this on a standalone non interplay connected 2018.12.3 system. I hope to do so in the coming days.

What I would like to ask, especially those in an interplay environment, is if anyone of you can do a classic import of 3 or 4 different audio files from the same location and play those 3 or 4 master clips and confirm that all 3,4 different clips are playing normally. Now enable dynamic relink and play those 4 clips again. Do all 3,4 master clips all of a sudden play the same audio file?

At the site where we see this odd relink behavior of 2018.12.3 (it probably wrongly assigns the same source mob id to all clips) MC 2018.8 works as expected.

Thanks in advance.

Jeroen 

Good morning. I am using a HyperDeck Studio Mini and have set it's codec to DNxHD 145 mxf. I link to the clip with source browser and the4 clip shows in my bin. When I try to play it I get: VDM3_VideoInputCvtr::ExecuteRequest: Unexpected state. and the clip does not play. I tried to consolidate which seemed to work but it still gave the same error.

I made a recording setting the HyperDeck codec to DNxHD 145 QT and all seems to work.

I'd prefer to stay in MXF if possible.

BTW, I tried the procedure of disconnecting and powering down the Nitris and computer and restarting...no difference.

Can I activate Dolby AC-3  / mts files / with MC 2018.12.1 or shoud I transcode consumer *mts files ?

Hi. After each edit I make on the timeline, the machine 'hangs' for around a second and a half - blue circle - before I can hit play or do anything else. Usual stuff of turning off all clip colours other than source, (inc offline colour), turning off dynamic relink, switching playlength to 1 and closing all bins with sequences so only one bin, one sequence is active. 

Nothing helps. 

However. I've just spotted in the console that it keeps brining up: 

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

So, I entered showbptime into the console to see what was going on - and it seems that the culprit is:

RTPlayerGraph Pipes took 1543 milliseconds to build

Awesome. 

Now.. what the hell is it, and how do I speed it up??

I hope someone can help...

John

(it's a z820 workstation with 32Gb ram, running 2018.5)

Just completed a presentation where I needed to do some cleanup and make the presentation succinct had about 70 fluid morph effects on the video portion, which was keyed.  I had several attempts using render-all, which crashed Avid every time.  I went into settings/render and disabled GPU Effects and all is fine now.  I think this has been a problem for some time but just wondering will we at some point be able to use the GPU to render effects in Avid?  The video cards are getting better and cheaper; I use my 1080 FTW in Resolve which has more than doubled my render times.

Thanks