I'm a fan of advanced trimming.  I love how I can keep my music / sfx / dialogue all synced up and still ripple my clips downward.  

Is there any way to insert an edit from the source monitor, but control what clips get pushed?  The same way if I were to trim out a clip, I can select what happens with my sfx/music/VO?  

How do script marks work on a clip with multiple resets within it?  In others words between "action" and "cut" the actors run through the same portion of the script, going "back to ones" instead of yelling "cut" and starting a new take?   Can script marks point to the same line in multiple points within the same clip?

We're subtitling a documentary with subcap and experience serious problems. First in MC 2018.12.0: when we ticked edit Master Caption List in the subcap effect palette, Media Composer quitted unexpected 8 out of 10 times. Found here online this was a bug in 2018.12, going to be resolved with next update. So we updated to 2019.8 this morning. Created new user settings at the first start ofcourse. And...subcap is showing the same malfunction that makes MC to quit. So is there a fix for this, because this problem is costing us a huge amount of time and the application crashing so many times in row is not healthy for the software and the hardware... We're on an Mac Pro Late 2013 (3,5 GHz, 6 core 32 GB RAM) - OS Mojave.

A number of .pngs with transparent backgrounds that DEFINITELYworked before in an existing project now no longer work in 2019.7 Nothing has changed. even relinking or reimporting does not work under any of the alpha channel options. Obviously pngs do not have alpha channels so what to do?

MC 2019.7 now available

The new Media Composer 2019.7 release along with Media Composer | First 2019.7 was made available, Tuesday July 23rd, 2019.

Location: Updates to Media Composer are available from Avid Link, MyAvid and the Avid Download Center (login and password required).

Dongle Info (Mac Only): If you have a dongle, 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. If you have a dongle, manually install the driver from this location (/Applications/Utilities/Avid_Utilities/Sentinel_Driver).

Status of Support Plan:  The ability to launch this Media Composer 2019.7 software is dependent on the status of your Upgrade and Support Plan on the date this software version is released.  

What’s fixed in 2019.7:  The following have been fixed:

-  Bug Number: MCCET-2905. Using the arrow up and arrow down keys to move clips from one track to another did not work when a nested effect was open.

-  Bug Number: MCCET-3016. Audio meters did not display in the Audio Tool, Audio Mixer or Timeline window during a Digital Cut.

-  Bug Number: MCCET-2986. In some instances, adjusting audio level from the Audio Mixer, while playing a sequence, did not affect the volume.

-  Bug Number: MCCET-3006. (Windows) Media Composer would crash when importing embedded AAF into a 25fps HD project.

-  Bug Number: MCCET-3112. (Script View) In some instances, Media Composer would crash when scrolling in a large bin and while playing in the Source/Record monitor.

-  Bug Number: MCCET-3003. You could not rename group clip tracks.

-  Bug Number: MCCET-2899. All related media object where not highlighted when selecting

media relatives if you grouped clips and selected Select Sync Clips Using “Film TC/Sound TC”.

-  Bug Number: MCCET-3031. In some instances, when I/O hardware was enabled, you could not import/transcode to AVCIntra50.

-  Bug Number: MCCET-3036. When working with an HD 1080p 25 project, transcode options changed if I/O hardware was enabled/disabled.

-  Bug Number: MCCET-3032. You might have received an “Exception: No Source” error when performing a video mixdown and choosing over/under as a Stereoscopic option.

-  Bug Number: MCCET-3086. You could not copy and paste markers using Ctrl + C and Ctrl + V.

-  Bug Number: MCCET-3059. You could not save newly created and renamed shared bins in project sub folders.

-  Bug Number: MCCET-3041. If you pressed ESC a few seconds after performing a trim, the Timeline did not update correctly.

-  Bug Number: MCCET-3026. When consolidating a subclip with “Delete original media files when done” enabled, an unrelated Transcode notification message was displayed.

-  Bug Number: MCCET-3073. AAF exports did not include the media if the clip was muted.

-  Bug Number: ETE-1512. A dark gray fill (instead of black) is provided now in the viewer for Pillar and Letter box areas that are not masked.

-  Bug Number: MCDEV-11146. Removed Show Position and Show Effect Contents from the Timeline settings.

-  Bug Number: MCDEV-8227. When switching between MXF and OMF media types in the Media Creation window, the window would not refresh until it was reopened.

-  Bug Number: MCDEV-8527. The Tool Palette moved position after resizing.

-  Bug Number: MCDEV-10060. Precomputes were lost when reentering the Avid Titler+Title tool.

-  Bug Number: MCDEV-10346. An asterisk might have appeared in the Bin name even if no changes had been made to the bin.

-  Bug Number: MCDEV-10412. You might have experienced problems loading sequences with Avid Titler+ titles between Windows and Mac systems.

-  Bug Number: MCDEV-10512. Avid Titler+ characters did not maintain relative position between each other during animation playback.

-  Bug Number: MCDEV-10624. Scrolling in Text view in a bin was column by column rather than by pixel.

-  Bug Number: MCDEV-10632. Even when a change was made, the Bin View name did not display in italics to indicate a change to the view had been made.

-  Bug Number: MCDEV-10801. Changing the sequence name in Frame View did not update the name in the Composer monitor or in the Timeline.

-  Bug Number: MCDEV-10818. Floating a bin might have resulted in the bin resizing too small.

-  Bug Number: MCDEV-10880. When creating a Volume Bin, “Export Folder” and “Set location” text does not display correctly if you are working in a Russian locale.

-  Bug Number: MCDEV-10918. Mapping “Set Bin Display” to a letter on the keyboard did not work.

-  Bug Number: MCDEV-10934. Typing the first letter of setting displayed the setting at the bottom of the window rather than in the middle of the window.

-  Bug Number: MCDEV-10995. When in Frame view, if you dragged a clip to the Source Monitor, the clip would load into the source monitor, but the clip’s thumbnail was moved to an unintended location within the bin.

-  Bug Number: MCDEV-11131. In some instances, effects with graphic backgrounds did not draw correctly in the track effect dialog.

-  Bug Number: MCDEV-11145. An Interlaced Roll/Crawl motion effect created with Titler + appeared as a frame motion rather than field motion effect.

-  Bug Number: MCDEV-11191. Double clicking to float an existing bin always stacked the bin in same position/size and did not retain its last known state.

-  Bug Number: MCDEV-11231. You might have experienced an occasional crash on exit with AJA 4K hardware attached. You must update to AJA Desktop software v15.2 to see this fix.

-  Bug Number: MCDEV-11245. The File Cache tab in Media Cache Settings window was cut off and difficult to activate.

-  Bug Number: MCDEV-11299. The font appeared bold in the Name fields for the Source and Record side of the Composer window.

-  Bug Number: MCDEV-11317. Titler + titles appeared in the bin without an icon. 

-  Bug Number: MCDEV-11429. The Name column did not appear as the first column in the Media Tool.

-  Bug Number: MCDEV-11442. (Bin Frame view) Clicking near edge of a selected item in the bin while in text-edit mode deselected the item.

-  Bug Number: MCDEV-11453. The Audio Clip Gain window did not remain open when you tried to enter a value from the keyboard or if you tried to move the slider up with the mouse.

-  Bug Number: MCDEV-11491. Pressing and holding the ALT key while dragging a number of clips onto the Record monitor did not create a sequence with the clips in the order they were sorted in the bin.

-  Bug Number: MCDEV-11492. If you selected a dropdown menu in the Inspector Tool and then clicked on another window, focus remained on the Inspector Tool.

-  Bug Number: MCDEV-11530. Double clicking a clip in Bin Frame view to load in the Composer monitor did not leave focus on the Composer monitor.

-  Bug Number: MCDEV-11534. The Lock/Unlock Bin options were missing from the Bin Container sidebar context and Fast menus.

-  Bug Number: MCDEV-11546. You might have received a “Crumb not found” error when deleting markers in the Source monitor.

-  Bug Number: MCDEV-11550. Perf information was missing in the Setting format pane of a film project.

-  Bug Number: MCDEV-11562. Tab and Shift+Tab did not allow you to move to the next or previous column in Bin Text View.

-  Bug Number: MCDEV-11568. With the Interface Brightness set to dark, track numbers were too light when you expanded the Audio Mixer Tool.

-  Bug Number: MCDEV-11569. You might have received a “PMM_SYNC_FAILURE” error when performing an Audio mixdown of a sequence with sub-clips and sample slip.

------------------------------------------------

Limitations Media Composer 2019.7:  Listed below are the known limitations in v2019.7.

-  Bug Number: If you launch a project and receive an “Enable 3rd Party Emulation” warning, even if you select Enable in the warning dialog, you should also perform the following: Select File > Settings and click the Project tab. Click General Settings and select “Enable Bin Sharing on 3rd party storage emulating Avid NEXIS/ISIS.”

-  Bug Number: MCDEV-11197. In some instances, the Interleave option might not appear in the Export As dialog box. If you are performing an Export using the Avid Media Processor, the Interleave option should appear when you choose Stereo, 5:1, or 7.1 Audio.  Workaround: If it does not appear, briefly toggle back to the Mono setting, then toggle to Stereo Mix once again. Doing so should reveal the Interleave option.

-  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: (Mac). You may occasionally see the menu bar flash followed by a brief beach ball. To fix this, deactivate “Displays have separate spaces” under System Preferences > Mission Control settings.

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

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

--------------------------------------

Media Composer 2019.6 Documentation: The “ReadMe” document for this release of Media Composer 2019.7  has been uploaded to the Knowledge Base - Media Composer 2019 Documentation Page

When a source group or a group in timeline is playing I' would change camera angles whille it's playing not stopping the playback. But when I use the previous/next in group buttons or the M1/M2/M3... buttons it stops on the frame and then change the angle so you have to press L or spacebar or whatever to play it again. Is that possibile? Is it a my problem or someone has it too? 

I have the latest MC 2018 release

While playing a group in source or record monitor you would change camera angles not stopping the playback. But I can't get this. When I press the previous/next in group button or the M1, M2, M3... button it stops on the frame and then change the angle so you have to press the L, spacebar or whatever to play it again.

I'm on the latest MC 2018 release

Ive been looking around many of the posts regarding workspaces/bins and project settings but I cant find anything specific to the new interface.

I really want to make this new software work, but its proving to be a real problem.

Weve just completed the Burghley Horse Trials for the BBC and we ran with 2 x MC 2018 and 2 x MC 2019.

None of the editors could work with 2019 - its to do with the way the bins are managed and where some of the menus are. For instance wheres the little pop out menu that you used to be able to access from the main viewer menu?

Also several times with 2019 the editor 'lost' the project menu so did not know which project he was working in (we run multiple projects - around 8 to make our workflow easier). It seems the only way was to exit Avid and restart - however this then reset all the bin workspaces again.

Weve just gone back to 2018.12.7 which works just the way it is supposed to.

I am very sorry Avid, but the new interface does not seem to have been designed with professional editors in mind.

We were very excited to think there would be a new version a few months ago but it does not feel as though its been properly thought through or tested.

I'd really like to be proved wrong on this - anyone else havng problems?

I am having issues deleting master clips in bins. The clips and bins are not locked. I am able to delete bins and folders in the bin container so it isn't the keyboard.

This doesn't seem to be a known issue as it is not in the known issues 2019.8.pdf

Any suggestions?

Hi Team! I'm working with ProRes 422 proxy (1280*720 @24) media.

My project is a custom 1280*720 @24 on AMC 8.4.5 w/QuikTime plugin 1.4.0.8690

But, when I try to consolidate the media I received the following error:

Assertion failed: mobisFrameRateMixAndMatch… File: ProxySyntheticMobs.cpp, line: 1215

If I click in "Debug" I received the following msg: Tracks have incompatibles edit rates

I don't have ny problem if I try to Transcode the files, but as far as I know, ProRes could be Consolidate, or am I wrong?

I'll really appreciate your help!

Thanks in advance,

Alvaro.-

Hi!

Copying and pasting text between locators (sorry MARKERS), stops working after a few copies and pastes.

Reboot and it works again... a few times. Very dull.

Any takers?

Thanks!

MC 6.5.2

OS 10.7.4

Mac Pro Quad Core

i've made a home made avx plugin for blend modes - you can test it :) 

it's pretty simple and contains only pure reference maths.

it's available for WIN and MAC and probably MC 6+. - currently tested on 2018 and 2019 MC versions.

here's the telegram channel with current news: https://t.me/MDVAvid/49

and download site at: http://djfio.com/mdv/

xBlend generic plugin :)

it's free.

Dear Avid User,

I try to install my third monitor with a Blackmagic Ultra Studio Mini Monitor Box 4K. 

I use a Mac book pro osx 10.14.6 and avid mediacomposer 2018.9 

I connected Ultra Studio Mini Monitor 4k, with an adapter for thunderbolt 3 to thunderbolt 2 and a thunderbolt 2 cable. From the box I go with HDMI to my monitor.
I installed the latest driver desktop video 11.4
The Avid recognized the box but I have no video output on my Monitor. And no sound either. Therefor I have another device with usb. So maybe it's the wrong driver? So I tried 10.11.4. But I have the same problem.
Or is there something else I missed? When I switched on the monitor it said "wrong frequency".
I have HD material with 1080p25. With my old workstation (Windows Computer, AJA Box and Avid MC 7) the monitor worked very well.
I would be sooo happy about some ideas.

Kind Regards

Hello Everyone,

I think native, flexible media managementis lacking in Avid. "Have you tried Media Tool?", you might ask. Here's my problem with Media Tool - it's not easy to use. For example:

1. An Assistant Editor finishes logging, then wants to transfer the project to an Editor. He'll bundle up the assets in one folder, grab the Avid project folder, and send them over to the Editor. Might be over the network (peer-to-peer) or through sneaker net.

2. An Editor finishes his project, and wants to do a backup. Same as before - he'll bundle up the assets, grab the Avid project, and store them on backup drives.

3. We produce events that require last-minute changes. Plus, there's on-location editing that requires gathering assets from multiple users. So bundling all the assets you need before traveling is critical. Hotel networks aren't built for large file transfers.

For years, the alternatives were MediaMover and MDV. MediaMover can do all the above, but MDV is the best I've ever used. It's simple, easy, and fast.

Here's the problem with MDV. (Problems, really.)

1. It's Windows only. There are ways of making it work in OS X, but you hate them all. How do I know? Because it keeps coming up.
2. It has limitations in Wine - neither bin sifting nor folder scanning works.
3. It's abandoned.

So what would it take to create a native OS X media management tool?

First, we need to know what we're working with, the data. Are there available file specs on:

1. Media Stream Managers (MSM's)
2. Projects
3. Bins
4. Metadata layout on individual MXF's

Is it just a matter of asking someone from Avid HQ? Do you know anybody?

It's clear we need something. But everyone's busy, you know... editing. Plus you're thinking, "What can I do? I'm not a programmer!" Well, I'm an anomaly. I do what you do, but I also have some development/IT chops. They just need some refreshing. And this project would be worth refreshing them.

So what do you think? Is it worth making the next MDV? Are there any others like me who would be interested in contributing? Do you have any contacts that could help point me in a direction?

Thanks!

Hello,

just for your information, we are currently downgrading to 2019.7 again because 2019.8 has too many issues.

On a MacPro 5.1 and 10.13.6 Avid has problems after hiding the Application or switching to other applications. Going back into Avid doesn't work or needs long time. This morning Avid did not came back, so I had to force quit. If I press cmd+q I can force the App to come back. Clicking the App in the Dock or switching with cmd+tab doesn't work. In the menue bar Avid is the active application but the App is just not there. After a while, when it comes back, it is not responding for some seconds.

On an AJA System (iMac Pro, 10.14.5) Avid most of the time crashes after quitting. Again.

Creating a new bin creates a bin with the columns all messed up. Name is somehere at the end, Color is not there and the first colum ist Audio SR. On both systems.

This is too much.

Doyle

If an Admin reads this: Sorry, I posted this in the Avid Options Forum at first, maybe someone could delete this thread from there.

Mac 10.14.1  MC 2018.11.0

I am trying to make a short replacement of audio in an MXF Op1a DNx 145 50.94i 1920x1080 8 track audio file.

I want to insert a short segment (7:14) on tracks 1 and 2.

I marked in and out, made sure only those track were selected and opened the Insert Edit Export tool.  I selected the file to modify,went to Options and checked Use Marks and Use Selected tracks.  I press the OK and immediately get the following error.

I have run into this a couple of times and must say it makes no sense at all.

I go to fix a single page of credits for example.  I mark in and out on the repaired sequnce, select Insert Edit Export, find and select the file to insert into, select Use Marks and Use Selected tracks, press OK and I get some version of the following error message:

"The sequence duration is longer (xxx frames) than the destination clip duration."

I know why this is occuring - when I made the original file export, it was from a longer sequence than I needed.  I used Use Marks on that export.  But now this choice has come back to haunt me.  If this is a limitation that can not be fixed, it needs to be CLEARLY explained in a workflow doc.  Seems like an oversight to me.

Jef

MC 2018.11  Mac OS 10.12.6

I have been beating on this tool, trying to decide whether it is safe to use during delivery to networks.  I have had issues.

First, on my home system which is limited to El Cap OS I can not get it to work at all reliably.  Now testing on a system with Sierra, it is working BUT I am getting some errors.

First, I took a show that I had output to MXF OP1a DNx 145 and changed about 5 Slates in the show.  This seemed to work well.  I tested the resulting file in MXF4mac player (RIP), Premiere 2018, Resolve 15 and it looked great.

When I attempt to link back to this file in Avid I get:

Exception: Cannot create the AMA sample mapper to play this clip - SelectFileMob() failed. OK

What????

So I did a bunch of test trying to recreate this error.    I made new MXF OP1a file and just started making small changes and linking back in Avid.   All of these worked just fine until I deleted audio in the same area where I was making a video only change.  I selected Use Marks and Use Selected Tracks in the Insert Edit Export menu.  I only had video tracks selected with my In and Out marks.  I did the edit.  After Avid was done making the fix, the following error message popped up:

AMAMapper::Setup() floc is set to NULL.  OK

Avid was not happy linking to this file UNTILL I quit and restarted Avid.  Then all was good.  The fix had worked as I wanted it to.

All of this is to say I am nervous in using this tool for critical deliveries.  And all deliveries are critical!!

I have started other threads on this tool and get little to no response.  Which surprises me based on the incredible value this tool presents.  I feel like I am just calling out “Bueller”.

Jef

Tested with Mc 2019.7/8 Can't Enable Dynamic Relink. GOoto the settings Dynamic relink, see the checkbox, click the box and the options flick for a split second and won't enable. Here's a screen recording.

https://drive.google.com/open?id=1sKKo_Ad_srqs4fcxlyKeIQIxdZyX6rRE

Firstly the Blackmagic BRAW 1.5 AMA Plugin to import footage from the Blackmagic Pocket 4k, ursa Mini Pro 4.6 in the BRAW format.

1. Can't transcode with-in Avid the BRAW format to Avid MXF format

Import BRAW Pocket 4k into Avid Media Composer. Columns for video in Avid Media Composer is 'un-supported' impossible to transcode with-in Avid Media Composer to Avid format. As you get un-supported resolution error.

2. Filename is cut-off and Timecode start is 00:00:00:00

Imported filename is cut off comes in the column 'name' A003_04182157_C0 Should be A003_04182156_C009 there by making edl/aaf impossible to work with afer in Resolve. Timecode start is always 00:00:00:00. When the BRAW files are imported into Da Vinci Resolve the correct timecode start is displayed in the file.

3. Impossible to edit from Avid BRAW for finishing in Da Vinci Resolve

Export an AAF/EDL from Avid Media composer for finishing in Da Vinco Resolve. Import EDL/AAF as new timeline in Resolve. The neweley created timeline from th4 Avid EDL/AAF media is all cut off for the filenames example A003_04182157_C0 Should be A003_04182156_C009