Field guide for editors
Media Composer transcribes every clip in every bin, indexes every word anyone says in your project, and runs a separate transcode and render engine outside the application. All of it is on by default. On a busy newsroom workstation it competes with playback for the same CPU and the same disk, and you feel it as stutter, slow bin opening and lag on the timeline.
This guide explains what each background process actually does, then shows you every place it can be switched off, from a single bin all the way to a setting that applies to every project on the machine.
Part one
Six separate things, and they are not all the same animal. Two live inside Media Composer, two run as their own programs beside it, and two are system level. Knowing which is which tells you where to go to switch each one off.
This is the big one. Since version 2023.8 Media Composer replaced the old phonetic search with real AI transcription that runs entirely on your machine, with no internet connection. When media arrives in a project, the indexer reads the audio of every clip and writes a full text transcript into a database, so that later you can type a word and jump to the moment somebody said it.
Avid states plainly in its own release notes that indexing is a resource intensive operation which may impact the performance of Media Composer. On a newsroom machine receiving fresh material all day, it never really finishes, because more media keeps arriving.
Feeds PhraseFind AI, ScriptSync AI and the Transcript Tool. If you never search for spoken words and never cut from a transcript, you are paying for something you do not use.
By default Media Composer will create a transcription for all media in a project. Avid acknowledges this is often wasteful, because music, sound effects and camera media without usable dialogue gain nothing from being transcribed. Every bin you leave included is more audio queued for processing.
From version 2024.6 onward you can include or exclude individual bins, and the Bin Container sidebar tells you the state of each one at a glance.
Controlled in three places: Project settings, the Transcript Settings window, and a right click on any bin.
A separate program that starts with the computer and keeps running whether or not Media Composer is open. It is the engine behind background transcode, background consolidate, background render and Dynamic Media Folders. Anything you tick as a background job is handed to this service and chewed through while you edit.
You control it from an icon in the Windows taskbar or the macOS menu bar, not from inside Media Composer. The same icon opens the Background Queue window, which is where you find out whether something is silently working through a list of jobs right now.
Process name on Windows: AvidBackgroundServicesManager.exe. Formerly called Avid Editor Services Manager.
Watch folders. You point one at a directory, and anything dropped there is ingested and transcoded automatically against a profile, without anybody pressing a button. Useful in a dailies workflow, pure overhead if nobody set it up on purpose. It depends on Background Services, so stopping those stops this too.
Not available on macOS Catalina and later, so on a modern Mac this one is already off.
Launches at login, sits in the background, handles your Avid account, product updates, marketplace feeds and notifications. It is the lightest of the six, but it is also the one most people are surprised to find running, because it offers no visible option to stop starting itself.
Warning: on subscription and floating licences, Avid Link is part of how the licence is checked. Do not remove it on a facility machine without asking your systems engineer first.
Scans and catalogues media on storage so that editing systems can find it. On a standalone workstation with local drives it does very little. On a facility connected to NEXIS or MediaCentral it is load bearing, because it is how shared media gets discovered at all.
If your workstation sees shared workspaces, treat this as untouchable and let the engineering team decide.
Part two
Work outward, from the narrowest setting to the widest. The first four are ordinary settings inside Media Composer and are yours to change. The last three reach outside your project, so read the caution on each before you touch them on a station that is not your own.
Two checkboxes here do most of the work, and they survive for the life of the project. The first stops transcription from stealing cycles at exactly the moment you need them, which is while your hands are on the keyboard. The second stops the pile of work growing every time somebody makes a bin.
Music, effects, graphics, mute camera material, archive and stock. None of it benefits from transcription, and all of it queues by default. Excluding a bin is instant and the sidebar labels the result, so anyone sitting down at the station can see the state without opening a menu.
This is the switch Avid points to in its own release notes when performance suffers, and it is the one most editors never find, because it hides behind a small gear in the bottom corner of a window nobody opens. Stopping the indexer halts transcription work without touching any other service.
Transcode, consolidate, render and watch folders all run through a service that lives outside the application. Because it is a separate program, quitting Media Composer does not stop it, and it will happily keep working through a queue while you think the machine is idle.
There are two ways in, and they control the same service. The taskbar route works even when Media Composer is closed. The in application route is the one that matters here, because only that window holds the checkboxes that decide whether the service starts again tomorrow morning.
| Control | What it does |
|---|---|
| Start | Immediately starts the background services if they are currently stopped. |
| Stop | Immediately stops the background services if they are currently running. |
| Pause | Pauses the services for a set length of time. If the pause runs out while you are playing, Avid extends it. Quitting the application clears the pause and the services resume. |
| Always Start at Launch | Starts the services whenever Media Composer opens. Clear this one. |
| Always Stop upon Exit | Stops the services when you quit Media Composer. Tick this one. |
| Enable Pausing of Background Service | Lets the services pause automatically during critical operations, which Avid lists as playback, capture and use of an Artist surface. |
Everything above is per project or per session, which is why the problem keeps coming back. Media Composer solves this with Site Settings. When the application opens a new project it reads the Site Settings file first and loads whatever it finds there, and only then loads the project and user settings that were not already covered. Put your transcript choices in Site Settings and every project created on that machine inherits them.
If you want a guarantee rather than a setting, you can take the plug-in out of the application so there is nothing left to run. Media Composer loads its AVX2 plug-ins from a folder on disk, and a plug-in that is not in that folder cannot be loaded. Quit Media Composer completely before you start.
If a station still shows background activity after everything above, the remaining levers are at system level. These are heavier, they are the ones most likely to cause a support call later, and on a facility machine they belong to the engineering team rather than to you.
Part three
Do not trust a menu click. Three quick checks tell you whether the machine is genuinely quiet.
| Check | Where | What quiet looks like |
|---|---|---|
| Indexer state | Edit > Find | The indicator beside PhraseFind AI Index is red, meaning indexing is stopped. |
| Bin state | Bin Container sidebar | The bins you excluded read Transcription Off in the column beside the name. |
| Background queue | Taskbar or menu bar icon | The Background Queue Window is empty and the service reports stopped. |
| Services status | Tools > Background Services | Status reads Inactive. The taskbar icon is grey, which means stopped. Green means active and orange means paused. |
| Watch folder activity | Timeline progress indicator | Grey means the background services are suspended. A spinning icon means processing is still happening. |
| Processes, Windows | Task Manager | No sustained CPU from AvidBackgroundServicesManager.exe or the transcode engine while you are not exporting. |
| Processes, macOS | Activity Monitor | Search for Avid and confirm nothing is holding CPU when Media Composer is sitting still. |
| Real world test | Your timeline | Import a fresh batch of rushes and scrub immediately. Before the change the machine hesitates, after it should not. |
Part four
Nothing here is destructive and every step reverses. If a documentary job arrives where searching an interview by word is genuinely worth the CPU, turn it back on for that project and leave the rest of the room alone.
| To undo | Do this |
|---|---|
| Indexing stopped | Edit > Find, gear icon, then Start PhraseFind AI Indexing. Indexing resumes and works through the backlog. |
| Bin excluded | Right click the bin and choose Include Bin in Transcription. |
| New bins not enrolled | Transcript Settings, tick Include all new bins in transcription again. |
| Background Services stopped | Tools > Background Services, then Start. Or click the taskbar or menu bar icon and choose Start. |
| Services no longer start at launch | Tools > Background Services, tick Always Start Avid Background Services at Launch again. If the taskbar icon has vanished entirely, this is also how you get it back, after a restart of the application. |
| Plug-in removed | Quit Media Composer, put PhoneticIndexNN.avx back in the AVX2_Plug-ins folder, and relaunch. |
| Transcripts deleted | They regenerate from the media, so this costs processing time but no data. Use Manage Transcripts to see what exists. |
| Site Settings changed | Remove the copied settings from the Site Settings window, and new projects go back to Avid's defaults. |