Hey,

Probably my first post here. I'm a colorist working on a show in MC. It's an HD show and has one main video track with occasional PIP and graphics. When I render I use MXF OP1a and either DNxHR SQ or DNxHD175X depending on who the render is going to. My render speed is typically a bit slower than realtime - a 23 minute timeline takes 30-35 minutes to render. 

On the same system (Threadripper 1950X, 64GB ram, 1080ti, 8-bay RAID) Resolve will render a similar sequence at 2-3x realtime so like 8-12 minutes.

Is there some mix of settings I can use to speed things up? I'd love to get 2x realtime on renders. This slowness is compounded when exporting longer timelines - a 45 minute timeline is excruciatingly slow.

Thanks!

Match Framing to a group-clip or audio-only clip, randomly gives:

FatalAbort Assertion failed: GetNumInputs() >= m_numUsedCameras, file ... MultiframeCombiner.cpp

- Mac or Windows
- Media Composer 2021.2 or 2021.5

Sounds a lot like:
Bug Number: MCCET-3996. You might have received an “Assertion failed” error when performing a match frame with a sequence with group clips.

Except that was supposedly fixed in 2021.5.

Rolling back to 2020.6 or earlier solves it.

We opened an Avid case about it, but they weren't able to help and the case is now closed.
Is anyone else experiencing it, and found a good solution?

I am a fan of AVID and its standard tools. But now i am working in a 4K project and I am losing tons of time just by making a simple lower third title. It needs to animate a bit, but it just wont do what I want. Just make is move up or down seems to be impossible. With the old Title Tool, I was able to do that in a minute. Now I am frustrated because after an hour it still won't do a simple move.

I am really frustrated . How can a professional company like AVID make such a bad tool.

Why can't I make a simple move of my title? Is it me?

Grrrrr.

My PC is slowed to the point of immobility by this program. It wasn't always like this. Everything worked fine for a couple mnonths, but a couple of weeks ago, it started. My system would grind to a halt. I updated my (brand new) W-2295 Xeon 3.00 ghz 18 core 36 logic processor HP z4 with an AMD WX 9100 in terms of EVERYTHING: bios, drivers, you name it. I even did a fresh OS install with the help of HP tech support and reinstalled all the drivers myself. When I installed Media Composer, even without any other software on there, this happens:

In case you can't see it, it's AvidAppManHelper.exe taking up 93% of my CPU, without Avid even running! This happens from startup. I opened a case with Avid's online tech support a couple weeks ago, but they advised me to BUY A NEW GPU (!) and then ghosted me a week ago. What can I do?!

Media Composer 2021.5 on Mac OS 11.4 Big Sur

My Mac OS keyboard setting has always been set to Norwegian (as I use a Norwegian keyboard layout), and Avid shortcuts have still always been in the same place as if I've used a British layout.

Now, however, the zoom in/zoom out function that is on CMD+[ / CMD+] on a British keyboard, which was always on the same key locations (CMD+å / CMD+¨) on a Norwegian keyboard, no longer work on my Norwegian keyboard, and as you can't map CMD shortcuts in Avid I'm forced to map it to other keys on my keyboard or pen tablet.

Avid's keyboard setitings remain on "MC English (United States)", which I've never changed, and if I change Mac OS's keyboard setting back to "British" the shortcuts go back to normal (though when I'm constantly between Avid and remote communications with Norwegian edit producers or series producers that's not an option).

I'm assuming this is a mistake, so would be great if it can be reverted to normal in the next update!

Hello, we are experiencing problems with Avid Link on one of our machines, for activation of Avid Media Composer Ultimate, version 2018.12.10.

The licence got renewed as usual and was active on Avid Link, but Avid Media Composer continued to ask for activation regardless. Logging in or off didn't change the situation and it was not possible to deactivate it.

We had to start Avid on trial as the machine was needed, but now if i try to activate the license i get "activation failed 101 total device count exceeded" error.

Working remotely as an Assistant Editor, I changed the label colors on the master clips in the project on my external hard drive (Pink = archival, etc.). When my editors send me bins with new cuts, will my label colors get changed if they're using different label colors for the same master clips? If so, is there a way to disable that?

Hi, wanted to get more information about this hidden Nexis feature.

1. Is there documentation on it anywhere, in the docs or KB? Because I couldn't find anything besides this 2016 post.

2. Is that "magic background mounting" only works on Windows, not Mac?

3. Does the OS user account credentials have to do with it, or it's based off of the Nexis Client Manager authentication? (in a Nexis without LDAP binding)

When I try to export a file (locally - Quicktime, fast or best including DNXHD) the file looks like it is going along, but it reaches the end and then continues to start over and over. The file itself never goes past 1kb. 

Has anyone experienecd this and what was done to resolve it?

I own Avid Media Composer 3.5 and just recently my iMac's operating system crashed and I needed to reboot. I lost all my files including AMC. I just want to reinstall my current version of Avid on the same iMac computer. I tried inputing the same System ID and Serial # but the activation failed and it told me to contact Avid Customer Service. Can anyone please help me activate my AVID program. Thank you!

Hi, 

I'm facing whit this issue. (I quote, It's summarizes the problem well)

"Sometimes when footage was shot with 50FPS for example, editors want to have it synched with sound (if there is any).

So what happens is, that an assistant Editor applies a timwarp (200%) on the Video Master Clip, syncs it with the audio file and generates a subclip. This method works well up to a point where you want to transfer an edit to DaVinci Resolve to online the whole thing. (for the editing process the footage was converted from ProRes4444 to DNxHD36)

An AAF File doesn't seem to transport the information that there is a timewarp applied to the footage and it has to done by hand. It's not a problem when there are only a couple of them but if you have a sequence with minutes of those it takes hours to do it."

more here

My project 1080p 25FPS

Delivery will be approx 60min long 25FPS 1080p

All footge shoot 50FPS, multicam, (4k, 8K),  all comes with Audio.  Has to be synced, groupped.

DnxHD36.mxf created with resolve  - 25FPS

In Avid, Version:2019.12.1.53716.0  (slowmo) clips were dropped to a sequence, (one by one each has own),  with 200% speed up motion fx on them. Put the audio under them, and created subclips. Subclips were gruppped. As soon they get into a sequence, they behave as normal 25FPS, i can do resize, stabilze, etc... But at export, AAF / EDL doesn't take 200% the motion fx to resolve.

So, do you anyone (Avid tech crew as well) know any sollution for this? Will be fixed?

Or any other workflow how to deal with a tonns of 50FPS footage in to a 25FPS project?

Thanks.

Great News! The new Media Composer v2021.5. is available today, Tuesday May 4^th, 2021. This release includes several bug fixes and improvements. including, but not limited to:

• FrameFlex quality was not good on render, mixdown and preview
• You could not activate Media Composer trial if Media Composer | First was activated

Location at Launch:  The new Media Composer 2021.5 is available in MyAvid Master Accounts, through the Avid Link application itself and from the Download Center.  The ability to launch Media Composer 2021.5 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2021.5 will be released on May 4^th, 2021.

Status of Support Plan:  The ability to launch this Media Composer 2021.5 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released. Media Composer 2021.5 will be released on Tuesday May 4^th, 2021 at 12pm EDT.

Media Composer Notes:

MCDEV-11537 If you intend to use full-frame stereoscopic with an Avid Artist DNxIQ, you may want to remain with Media Composer v2018.12.x until the issues with Stereoscopic support are resolved in a future version.

• (MCCET- 2541) When working with Avid Artist DNxIO or Avid Artist DNxIQ, you should disable the Line In recording input (BlackMagic Audio in the Windows OS).
• Avid recommends that you do not install Desktop Video software version 10.10.1 on Media Composer versions prior to v2018.5.1. 
• 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 v11.0 or higher. If you are using Avid Artist DNxIV and Avid Artist DNxIP please update to AJA software v15.2 or later.
• Qualified Operating Systems: For information on qualified operating systems, see Qualified Hardware and Operating Systems.
• 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.

What’s Fixed in 2021.5:  The following has been fixed.

• Bug Number: MCCET-3858. In some instances, performing a Consolidate changed the tape base Timecode
• Bug Number: MCCET-4012. Exporting an Edit While Capture “In progress” clip as h.264 did not work with the UME plug-in.
• Bug Number: MCCET-3996. You might have received an “Assertion failed” error when performing a match frame with a sequence with group clips.
• Bug Number: MCCET-4001. Sorting was inconsistent in bins when in Script View.
• Bug Number: MCCET-3999. Changing the “Start” Timecode of a sequence from within the bin column, unexpectedly caused the drop timecode (DF) to become a non-drop timecode (NDF).
• Bug Number: MCCET-4026. When T+ button was mapped under the Record monitor, the Titler+ icon appeared different after re-launch/edit.
• Bug Number: MCCET-3925. Clips with alpha may have had unexpected level changes when rendered.
• Bug Number: MCCET-4060. Color adapter should not have been added to alpha channel when doing a refresh sequence.
• Bug Number: MCCET-3624. In some instances, QuickTime h.264 could not be linked or imported.
• Bug Number: MCCET-3824. FrameFlex quality was not good on render, mixdown, and preview.
• Bug Number: MCCET-4082. Performing a video mixdown of a sequence named with a trailing space produced mixdowns that resulted in issues such as Reveal File not working properly.
• Bug Number: MCCET-3895. You might have received an “Out of Memory” error when exporting a 2 hour sequence to ProRes HQ 10bit.
• Bug Number: MCCET-3843. When working with Titler+, some Arabic text did not display properly.
• Bug Number: MCCET-3957. In some instances, Titler+ text did not look correct in the Record monitor. but did look correct in the Effect Editor. 

Limitations: The following are known limitations

• Photoshop PSD files are not supported for AMA linking if QuickTime is not installed.
• Some fonts, by their design, are available only in Bold. On the Mac system it can happen that selecting a font does not produce any visual changes. Try selecting “Bold.”
• 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: MCCET-3788. You might receive a “clip name is a clip in a multi-essence file that cannot be exported using the specified Embedded in AAF setting” when exporting embedded AAFs with OP1a audio clips.Workaround: Consolidate the OP1a clips to Avid OP-Atom prior to performing the export.
• Bug Number: APPSVCS-723.  The Collab App in MediaCentral CloudUX window does not currently work with Media Composer.
• Bug Number: MCDEV-13604.  You might have issues playing clips containing Media Composer effects in the Baselight User Interface if the Fast Image Access option is enabled in the Baselight plug-in
• Bug Number: MCDEV-12926. (macOS) If you have upgraded to macOS 10.15.4, there is a known issue with local attached RAID storage. The system will hang when running Media Composer or copying large files. This does not happen with earlier versions of the OS. You can read details about this issue in this blog. This limitation no longer exists with macOS 10.15.5.
• Bug Number: MCDEV-12988. (macOS) The AMA Drastic plug-in is not supported with Media Composer v2020.4
• Bug Number: MCDEV-12964. For a faster performance of export audio/video sequences to .mov in 2020.4, please render the sequence prior to export, or disable the GPU fx (in the Render Settings - Current menu)
• Bug Number: MCDEV-12735. Maestro graphics do not appear correctly in the Timeline if your system uses the Radeon video card.
• Bug Number: DEFI-1808. (Media Composer | Distributed Processing) Two clips or sequences will always be created when performing a consolidate or transcode with Media Composer | Distributed Processing.
• Bug Number: MCDEV-11481. Promoting a title from the Title Tool application to Avid Titler+ cannot be performed if it includes a motion adapter.
• Bug Number: MCCET-11796. Larger than 10 bit DPX files might fail to link correctly.Workaround: Go to File > Settings and click the User tab. In the Link Settings, click the Link Options tab and make sure Alpha Channel is set to Ignore.
• Bug Number: MCDEV-11430. Media Tool ignores the “Current project” filtering option and lists media files that are not associated with the current project.
• 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-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: (macOS).  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.
• Bug Number: MCDEV-5385. MultiCam editing with Panasonic LongG media is not supported with this release.

For details on the complete bug fixed, see the knowledge base Media Composer 2021 Documentation page at launch.

ReadMe: The new ReadMe will be uploaded to the Knowledge Base Media Composer 2021 Documentation page at launch.

Hi all,

I'm getting really slow playback performance the second I add a titler + effect onto my sequence. I have to render the titler+ effect in order to preview my title in real time. 

For context, I'm on a 1920x1080 timeline, with DNxHD SQ footage.

I'm on 2021.2 too. is anyone else having slow performance with titler +?

Here’s the weird stuff that happened to me: I’m using MC 8.5.1 (updated a few weeks ago). So I start Avid and oddly up comes the activation flag, okay do it, up comes the manager, which shows I’m activated (perpetual licence) which means I can’t activate, but MC won’t start – catch 22. Call Avid, some corrupt files in AppManger, delete those, works fine.

Next day, same issue except I also notice the computer is working hard although no apps are running. I open task manager and the C drive is running 100%, the RAM is 19GB and the CPU is 60%. The C drive is filling up fast and I can’t stop it. So I do the virus / malware search, nothing. I track it down to the AppData file which is being filed with thousands of AppMan_jetty folders,eg;

C:\Users\Michael\AppData\Local\Temp\AppMan_jetty-TEMP-old1814571676

Eventually filling the drive to 100% capacity. And guess what was creating all those files? Avid Application Manager. Anyone else had this sort of experience and have any ideas how to stop it?

My first impressions of Titler+

- Wow great at last, over 20 years after Unicode became a standard, we at last have a modern Title Tool, rewritten, with a modern(ish) interface.  So I can add titles in all scripts, with diacritics, in Cyrillic, in arabic…. No more fiddling around with photoshop, exporting, importing. Hurray!

- Toolbox nicely laid out. Not too many bells and whistles which are unnecessary most of the time.  For fancy 3D titles I’ll use another tool - here we have a modernised replacement for the old Title tool, usable for lower thirds, simple static text and end-credits (the primary uses of the Title tool) with the possibility for soft discreet shadows which are very important.

- It is directly accessible from within the timeline, no second window, no plugins, it is integrated.

Great work…

But then I started to use it….

OK, now I expect a few issues after all this is a first release (but not an alpha version), a few unforeseen use cases etc….  What I found to be honest disappoints me greatly. Certainly my expectations were high, expecting not only a slick, easy to use welcome update of the >20 year old Title tool for the final year of the decade, but with the niggles with the old title tool sorted out (that came up very frequently and well known amongst seasoned editors and AEs), namely:

1. Possibility to add left, center and right justifying tab-stops allowing two column rolling titles (for end-credits).  

2. The possibility to copy and paste images into rolling titles (used to work reliably a long time ago…)

3. The possibility to export all titles on a track as text with timecode (as is possible with subcap) for reports required by production (would be fantastic)

4. Full Unicode ie. accented / non-latin character / right-to-left support.

5. Or maybe even something amazing like importing an RTF file making a rolling title with tabs, images, fonts…  or constraining vertical movement in rolling credits to a fixed number of pixels to avoid flicker… I digress… :-)

The impression I have is that it was not thought out from a user perspective, the result is nowhere near as intuitive as it should be for software today. 

In a sentence, Titler+ -  it is a bit like a sliding door with a pull-handle and a sign saying Push…. ;(

So here we go : 

a) You click in the monitor, a caret appears, you can type.  Double click a dotted border appears, so far so good.  All is nice and works as expected.  A good start.  It has an ugly black drop shadow that I’d prefer off by default, but I can turn it off. Fine. Looks good so far.

b) Click on the T in the Titler+ « toolbox », you get a square - You type and the square doesn’t change size, the text overflows - no wrapping….  No means (that I found) to have a text area that will wrap, not that it’s that important but the UI leads to expect that behaviour.  Resize the square and the text changes size, but the square is still smaller than the text???  Can’t change the size of the square without deforming the text.  It turns out the T creates a text layer (zone) not simply allowing text to be added, this is unclear….. hmmm it’s starting to feel a bit quirky……

c) Playing around with it I understand that there seems to be two types of ‘object’ - a ‘layer’ = zone that is created in the safe area that you can resize, resizing all the ‘child’ objects ..  and text created by clicking, making ‘child’ objects of a layer….. Phew…. Seems far too complicated and unclear - problem with nomenclature and UI.  Maybe reduce opacity on all other layers other than the selected one to indicate the current layer, but still UI badly thought out.

The whole layer / text object concept is very unclear in use - should be straightforward and evident.  I create a text object and that should be it, they have an order that I can change. Rather than have confusing layers (this is an implementation detail that should be hidden from me), allow me rather to group objects together, with safe-area guides as before.  I should be able to group and ungroup text or graphic elements and reorder them at will.  Or keep all objects independent as in the old Title tool.  The parameters in « layer » - position, scale, rotation, skew should simply apply to the current object or group, with the possibility for global positioning/scaling.  Simple and easy to understand, and closer to the way much other software operates.  No need to have layers, particularly as the UI has no window showing the hierarchy of objects and what layers exist (justified in eg. Photoshop but not here).  Something reminds me of TitleDeko with less UI... hmmm...

d) Can’t get rolling titles to work for the life of me…. That is to say…. No vertical scroll bar.   Rolling titles are used 99% of the time for end-credits, which are typically 10-20 times the height of the frame.   I can see the rest by moving the position in the clip and selecting ‘effect mode’ in the effect editor, but then I can’t edit.  And « Effect mode » in the effect palette this doesn’t mean anything at all!! I am in effect mode..!!  This is misnamed.  « Preview » maybe?  And there is no none, just Crawl, roll etc... Not clear.

e) The relationship between the effect palette and the titles is unclear.  Eg. Select a few characters, layer/scale has no effect as it only applies to layers (zones) (no visual cue as to which parameters apply), Layer/Add Text adds a new independant Text Layer, not text within a layer…. Should be named Layer/ Add text layer…     I understand the principle, but there is a problem of organisation and naming, making it very unintuitive (related to c)

f) The mixture of parameters that apply to the currently selected layer and operations‘select layers’, ‘add text’ in the same place is misleading and seems poor design.  Effect palette should be essentially for parameters and related operations, especially as there is a dedicated toolbox window with this effect for everything else - much more convenient (great that they this is the first AVX2 effect with a dedicated interface - everything does not have to be shoehorned into the effect palette). Also no means to add a tracker as was possible previously.

g) Accented characters can not be inputted from the keyboard.  É, ç à from the keyboard are ignored.  This wasn’t tested it would seem with non-US keyboards (I’m on MacOS 10.12…6, with a French keyboard).  But you can copy and paste anything you like including non-latin and right to left scripts, which is great news.

h) Selection of text.  Every text editor, be it in Word, Photoshop, Title tool… changes the background of selected text…. Here, you get a confusing rectangle, making you think that you have created an new object….  The difference between a click creating a new object and selecting an existing object is not always correctly handled -> there should be an arrow tool for selecting and a text tool for creating/editing and a way to make the caret disappear.  Feels quirky.

i) No means to select and align multiple text objects (left, right, center), a) with respect to each other and b) within the frame.  Multiple object selection impossible via Cmd+click or Shift+click.

j) Select previous/next layer icons look like alignment icons….

k) Resizing of rectangles should be unconstrained by default, and aspect constrained with shift.  The opposite is the case.

l) No polygons (often useful for basic lower thirds), or lines (there is a convention in France to place a large full frame cross 240f before FFOA - line tool useful).

m) Tools/Avid title+ refers merely to the tool palette, allowing you to find if it is hidden behind other windows.   This is not clear.  Does nothing in Src/Rec mode.

n) To create a title you need to drag+drop from the effect editor, add title in the timeline doesn’t always work (either no response or ERROR: unable to add an Avid Titler+ effect) - impossible to create a title as the only thing in the sequence as you can’t create the space in the timeline to drop the effect.

o) Alt+Cmd after Cmd+L to move around doesn’t bring up the hand cursor (but still works - this is a minor issue)

p) The two icons in the top-right of the effect palette (drag points, select areas) are identical, wasn’t able to figure out what they do. Related to (f) - if is changes interaction with the objects in the monitor it should be in the toolbox.

q) With my developer hat on, under the hood, looking at the AAF, for interoperability... doesn't look amazing... some of the data (text/font names) is hidden as "Private data" in a proprietary binary format (seemingly confirming some TitleDeko heritage...), the rest is as AAF Constant Values, with many repeated property names.  Maybe just use XML as a text value, that other downstream software can parse and use.  Avid (and other companies) uses XML elsewhere in AAF (and MXF for that matter) where things don't easily fit in to the AAF datamodel. Interoperability is what sets Avid apart and where other systems fall way short.  AAF is documented - everything is there, once other manufacturers properly implement import (not always the case) - a clear interface that is easily parsed reduces bug probablity elsewhere. 

You sort of get used to how it operates, but it is very very quirky.  The Avid design team should put someone who has never used the Title+ tool but with experience of editing software as a user and observe how they get on without a manual - a lot would be learned….   It practically breaks most UI rules in the book…. Poor affordance, hidden hierarchy, no feedback from some user operations, unconventional behaviour.  Yet it was certainly beta-tested…  (eg. with respect to the accented character issue reproduced on two machines - no French beta testers???)

Maybe I’m a bit harsh, but I do think that the first impression that you have on these sorts of things is the right one.  It is possible that some of the things I was unable to do, are in fact possible - but this is the point, it should be intuitive - the manual should not be necessary, not for something as straightforward as this.   I teach in a film school and using this, I’m thinking, this is going to be a fun one to explain to first-time users….  :-(

It is a pity that with this opportunity to rethink things from scratch we didn’t get better than this.  Should be clean, well thought out and elegant.  

Don’t get me wrong, I’m testing out the other features of 2018.12 and so far very impressed, not least the possibility to make a multigroup from a sequence AT LAST with cameras that start and stop whenever!!! Super work Avid!!  but this titler….. :-(

Curious to see what everyone else makes of it!

Janusz 

I'm still having crashes when changing Workspaces and I'm wondering if MC doesn't like my video card.

We are starting to use it in our facility, but I cannot see many people taljing about it/asking questions etc.

Is there anyone out there?

Steve

On 2021.5 when I set a drive in any Media Creation tab (Capture, Titles, Import, Render etc.) and click apply to all, it doesn't. I have to individually ensure each tab is pointing to the right drive. Anyone else experiencing this?

I love the new Sequence Map. Especially when cutting long sequences of demanding linked media with no time to do a transcode it's great to be able to jump to anywhere in the sequence quickly.

It would however be a lot more useful if it was a bit more customisable.

For example, I tend to turn on Film view so I can see frames from the whole sequence in the map, but to do that I need to keep Film view on in the actual Timeline window, making it slower to move around it. Ideally I'd like to keep the Film frames visible in the Sequence Map but not in the Timeline window. Conversely, I don't need to see every audio track or clip in the sequence map—ideally I'd just turn those off and only keep them visible in the Timeline window.

In an ideal world I would like to have the option to view a sequence map of only densely packed film frames and nothing else!

Lastly, there ought to be a way of making the sequence map fill the Sequence Map window. At present, if I have only a few tracks in my timeline and empty space above and/or below it, the Sequence Map also shows a lot of empty space that isn't useful for anything (clicking on or outside a track in the Sequence Map makes no functional difference). It would be better if there was at least an option to "fill Sequence Map window" regardless of your track size in the Timeline window.

That's all!

I wanted to import media but i can't. I try to change the resolution project, i try in an other project, nothing work. 

When i try to import, i got that in the console... I don't understand. Please help me

Memory stats: physical = 16328 MB, virtual = 134217727 MB, restriction = 0 MB

WARNING: Requested LocateBuffer size 2048MB is the same as current size 2048MB.

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

WARNING: Requested LocateBuffer size 2048MB is the same as current size 2048MB.

AWin32Mixer::Open inputMixerID = 4

AWin32Mixer::Open - Failed to validate output mixer: outputMixerID 0 is invalid mixer

Created ADM Device : 1394 Audio

DirectSound ADM running on Windows OS Version Major=6 Minor=2 Build=9200

AWin32Mixer::Open inputMixerID = 4

AWin32Mixer::Open - Failed to validate output mixer: outputMixerID 0 is invalid mixer

Created ADM Device : DirectSound Audio

AlertableTimer Win32 constructor, default system clock resolution min = 1, max = 1000000

AlertableTimer Win32 constructor, default system clock resolution min = 1, max = 1000000

AlertableTimer Win32 constructor, default system clock resolution min = 1, max = 1000000

MCBootstrap::gwhoami = 30

Duplicate definition entry (not added)

Plugin definition registration failed

Avid Media Access: Device monitor successfully initialized

AVX Library V1.5

OpenGL implementation found:

vendor = Brian Paul

renderer = Mesa OffScreen16

version = 1.5 Mesa 6.4

This OpenGL implementation does not support hardware texture render

dimensions de rendu maximales : = 1920 x 1080 à 8 bits par canal de pixel

OpenGL implementation found:

vendor = NVIDIA Corporation

renderer = NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2

version = 4.6.0 NVIDIA 466.47

This OpenGL implementation supports hardware texture render

dimensions de rendu maximales : = 1920 x 1080 à 8 bits par canal de pixel

AME CPU Buffer Deallocator Registered Successfully

AME GPU Buffer Deallocator Registered Successfully

MonCon Peintres : GPU, CPU

DualCopy Engine: Qualified

Type de transfert ACPL : OCL+OOC

Type de mémoire tampon de transfert ACPL : Persistent

Mode de transfert ACPL : Overlapping Enabled

Capacité du pool de mémoire ACPL GPU :1536 Mo

Capacité de l'hôte du pool de mémoire ACPL GPU :1024 Mo

Capacité du pool privé de mémoire ACPL GPU :0 Mo

Capacité de l'hôte du pool privé de mémoire ACPL GPU :0 Mo

Capacité VRAM ACPL GPU :3072 Mo

ACPL GPU Driver: 466.47

ACPL GPU Card Model: NVIDIA GeForce GTX 1060 3GB

Newer CPU<->GPU bus speeds detected (3.7826)

AAF DLL loaded from : C:\Program Files\Avid\Avid Media Composer\AAFCOAPI.dll

AAF DLL version : 2.0.8 (102) [1]

DFM loaded. 202 entries initialized. Scripts directory 'C:\Program Files\Avid\Avid Media Composer\SupportingFiles\CodecToolkit_Config\'

Setting chained toggle /Q7Container/EnableInternalProcessing_H264:true

Setting chained toggle /Q7Container/EnableInternalProcessing_AAC:true

Setting chained toggle /Q7Container/EnableInternalProcessing_MJPEG:true

Setting chained toggle /Q7Container/EnableInternalProcessing_TIFF:true

Setting chained toggle /Q7Container/EnableInternalProcessing_JPEG:true

Setting chained toggle /Q7Container/EnableInternalProcessing_PCM:true

Setting chained toggle /Q7Container/EnableInternalProcessing_ProRes:false

Setting chained toggle /Q7Container/EnableInternalProcessing_MPEG-2:false

Setting chained toggle /Q7Container/EnableInternalProcessing_DNxHR:false

Setting chained toggle /Q7Container/EnableInternalProcessing_DNxHD:false

Setting chained toggle /Q7Container/EnableInternalProcessing_Alpha:true

Setting chained toggle /Q7Container/EnableInternalProcessing_RLE:false

Setting chained toggle /Q7Container/SupportMediaWithRoundedTrackLength:true

Setting chained toggle /Q7Container/RedirectToQ7_26_IfAvailable:false

Setting chained toggle /Q7Container/RedirectMediaWithRoundedTrackLengthToQ7_26_IfAvailable:false

Setting chained toggle /Q7Container/Disable16BitImageFormatsSupport:false

Setting chained toggle /GenericMXFContainer/MXFSuppressMCAMetadata:false

Setting chained toggle /GenericMXFContainer/OverrideUnsupportedDistinguishedFrameLayout:true

Setting chained toggle /Q7Container/TruncateMasterMobEssenceSlotsToMinumumCommonDuration:false

Setting chained toggle /Q7Container/TreatVariableFrameRateAsConstantAverage:true

Setting chained toggle /QuickTimeMediaContainer/TruncateFractionalStartOffsetsToFullFramePrecharge:true

Setting chained toggle /AMPPlugin/Enable_DNx:true

Setting chained toggle /AMAFI-SDK/DisableLoggingErrorMessagesOnContainerHandlerProbing:true

Setting chained toggle /Q7Container/RedirectMediaWithMasterMobFillerToQ7_26_IfAvailable:false

Setting chained toggle /AMPPlugin/Enable_DCP_J2K:false

Setting chained toggle /AMPPlugin/Enable_IMF_J2K:true

Setting chained toggle /AMPPlugin/Enable_J2K:true

Setting chained toggle /AMPPlugin/Enable_DV_Based:true

Setting chained toggle /AMPPlugin/Enable_CAT_AVCI:true

Setting chained toggle /AMPPlugin/Enable_H264_Proxy:false

Setting chained toggle /AMPPlugin/Enable_DNxU:true

Setting chained toggle /AMPPlugin/Enable_ProRes:true

Setting chained toggle /AMPPlugin/Enable_DNxHD_VCID:false

Setting chained toggle /AMPPlugin/Enable_CAT_DNxHR:true

Setting chained toggle /AMPPlugin/Enable_CAT_DNxHD:true

Setting chained toggle /GenericMXFContainer/SetDefaultLengthInStaticSlotComponents:true

Setting chained toggle /GenericMXFContainer/EnableRedirectionToAvidOPAtom:false

Setting chained toggle /WaveAiffReaderMovMediaContainer/AudioTimecodeUseBEXTOriginationDate:false

Setting chained toggle /AMAFI-Tiff/TiffReturnCompressedEssence:true

Setting chained toggle /AMAFI-SDK/DisableVariableFrameRateModeForTruncatedEssence:true

Setting chained toggle /WaveAiffReaderMovMediaContainer/BigEndianSmpteIdInBEXTData:false

Setting chained toggle /Q7Container/AllowARRIMediaWithLUTs:true

Setting chained toggle /AMAFI-SDK/UseFillerOnMasterMob:false

Setting chained toggle /Q7Container/AlwaysRedirectToQuickTime:false

Setting chained toggle /AMAFI-QTFF/RejectVariableFrameRateMedia:false

Setting chained toggle /AMAFI-QTFF/AllowProResRAWLinking:true

Setting chained toggle /AMAFI-QTFF/AllowProResWriting:true

Setting chained toggle /AMAFI-SDK/DisableRoundingOfOriginForAAF:false

Setting chained toggle /AMAFI/AllowH265Linking:true

Setting chained toggle /REDR3DMediaContainer/EnableIPP2:true

Setting chained toggle /AMAFI/AllowProRes4444Linking:true

Setting chained toggle /AMA/AllowProRes4444Linking:true

Setting chained toggle /AMAFI-QTFF/AllowH265Writing:true

BigBufferPool 0x000000005F3CA800:

Size: 2147483648 (2.00G)

Total Free: 2147483648 (2.00G)

Largest Free: 1476395008 (1.38G)

Memory Chunk 0x000000005F277380, ADDR=[0x00007FF316DF0000]

Size: 83886080 (80.00M)

Total Free: 83886080 (80.00M)

Largest Free: 83886080 (80.00M)

Number Allocs: 0

Max Allocs: 0

Memory Chunk 0x000000005F2772E0, ADDR=[0x00007FF31BDF0000]

Size: 117440512 (112.00M)

Total Free: 117440512 (112.00M)

Largest Free: 117440512 (112.00M)

Number Allocs: 0

Max Allocs: 0

Memory Chunk 0x000000005F277B00, ADDR=[0x00007FF322DF0000]

Size: 117440512 (112.00M)

Total Free: 117440512 (112.00M)

Largest Free: 117440512 (112.00M)

Number Allocs: 0

Max Allocs: 0

Memory Chunk 0x000000005F2773D0, ADDR=[0x00007FF329DF0000]

Size: 117440512 (112.00M)

Total Free: 117440512 (112.00M)

Largest Free: 117440512 (112.00M)

Number Allocs: 0

Max Allocs: 0

Memory Chunk 0x000000005F276BB0, ADDR=[0x00007FF330DF0000]

Size: 117440512 (112.00M)

Total Free: 117440512 (112.00M)

Largest Free: 117440512 (112.00M)

Number Allocs: 0

Max Allocs: 0

Memory Chunk 0x000000005F276B10, ADDR=[0x00007FF337DF0000]

Size: 117440512 (112.00M)

Total Free: 117440512 (112.00M)

Largest Free: 117440512 (112.00M)

Number Allocs: 0

Max Allocs: 0

Memory Chunk 0x000000005F276AC0, ADDR=[0x00007FF33EDF0000]

Size: 1476395008 (1.38G)

Total Free: 1476395008 (1.38G)

Largest Free: 1476395008 (1.38G)

Number Allocs: 0

Max Allocs: 0

MSM directories:1

LocalMDB::LoadMobsFromMDB() inCallback=0000000000000000 sourceOnle=FALSE

mediaDirPath phyMobs logMobs

"C:\Users\Public\Documents\Avid Media Composer\Avid_MediaFiles\" 0.02 sec

total time=0.02 mobs=0

Media Drives:

(C:), OSVolID = 67, 233784336 totalKB, 107775944 freeKB, 107565445 realFreeKB

SSD (D:), OSVolID = 68, 488383484 totalKB, 455622472 freeKB, 454732585 realFreeKB

HDD 2To (E:), OSVolID = 69, 1953497084 totalKB, 1679348348 freeKB, 1676068371 realFreeKB

Maxtor (F:), OSVolID = 70, 3906885628 totalKB, 1986174304 freeKB, 1982295058 realFreeKB

COM2: error (2) Le fichier spÈcifiÈ est introuvable.

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

MAX_INDEXES_TO_READ set to 10240

MXF Indexes in Memory changed to 524288000: Old Size 524288000

In Init ARO Cmds

MTSC state = 0The single frame player will be built for a length of 3600 frames

Viewer: OpenCL and OpenGL are not compatible: No OpenCL devices

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

WARNING: Requested LocateBuffer size 2048MB is the same as current size 2048MB.

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

WARNING: Requested LocateBuffer size 2048MB is the same as current size 2048MB.

Destroying Bin Container without closing

qm2b is enabled

The default render wait time is 50

AS11: writeback is not supported for this type of project.

Supported projects:

576i (25i PAL)

486i (30i NTSC)

1080i50

1080i59.94

720p50

720p59.94

User abort of batch import.

Batch imported 0 of 1 clips

Changing project type to 720p/25

Avertissement : la conversion du chemin de UTF16 vers MBCS a échoué.

Chemin MBCS interprété comme : E//SHOWREEL/Music/10 ?µ?y 10.mp3

Avertissement : la conversion du chemin de UTF16 vers MBCS a échoué.

Chemin MBCS interprété comme : E//SHOWREEL/Music/10 ?µ?y 10.mp3

Avertissement : la conversion du chemin de UTF16 vers MBCS a échoué.

Chemin MBCS interprété comme : E//SHOWREEL/Music/10 ?µ?y 10.mp3

Avertissement : la conversion du chemin de UTF16 vers MBCS a échoué.

Chemin MBCS interprété comme : E//SHOWREEL/Music/10 ?µ?y 10.mp3User abort of batch import.

Batch imported 0 of 1 clips