Hi everyone.

Since upgrading to MC8, I'm having ongoing struggles with transcoding AMA linked AVCHD footage shot from my Sony NEX-FS100.

After a little research I thought perhaps the problem was that I don't have the correct AMA plugin loaded.  However I was under the impression that the correct codec was included with the MC software and not needed to be added separately.

The simple workflow is that I Copy the "Private" folder to hard drive.  AMA link it from the input>source browser. Then transcode.  But on some (not all), I'm getting the dreaded "exception: std::exception, what: AVCHD Reader : 8000ffff" error message.

Looking at the AMA files in a bin, it says it's using the "AVCHD MVP plug-in".  Any thoughts?

I could re-wrap them in EditReady, but that's kind of a pain.

P.S. the ama clip plays in the source window.  But won't transcode.

Thanks,

Brad

I have an old student version of Avid Media Composer which is at version 7 Interplay edition. Its complainting that my computer doesn't the minimum  Ram of 4G when I have 12G installed. Could someone advise me the best way to update or patch it?   

Any mxf file i link to, the pix is fine but the sound loads in a few seconds on head of clip and stops. The next clip does the same thing. Even mxf files that i have been using and transcoded allready in project, If i go back to the original clip that use to work on 2018.9 can't be brought in with 2018.10. You can see the waveform in the picture attached, it stops.

Any thoughts?

thanks

Hi. I need a little help.

My MC licence won't Activate.

Error message:

Activation failed: 0 success

License is annual subscription. Renewing 11/1/19.

(New problem .. was fine yesterday)

Thanks in advance!

Hi all,

I was working on a client's MC 6.5 station yesterday, and titles don't show in the monitor when parked. They only show during playback. The same thing happens when I park on a still with Pan and Zoom applied. On playback, the effect shows properly. When I park on a frame, I see just the underlying still as if the effect is doing nothing.

I tried changing the video display quality and restarting Avid, but no change. Any ideas?

Thanks,

Vito

I have a 12;20 720p sequence that I had to export to h264 QT and took more than 4 hours to complete. This, btw, is not unique to this clip, or project. I've had :30 clips take 30 minutes to export. Whats the deal?

First, the basics: 2014 Mac Pro, 2.7 GHz 12-Core Intel Xeon E5, 32 GB 1867 MHz DDR3, OS 10.9.5, MC 8.3.0

The Sequence is mixed codecs and resolutions, but all have been transcoded to 720p/59.94/DVCPro HD MXF. Output is set to Quicktime Movie/ H264/ Custom/ Best Quality (multipass) 1280x720 Video and Audio (mixed to stereo 1&2)

So, why does the export take so long? 4+ hours for a 12 minute clip seems excessive, doesn't it? Should I be transcoding to a different codec before exporting? Help me Avid Wan Kenobi, you're my only hope!

Hello,

I just wanted to get some feedback, maybe tips on how to build compositions from photos and graphics inside Avid, without using other programs except for Photoshop maybe. It is quite surprising that the program, called a composer, does not contain built-in tools for comfortable working with photocompositions. The Pan & Zoom tool does not allow to crop, mask photos and overlay them in different modes on the video. I found for myself a way out in using a third-party plug-in from Boris, which for some reason dubbed AvidFX. It has not been updated for a long time and, generally speaking, it is not very convenient to use. This is especially true of complex trajectories of movement on the photo, which quickly turn into painful attempts to achieve smoothness. I recently tried the original Boris RED 5.6 plugin. As it turned out, it often allows you to watch real-time previews with reduced quality. But unfortunately, he was unstable, often crashes with the host and my attempts to communicate with support about his correct work with Quadro GPU did not work. So, what could be the modern way to work with Avid photos inside, without using After Effects. I heard there is a connector for Fusion, but I have not yet managed to get close to this program.

Thanks for any advice

Hi All,

I have to output my project to a local broadcast in Bangkok and they require the delivery in XDCAM HD 50 422 interlace in MOV not MXF. I've searching all over the google and haven't find any real answer. I hope someone here would know the answer. Any help and guidance would be so appreciated.

Thanks in advance,

Smith Timsawat

p.p1 {margin: 0.0px 0.0px 10.0px 0.0px; line-height: 12.0px; font: 10.0px Verdana; color: #000000} span.s1 {font-kerning: none}

Hi All,

We have been running into a consistent playback issue with MC 2018.3 (as well all versions up to 2018.8) on Mac OS High Sierra (10.13.6). We did not have this issue on MC 2018.3 (as well all versions up to 2018.8) on Sierra (10.12.6). 

Whenever an editor is in trim mode then clicks on the timeline to exit trim mode and hits play, the video will play but the audio stalls out. This creates a looping audio effect coming out the speakers. Avid plays the same ~1-2 sec audio bite while the video plays normally. Only when the editor pauses, then resumes playback will MC stop looping audio and return to normal playback for both audio and video. The aformentioned actions usually happen within a matter of seconds as the editors are moving very quickly and MC seems to not be able to disntinguish between loop playback in trim mode vs. exiting trim mode and then resuming normal playback. 

I should also mention we've tested several versions of AJA drivers as the systems are using LHi cards for output. No difference. Even when turning of the AJA card, issue still persists

Anyone else run into this issue? 

Good day everyone. I just tried my hands on the Sony Alpha 7 III and I was trying to AMA into MC but it says no clips found so I guess there is no AMA plugin for the A7III. If so, what's the workaround to get these clips to MC for edit. Thanks

I just purchased a Sony AX53 and am testing it out. I don't seem to be able to import the files, and notice earlier threads about the Sony format being incompatible with Avid. Is this still a no-go or should I be able to import without going through an extra step? If not I will take the camera back and wait until Sony and Avid are singing the same tune.

Hi,

I experimented a wreck with my external harddisk. All the material vanished. Luckily I have all the original files from camera left. I also have sequence recovered from Attic. But my problem is:
I have a sequence MediaOffline. When I decompose the sequence I have all the clips separately visible at the bin. But when I try to re-import them Avid needs me to point every single clip separately in re-import. My clips were originally transcoded from AVC-INTRA100 to DNXHD120. So the offline clips have extension .new01.

Is there any way that I could have all the clips re-imported without have to point every single clip separately to Avid?

Many thanks,

JaMa

I always disable updates when installing windows.

When I was using 1703 ASDT would fix all my windows settings.

But on win 1803 i hit fix, and it can't seem to fix much.  It's stuck on security center...

Can anyone chime in on this? thx

When one posts error messages here and Avid does not fix bug introduced in 2018.9 it sure looks like it's time to move to Resolve. Not being able to publish a Sequence is about as fatal an appliation bug as one can have.

And, what's with new undocumented install option tha seems to require quitting the Application Manager.

And, what do our Moderators do? Nothing! 2018.10 has been out since last week. Nothing posted here! Do they ever work on the bugs posted here? Nope.

SO SAD!

Hi 

If I zoom way in, the blue playhead is like double with 1 frame apart..there's a right side slightly dimmer than the left side... Not sure the reason for this, in the first place. Anyone know why it is that way.. and the benefit? it's definetely by desgn

if I then make an out point at a cut, I have to use the "right" side of the playhead, in order to have it be excast at the cut. If I then make an add edit at that chosen out point, the add edit chooses the "left" side of the playhead, so that the add edit point is 1 frame before the out point...

what's the genious about this? is there a setting that I dont know off. it's crazy annoying.

Best Ulrich     

Importing xavcs 4k into MC 8.5.2

So --- who is going to be in LA Next Tuesday 11/6/18?

I am and woud love to meet many of you.

ping me if you are interested in a get together.

Marianna

Avid is pleased to announce the October release of Media Composer 2018 which is available as of today, October 24th, 2018 at 12:00 PM EST.  

Location: This release is available from Avid Master Accounts, Application Manager, and the Avid Download Center (login and password required).

What's New file is attached. ReadMe file is HERE.

Operating System Update: macOS Mojave (10.14) is now supported on Media Composer 2018.10.

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

Macintosh v10.11.6, 10.12.6, 10.13.6, 10.14  

To learn more about compatible versions visit http://www.alwaysediting.com/avid-mc-versions.html 

Manual approval of loading Kernel Extensions (KEXTs): With the release of Mac OS v10.13.x (High Sierra) and 10.14(Mojave), Apple requires manual approval of loading Kernel Extensions (KEXTs). (For example: Avid Nitris DX, BlackMagic, and AJA IO devices install Kernel Extensions.) At installation time, you should get a dialog saying that the KEXT was not loaded. You must go the “Security & Privacy” system preference and manually approve the KEXT. Keep the Security & Privacy pane open after you install the I/O device drivers so that you will see the notice that the driver has been blocked and press the “allow” button within 30 minutes of installing or the driver will be permanently blocked.

Application Installers:  With this release of 2018.10 (as with 2018.9), you have a single installer for Media Composer and Media Composer | First. The option to run as Media Composer | First is now include in the Avid Media Composer Activation window.

What’s New:  The following are new features in 2018.10

• Mac OS Support - Updated list of supported Operating Systems. 
• AVC-LongG - Additional AVC-LongG formats are supported with this release.
• Color Management LUT fix - The BT.2100 color conversions between PQ 2020 and HLG 2020 are made according BT.2390 specifications (at 1000 nits).
• Additional Color Space Presets - More color space presets are available inProgressive HD projects.

What’s Fixed: The following have been fixed in 2018.10: 

- Bug Number: MCCET-2605. You might have seen a BSOD (Windows crash) after launching the editing application in a Media Composer | Cloud VM environment.

- Bug Number: MCCET-2586. Performing a Shift + render In-to-Out behaved differently if you performed it a second time.

- Bug Number: MCCET-2664. Exported audio set to Mono might have played back 3dB lower than the original sequence.

- Bug Number: MCCET-2691. (Windows 7) If you deselected “Re-encode for XDCAM” in the Transfer Settings, creating a new project with the same user would select the “Re-encode for XDCAM” option.

- Bug Number: MCCET-2694. When logged into Production Management Services, you might have received a “structured Exception” error when exiting the bin Fast Menu. 

- Bug Number: MCCET-2672. In some instances, Media Creation settings did not remain the same after closing and opening the project.

- Bug Number: MCCET-2668. Send to Playback might have failed if your sequence contained audio with clip pan and a rendered audio dissolve.

- Bug Number: MCCET-2454. In some instances, transcoding 10bit to 8bit introduced vertical banding on solid color.

- Bug Number: MCCET-2292. Audio might have been out of sync and you might have seen audio underruns when linking Apple Prores 422 using the QuickTime plugin.

- Bug Number: MCCET-2619. When splitting a 5.1 audio track into mono tracks in the sequence the tracks were always arranged in the ProTools order, no matter what the Mix Mode Selection in the Audio Mixer was set to.

- Bug Number: MCCET-2638. The “NTSC Has Setup” option did not appear in the General Settings when a Nitris DX was connected.

- Bug Number: MCCET-2482. Exporting an H.264 sequence with stereo did not export as stereo.

- Bug Number: MCCET-2648. You might have received an “Exception: Tmf export only supports Long GOP” error when performing a Send To Playback with AVC Long GOP that has an I-frame at the beginning of the sequence.

- Bug Number: MCCET-2588. If your Tape ID contained spaces, the editing application would crash if you performed a Send To Playback.

- Bug Number: MCCET-2651. In some instances,a .transfer sequence with Long GOP format generated during the Send to Playback process, did not show as rendered.

- Bug Number: MCCET-2609. Performing an AMA File Export of MXF OP1a using Avid Media Processor set to Stereo Mix, exported as two separate mono tracks.

- Bug Number: MCCET-2639. If you closed and reopened a sequence multiple times, the Timewarp effect lost its render and the output setting changed to default (Interlaced).

- Bug Number: MCCET-2581. In some instances, you could not relink back to media that was linked with the Avid Generic plug-in.

- Bug Number: COGS-4963. (Live Timeline) In some instances, you could not scroll while performing playback in the Timeline.

- Bug Number: COGS-4939. (Live Timeline) You could not add markers on stereo audio in the Source Monitor during playback.

- Bug Number: COGS-4897. (Live Timeline) Loading a new clip into the Source Monitor by performing a drag and drop operation did not stop play and load the clip.

- Bug Number: COGS-4870. (Live Timeline) Pressing Ctrl + / did not zoom to show the entire sequence during playback.

- Bug Number: COGS-4862. (Live Timeline) When working in the Audio Mixer you could not enable/disable tracks during playback.

- Bug Number: COGS-4860. (Live Timeline) Clicking on Source Browser contents was stopping playback.

- Bug Number: MCCET-2599. The editing application became slow after loading a large sequence into the Source/Record monitor.

- Bug Number: MCCET-2601. The Trim to Fill (Timewarp) effect did not work on clips with a spatial adapter.

- Bug Number: MCCET-2646. You would receive an “Invalid File Name” error when transcoding a linked WAV file that contained two consecutive dots in the original file name.

- Bug Number: MCCET-2611. After sorting a bin by double clicking on a column, selecting an item in the bin resulted in the item being deselected.

- Bug Number: MCCET-2569. In some instances, the thumbnail displayed on the Frame column in the bin appear as Media Offline when importing a matte key.

- Bug Number: MCCET-2118. (Mac) Files that include “ ” in the name could not be transcoded and resulted in a “failed to import” error when checked out on a Windows system.

- Bug Number: MCCET-2590. When returning to the Find window to perform a repeat custom sift, the Custom Sift text field was not highlighted.

- Bug Number: MCCET-2653. You might have received a “Cannot be exported” error when performing an export to XDCAM OP1A of a “Capture in progress” clip.

- Bug Number: MCCET-2600. Airspeed MP2 low res proxy waveforms did not draw on the Timeline.

- Bug Number: MCCET-2254. A green/pink gradient might appear on some images captured from a Sony HDR FX1000E device.

- Bug Number: MCCET-2624. (Windows 10) You might have received a “FILE_OTHER” error when linking a P2 folder that contained a multibyte name on a shared workspace.

- Bug Number: MCCET-2520. If you had linked h.264 media containing AAC sound and then exported that media to h.264, the editing application would hang.

- Bug Number: MCCET-2627. (Mac) If you had Boris FX Final Effects Complete installed, you may have had problems with Open I/O devices.

- Bug Number: MCDEV-9676. Intermittently, the blue bar in the Source and Record monitors did not move.

- Bug Number: MCDEV-9781. You might have seen the following issues if Run Length Encoded is enabled:
“Core Consistency Check Failure” errors when recreating animated Marquee titles Media size might not be accurate when working with interlaced projects

- Bug Number: MCDEV-9523. When linking with the Avid Generic Plug-in, audio waveforms did not build properly in the Timeline when playing back an H.264 movie with AAC audio.

Media Composer Notes: 

1.     Desktop Video:  Avid recommends that you do not install Desktop Video software version 10.10.1 on Media Composer versions prior to v2018.5.1.

2.     Avid Artist DNxIO and Avid Artist DNxIQ: If you are using Avid Artist DNxIO, Avid Artist DNxIQ, or a BlackMagic Designs video device, please update to Desktop Video software version 10.10.1 or higher. The minimum Desktop Video version that will work with Media Composer v18.5.1 is 10.9.11. Older versions will be rejected, and you will not be able to use your hardware until you update.

3.     Dongle Info (Mac Only): The Dongle Sentinel driver installer is no longer automatically installed when you install the editing application. The driver is now located in the Avid_Utilities folder (/Applications/Utilities/Avid_Utilities/Sentinel_Driver). If you have a dongle, manually install the driver from this location.

4.     NVIDIA Driver: The editing application supports Nvidia Driver v390.77.

5.     Quadro 4000 - If you have a Quadro 4000 graphics card remain on the Nvidia v353.82 driver. Avid recommends that if you are on a Windows 7 system and working with the v390.77 Nvidia driver, you should enable desktop composition. See this article for details: http://avid.force.com/pkb/articles/en_US/how_to/Enable-Desktop-Composition-in-Windows-7

6.     DX Driver installed separately: Starting with Media Composer v8.9.4, the DX Driver was not automatically installed on Mac systems.With this release, the DX Driver is not automatically installed on Windows systems. 

How customers will obtain the October Media Composer 2018.10 Update:  

1.  Customers who have already installed the latest version of Media Composer or Media Composer |First will be notified of the availability of the upgrade via the Application Manager. The Apps tab also provides a link to download and install the update(s) when desired. 

2.  New customers who purchase Media Composer will receive the update in their Avid Master Account at https://my.avid.com/account 

3.  Customers on current Avid Update plans can download the Media Composer or Media Composer | First update from their MyAvid Master Account and Media Composer customers can also download the update from the Avid Download Center (login and password required.) here: http://esd.avid.com/ProductList.aspx

4.  Customers NOT on a current Upgrade plan must purchase either 1. new Media Composer Subscription Crossgrade or 2. new Subscription or 3. new Perpetual license to receive this update. 

Reminder: This release of Media Composer requires an active Upgrade plan. Customers have to have one before installing this update.

Hi. Firstly this worked on Monday and I have not knowingly made any changes to my system since then, but yesterday and today I am unable to log in to application manager with it getting stuck at the "Getting subscription data" message.

I am using Windows 10 64-bit.

Things I have already tried:

1) Turned off my system firewall completely

2) uninstalled and reinstalled both media composer and application manager

3) Gone to preferences and clicked 'Clear Cache files' & 'Restart App Man Helper' and restarted the application manager

4) Physically deleted the AppManager folder in c:\programdata\Avid (app manager has subsequently recreated this folder

5) pinged the avid servers at:

  https://license.avid.com:3443/ping.aspx

  https://license.avid.com:443/ping.aspx

  http://update.avid.com:96/ping.asp

6) restarted my pc (several times)

7) Updating application manager to the latest version.

So far nothing has had an impact. So from a system that was working perfectly two days ago i cannot access Media Composer. I'm due to present a video on Friday so any help for me to regain access to my project would be really really appreciated! Up to now I've been a happy user of Media composer First and have been considering upgrading to make this my primary tool, but I need to know that the licensing is robust.

Avid is pleased to announce the latest release of Media Composer v2018.10 on October 24th, 2018. The software is available through My Avid, Avid Application Manager, or the Download Center (login and password required). You must have a current Support & Upgrade plan to run the latest software.

+ OS SUPPORT:
This release adds support for macOS 10.14 (Mojave), while including macOS 10.13.6 (High Sierra) as well as 10.12.6(Sierra), and 10.11.6 (El Capitan).

+ NEW FEATURES:
- Additional AVC-LongG formats are supported
- Color Management LUT Fix
- Additional Color Space Presets

+ MOJAVE USERS:
Please note you may experience a significant delay in trying to install the application the first time, and the Finder may hang. Allow the process to complete after several minutes and you should be able to install successfully.

+ NITRIS DX/MOJO DX USERS:
Please note the DX driver is NOT automatically selected in the install process. Within the MC installer, when you get to Installation Type, be sure to select the Avid DX Driver under Media Composer Editing Application.

+ BUG FIXES:
This release addresses 40 bugs since the last release, including:

- In some instances, Media Creation settings may not have remain the same after closeing and opening the project.
- Audio may have been out of sync when linking ProRes 422 files
- Exporting an h.264 file as stereo did not export in stereo
- In some instances, you could not scroll while perofrmaing playback in the timeline
- Trim to Fill did not work on clips with a spatial adapter
- If you had Boris FX Final Effects Complete installed, you may have had problems with Open I/O devices
- Intermittently, the position bars under the source and record monitors did not move



+FOR MORE INFORMATION:
See the ReadMe or What's New documents published on the Knowledge Base prior to upgrading if you have any questions.

If you have general issues with installing or running the release, post them here. If you think you have found additional bugs, please start a new thread.