New AJA Unified Software v15.2 - Resolves benign crash-on-exit

June 11, 2019, 11:37 am

≫ Next: Settings not saving and other weird bugs

≪ Previous: Waveforms cripple my system

$

0

0

Aja has released a new driver and firmware package v15.2 which resolves benign crash-on-exit with MC.

Release Notes:   Please read the Win Release Notes for complete details. 

For best results when capturing using Avid Media Composer or AJA Control Room, set Ref In to Video In with AJA KONA, AJA Io products and Avid Artist DNxIV, DNxIP. Here as a reminder, this recommendation began with v14.3. 

Media Composer Specific Fixes: Listed below are the few fixes that directly impact Media Composer users.

-  Solved problem whereby after frame-stepping in Avid Media Composer, the following attempt to playback resulted  in frame skipping and/or repeated frames.

-  In conjunction with Avid, and working with their new release of Media Composer (2019.6), addressed some audio metering deficiencies whereby depending on the order of window selection/activity in Avid Media Composer, audio metering for Capture and Audio Punch-In was not available, despite audio being present. 

-  Fixed benign crash-on-exit with Avid Media Composer.  (<— this is a biggie)

 

---

Settings not saving and other weird bugs

February 9, 2018, 9:54 am

≫ Next: Background Bin Save is a disaster

≪ Previous: New AJA Unified Software v15.2 - Resolves benign crash-on-exit

$

0

0

I am presently running Avid Media Composer 8.8.1, but I should note that the following problems have occured on different workstations (all avid configuration approved), running different versions of media composer 8 (including the most current version), and also with different user settings. My user settings are stored locally on the internal drive and not shared across other systems. 

The first problem is simple to explain- my user settings don't always save. In fact, they almost never do. When I moved from Color Correction Mode back to Source/Record editing mode the windows don't move back to the saved position, forcing me to use a different key binding for a saved workspace instead. If I change the settings on my grid to include title safe, the next time I open Avid that setting is reset. The same goes for new keybindings, etc.  

Another, much stranger issue, which has persisted since MC 7, in every version: When I open my audio mixer tool, if I use the mouse to click on the meter level, to move it up or down, *occassionally* this will bug out the entire bin. By that, I mean that after clicking on the meter level, Avid will refuse to respond to any key commands and will not allow me to play back the sequence. It plays a single frame and then stops. No keyboard commands function after this. Not ctrl S for save, not playback, not mode changes- nothing. The keyboard works fine on Windows related things and in other programs.

Bizarrly, you can use the mouse to 'File- Save' the bin, then close the bin, then reopen the bin. And suddenly everything is back to normal. This does not occur 100% of the time. I'd peg it at about 1 in 20 or so times. But it happens enough over the years and through versions to cause me to become increasingly frustrated. I have rebuilt my settings from scratch several times over the years to try and stop this from occuring. But the bug contnues unabated. I have also attemtped to blow away MC state, site settings etc. It never fixes the issue. 

Background Bin Save is a disaster

January 12, 2019, 2:56 pm

≫ Next: runtime error 216

≪ Previous: Settings not saving and other weird bugs

$

0

0

Please do not use it. 

This feature saves our Bins with 0kb! Also in the Attic-Folder! Already the second workstation has got infacted by that problem. So we deactivated BackgroundBinSave in the Console. But hey what a disaster is this? It is not a real Background save. It is saving in an temporal bin and when it wants to write the original bin it can´t because the "lck" (Bin-lock) File! So this is not working at Windows. With Mac we had another Issue: When we rendered Sequences and saved them via Background BinSave and closed the Bin and opened the Bin on another Windows workstation,  then always the last ca. 50 effects of the sequence which has been rendered are not rendered / or the renderfiles have not been saved. Deactivate it in the Console, type "backgroundbinsave" and hit enter.

runtime error 216

June 13, 2019, 12:02 am

≫ Next: Lack of Attic saves 2018.12.3

≪ Previous: Background Bin Save is a disaster

$

0

0

Hi until I'm having issue not sure whats caused it but recently any time I'm say exporting a file and through the explorer window that avid opens, and I create a new folder to write the file to I get this error. (Hopefully in the attachment)

Not sure whats goiung on it's only an issue with Avid. Seems like permissions but they all look fine ?

 

Cheers

 

On version 8.5.3

 

Lack of Attic saves 2018.12.3

April 19, 2019, 5:56 am

≫ Next: Sony LUT applied by default

≪ Previous: runtime error 216

$

0

0

Avid bombed out so just relaunched expecting to lose 3-4 mins work.  Instead I lost 45 mins.  Checked the attic and there is a 45 min gap between saves in this instance - otherwise its the regular autosave every 3-4 mins as I have set.  Click image to enlarge and see the Attic file created times...

Anyione any ideas why - im really a bit grumpy about it having lost 45 mins on a National Holiday!

Sony LUT applied by default

June 13, 2019, 12:25 pm

≫ Next: XAVC vs DNxHR performance

≪ Previous: Lack of Attic saves 2018.12.3

$

0

0

MC is automatically applying a Sony LUT (SLog3-SC3.Cine to LC-709) to my AMA linked FS7 footage.  I prefer to use a slightly different "Type A" LUT.   Other than deleting the LUT from all the clips and then re-applying my preferred LUT, is there a way to prevent MC from automatically applying the LUT?  

XAVC vs DNxHR performance

June 13, 2019, 7:24 pm

≫ Next: Will it be possible to mix 2018.12.5 users with 2019.6?

≪ Previous: Sony LUT applied by default

$

0

0

After linkng XAVC-I footage via AMA, I tried two methods: 

1) Consoldiated the clips to my computer's hard drive, which remained XVAC-I.  

2) Transcoded the clips to my computer's hard drive as DNxHR HXQ. 

After color correcting, I notice the color is slightly richer with DNxHR HXQ, but the playback performance really suffers.  Any clips with even moderate motion will stutter in playback.   The consolidated XVAC-I clips play back without a hitch. 

Does it take a super powerful computer to play back DNxHR HXQ?

Will it be possible to mix 2018.12.5 users with 2019.6?

June 14, 2019, 4:22 am

≫ Next: Electronic Activation

≪ Previous: XAVC vs DNxHR performance

$

0

0

When 2019.6 is released, I will start with upgradeing for volunteers, but all of our users works with shared projects.

 

Can a 2019.6 user and a 2018.12.5 usre work with the same Avid Project on Nexis?

---

Electronic Activation

June 14, 2019, 7:04 pm

≫ Next: Adding Closed Captioning

≪ Previous: Will it be possible to mix 2018.12.5 users with 2019.6?

$

0

0

So ... I have a subscription ... every so often I seem to need to re-activate the software...it was much easier with a perpetual license... 

Tonight I have a critical export to do - and I'm being told to Electronically activate - but there seems to be no way of doing so ... The codes are all filled in ... there are various updates (mainly with plugins), which I don't need for this project ... 

Message as below:

License Status: Activated

License Type: Subscription

 

Have tried clearing cache, restarting machine.  Just not working.  Having to resort to using alternative software as I have to create a DVD by the morning ... 

What am I doing wrong?  I can't even open the software! Thanks so much

Charlie

Adding Closed Captioning

June 15, 2019, 6:16 am

≫ Next: Track a New Blue title in video clip

≪ Previous: Electronic Activation

$

0

0

Hey all,

Can anyone tell me the workflow for adding closed captions from a SRT file?

Thanks

Track a New Blue title in video clip

July 23, 2016, 10:00 am

≫ Next: Media Composer 2018.12.5 AVAILABLE 14 May 2019

≪ Previous: Adding Closed Captioning

$

0

0

I created a title with New blue titler and have it on V2. this clip is a panning shot of the parking lot on V1. I want the title to be revealed as the pan ends and stops at the title. 

I recreate this title in BCC 10 title studio I am trying to use this title with Mocha tracking by following this video
https://vimeo.com/141952226

Seems you use the tracking data from mocha using an effect/save it/ and apply it to match move effect.  I can not get this to work well. Has anyone tried this?

Media Composer 2018.12.5 AVAILABLE 14 May 2019

May 15, 2019, 4:33 am

≫ Next: Why no render?

≪ Previous: Track a New Blue title in video clip

$

0

0

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.

Why no render?

June 17, 2019, 11:14 am

≫ Next: Which one will perform best with MC? (rendering, export)

≪ Previous: Media Composer 2018.12.5 AVAILABLE 14 May 2019

$

0

0

Actually, I have a couple of questions. First, I've noticed a few times where I parked the cursor on the green dot effect, hit the render button but after render is done, the green dot is still lit up. Even several renders didn't fix it. Any ideas here?

Next, I'm a little confused about how to get the best quality export of my video. Is transcoding from DNxHD145 to DNxHD220 the same as re-importing all clips at the higher resolution? Since I need to clear this project out, what master formats would you recommend? I made a 1:1 copy which was 42gigs for a 27 minute film. What else should I make?

Thanks!

Which one will perform best with MC? (rendering, export)

June 17, 2019, 11:32 am

≫ Next: [BUG] Relink to File(s) not working

≪ Previous: Why no render?

$

0

0

I have z240's with 4.2 ghz i7 7700k, 4 core's, which is really fast in rendering and export.

 

Will a z2 with 3.7 ghz i7 8700k, 6 core's, perform better?

[BUG] Relink to File(s) not working

November 27, 2018, 7:30 am

≫ Next: Console issue

≪ Previous: Which one will perform best with MC? (rendering, export)

$

0

0

I noticed that some linked files in my projects could not be relinked with "Relink to File(s). Not all, but some.
I did some testing and found out that files that were linked with the MSP_MXF Plug-in could not be relinked ("Relink to File(s)" is greyed out) but files linked with the Quicktime Plug-in could be relinked without problems.

I could reproduce this on MC 2018.11 and 2018.10.

---

Console issue

June 18, 2019, 8:26 am

≫ Next: Exception: Structured Exception, ExceptionCode: 3221225477, ExceptionString: Access_Violation

≪ Previous: [BUG] Relink to File(s) not working

$

0

0

How can I fix this console error:

 

 

Avid OPAtom MSP Plug-In: BER encoded length is 4. For maximum compatibility with MXF files created by the AAF Toolkit it should be 9

 

also I am receiving a MSMRescan() took 2.29s

not sure it's related

Exception: Structured Exception, ExceptionCode: 3221225477, ExceptionString: Access_Violation

September 12, 2013, 4:24 am

≫ Next: Avid site in Chinese upon login

≪ Previous: Console issue

$

0

0

Exception: Structured Exception, ExceptionCode: 3221225477, ExceptionString: Access_Violation

 

I'm receiving this message upon loading Media Composer 7.0.2 via Editshare. When I load it from the desktop icon it works fine, however via Editshare when it gets to 'Initializing Import/Export' the error appears. I can only click ok & it dumps me back to the desktop. This has only occured since I upgraded to 7.0.2 this morning. I have uninstalled/reinstalled Editshare to no avail, unistalled/reinstalled MC 7.0.2, and even downgraded again to 7, all with no success. The message still appears.

 

Anyone have any thoughts?

 

Thanks

Stephen

Avid site in Chinese upon login

June 18, 2019, 10:05 am

≫ Next: MC and scarlett 2i2 - drivers problem?

≪ Previous: Exception: Structured Exception, ExceptionCode: 3221225477, ExceptionString: Access_Violation

$

0

0

Is anyone else seeing the Avid website in Chinese when you log into your account? 

MC and scarlett 2i2 - drivers problem?

November 3, 2015, 12:09 pm

≫ Next: Frameflex - why cant it work like other effects?

≪ Previous: Avid site in Chinese upon login

$

0

0

Hello guys, new here, long post, i just cant find a solution to this and it´s making me crazy, i come from Premiere CC and making the transition to MC.
When i first installed all worked ok, but then i needed to do a driver update on my system, a full drivers update. After that, i have this problem: when i open MC and hit play anywhere, the play doesnt start and the audio meters stay frozen. If i disconnect and reconnect my audio interface and hit play it works like it should. If i change to any other window (play audio or not) and then come back to MC, the interface make noise like it was connected again, and same simptom, no playback. I then disconnect and reconnect the interface again, and works.
I unistalled and reinstalled the focusrite drivers, same with MC, added a generic deck, deleted it, check sound configurations, check audio configurations, and cant seem to find the problem.
When MC is reproducing audio sometimes it crackels, and is not with the best quality.

My system config is:
*windows 7 64 bits sp1 updated
*Toshiba qosmio x875 laptop (i7 - 12 gb ram - 2x500 gb 7200 rpm - nVidia gtx670m)
*focusrite scarlett 2i2 audio interface
*any other audio disabled from device admin
*Premiere CC and nuendo 4 works ok with the interface, no problems there
*This laptos doesnt have 1394, only usb devices connected are mouse and audio interface

One thing that i encountered, is that if i left MC playing video/audio, then switch to another window, then come back to MC, the audio continues to work and the problem dont happen.

Any ideas whitout restoring windows to an old point? If is the only option i suppose i can do that, but i prefer not.

Frameflex - why cant it work like other effects?

June 19, 2019, 6:29 am

≫ Next: Hagrid Error when trying to capture from Tape

≪ Previous: MC and scarlett 2i2 - drivers problem?

$

0

0

I have a long timeline of many clips and need to reuse the same Frameflex effects on many of them - LS/MLS/MS reframes & some gentle push ins. Howebver I cant drag the effect to a bin like I can all other effects.  Also copying values from an effect editor keyframe and trying to paste it into another clip doesnt work properly - it doesnt stick (workaround is to change one value manually, click the timeline TC track, then it sticks).

 

Also the 'lock aspect' button does not work consistently - you can end up with different values there.

 

I'm on 2018.12.3 and super stable at the moment (so leaving well alone) - but has this been addressed at all guys - not missing anything?