Media Composer on NEXIS
Shared storage reference

Media Composer on NEXIS without the 3am crash

Compatibility and crash-avoidance reference for editors, assistants, and facility engineers. Two halves: what Media Composer does under shared storage, and what the storage does to Media Composer. Both matter — the second half only exists because of the first.

Built from the Avid NEXIS 2026.6.0 readme (22 Oct 2026) and the Media Composer 2025.12 readme

The version trap

01

Three things have to agree: the Media Composer build, the NEXIS client, and the NEXIS server. Get the order wrong and you either break bin locking outright or start writing inconsistent media — bins and sequences first, because they are rewritten constantly.

Clean combination Media Composer 2025.12 on NEXIS 2025.5.7 with a matching client — nothing on this page trips.

The server may be newer than the client; that direction ships server-only fixes. The client must always satisfy the Media Composer build, so it goes up before the app does.

Server ↓ / Client →2023.x2024.x2025.x2026.x
2023.xoutoutoutout
2024.xoutnot rec.not rec.not rec.
2025.5.7outnot rec.YY
2026.xoutnot rec.YY
Y supported out no longer supported not rec. works, don't build new on it

Table shows families only. Everything from 2022 down is out of support and collapses into one "out" bucket in the evaluator, so the dropdowns are the only place the detail lives.

Media Composer crash bugs

02

Faults in the application itself, all fixed in 2025.12 or later. They are here because they are what people actually hit mid-session — and because running an older build reintroduces every one.

Critical

Crash on macOS when bins are renamed

SSENG-44555

Projects on NEXIS crash Media Composer on a bin rename. The most common way an assistant kills an editor's session.

Fix — rename with the bin closed, or on a local copy. Alphanumerics, underscores, hyphens, dots only.
Critical

Memory leak from repeated access to SMB mapped drives

MCCET-6023

Domain environments leak memory every time a mapped network drive is touched. Long sessions degrade until the app dies. Directly relevant if you map letters instead of mounting through Client Manager.

Fix — 2025.12+, and mount workspaces via Client Manager.
Critical

Crash switching workspaces with the Project window open

MCCET-6131

Edit to Color and back with the Project window up and the app goes down. Editors hit this constantly on finishing shows.

Fix — 2025.12+, or close the Project window before switching.
Critical

Launch crash on Windows with Enterprise roles applied

MCCET-6017

Access violation in Qt6Core.dll at launch on 2024.12.1. The suite is dead on arrival.

Fix — 2025.12+.
High

Crash nudging clips with the Markers window docked top-left

MCCET-6043

Specific to that dock position, which is where a lot of people put it.

Fix — 2025.12+, or dock the Markers window elsewhere.
High

Crash during audio transcription

MCCET-6033

Transcription crashes on 2025.6. Transcripts on long takes are the obvious trigger.

Fix — 2025.12+. Transcribe in shorter chunks on older builds.
High

Uncontrolled resource consumption from Elasticsearch, then crash

MCCET-5902

The search backend eats the machine and the app falls over. Often mistaken for a storage problem because playback degrades first.

Fix — 2025.12+. Pause PhraseFind AI indexing when editing gets sluggish.
High

Unresponsive on complex AAF import

MCCET-6000

Checking out or importing a heavy AAF hangs the app. Common on turnover from other departments.

Fix — 2025.12+.
High

Freeze or crash applying animated effects to clips with alpha

MCCET-5360

Intermittent, which makes it hard to prove. Hits matte-key-heavy comps.

Fix — 2025.12+. Render alpha work before stacking animated effects.
Medium

Crash loading a second sequence in Play Standby

MCCET-5810

Load one sequence, enter Play Standby, load another.

Fix — 2025.12+, or leave Play Standby first.
Medium

Crash exporting markers

MCCET-5895

Marker export takes the app down. Painful when markers are the deliverable.

Fix — 2025.12+.
Medium

Crash importing ProRes MXF from ARRI Alexa 35

MCCET-5628

Direct crash on import of Alexa 35 ProRes MXF.

Fix — 2025.12+.

Standing rule

Pin one qualified build per suite and stop drifting. Most of the list above is one version number away from solved, and mixed builds across a floor make every crash report ambiguous.

Storage faults that surface as MC crashes

03

These live in the NEXIS client and server, but the visible symptom is Media Composer falling over or losing media.

Critical

MXF corruption on mirrored workspaces during simultaneous ingest

SSENG-47292

Ingest devices set to Hi-Resolution client type writing into a mirrored workspace starve resources. Portions of the file get zeroed. In Media Composer: corrupted frames, audio dropouts, Consistency Check Failure, Assertion Failed.

Fix — no Hi-Resolution client type on ingest devices into mirrored workspaces, or serialise the writers.
Critical

MC 2026.x needs client 2026.6.0 for bin locking

NEXIS readme, MC compatibility

MC 2026.x changed security handling. On Ultimate, bin locking and shared projects break against an older client. 2026.6.0 is also required for Media Composer v2026.8.0.

Fix — client 2026.6.0 is mandatory before MC 2026.x. Client first, then app.
Critical

Kernel panics on macOS Sequoia clients

SSENG-45072 · 43073

Panics on Sequoia. The Sonnet Twin10G SFP+ with its kext driver panics on writes to NEXIS; the Apple dext does not.

Fix — 15.7.1+, and unload the Sonnet kext.
Critical

Server reboots during drive rebuilds

SSENG-47440 · 47216

Out-of-memory from high memory locking reboots the system repeatedly during a rebuild. Also: System Director asserts under sustained rising write load. Every client drops mid-session.

Fix — 2026.6.0. Throttle non-critical ingest during rebuilds.
High

Firewall on macOS 15.3+ breaks reads and writes

SSENG-44726

Socket send failures cause read and write errors. Intermittent, so it gets blamed on the media.

Fix — 15.7.1+, or disable the firewall until you can update.
High

Incomplete file copies and sluggish Finder on Sequoia

SSENG-44926

Finder copies finish short after the 2025.x client upgrade. The copy looks done and the media is not there.

Fix — verify by file count before calling media online.
High

Workspace delete cascades and restarts the System Director

SSENG-46479

On 2025.2.2, deleting a workspace recurses through directories, throws an assertion, and restarts the System Director.

Fix — schedule workspace deletion outside edit hours.
High

CrowdStrike: panics, then dropped frames

SSENG-39564 · 40594 · 40601

7.14–7.18 panics the client. Below 7.24 it delays I/O enough to drop playback frames. Avid tests against 7.37.

Fix — 7.37 with process exclusions for Media Composer and NEXIS binaries.
High

Defender blocks deletes, Send-to-playback fails

SSENG-40046

Defender holds a handle while MC deletes on a drive-letter mount. EDR path exclusions are not supported for drive letters at all.

Fix — process exclusions, set by IT. Never path exclusions.
High

Windows updates the NIC driver, strips NEXIS settings

SSENG-2571

Automatic driver updates remove the adapter settings the client depends on. Fine yesterday, dead today.

Fix — Device Installation Settings → No. Lock drivers in the image.
Medium

Client Manager stops listing workspaces on Windows

SSENG-45111

After 2025.5.3, workspaces vanish from the list. Still mounted, just invisible, so operators think they were deleted.

Fix — move off 2025.5.3.
Medium

Workspace duplicate strips other users' permissions

SSENG-46663

Since 2025.5.3, duplicating then editing permissions removes access for everyone you did not touch. Assistants lose workspace access silently.

Fix — save the duplicate, then edit permissions as a second pass.

Media Composer settings that matter on shared storage

04

Defaults are tuned for local disks. These are the ones to change or verify per suite.

Bin sharing toggle

If you get the "Enable 3rd Party Emulation" warning, the dialog is not enough. Also set Settings → Project → General → "Bin Sharing on 3rd party storage emulating Avid NEXIS/ISIS." Without it locking silently does nothing.

Disk cache

Proxy playback fails when Disk Cache is off or 0. NEXIS EDGE users must set 1GB or more.

PhraseFind AI indexing

Indexes in the background and is resource-heavy enough to degrade playback. Pause it from the Find window gear → Pause All Indexing when a cut gets sticky.

Render and transcode windows

Background render, background transcode and DMF all compete for the same bandwidth as playback. On a loaded group, stagger them instead of letting every suite render at once.

Project location

Projects belong on the workspace. A local project file defeats locking and then gets written back over the shared version.

Distributed Processing

Transcode and mixdown jobs to DNx fail on DP 2024.10.1 and earlier. Keep DP matched to the MC build.

After the crash

05

What to do in order. Skipping ahead is how a recoverable session becomes lost media.

  1. Reboot before reopening the project. Stale bin locks and a half-written media database both clear on restart.
  2. Check the workspace is actually mounted. A workspace that dropped mid-conform reports every clip offline even though the storage is technically fine.
  3. Delete the media database files before relaunch if media looks wrong. Let Media Composer rebuild rather than working on a suspect index.
  4. Expect MOB errors. "Can't delete MOB because it is still being referenced" that blocks every operation in the bin usually means a rebuild, not a repair.
  5. Open a copy of the bin, not the bin. Confirm it loads before letting anyone else near it.
  6. Log the build numbers — client, server, MC, OS, endpoint sensor. A crash report without those is untriageable.

Never do this

Two editors opening the same sequence in two different projects, then both saving. Locking protects bins, not sequences pulled across projects. Pick an owner.

Bin locking rules

06

Most "corrupt bin" reports are locking violations, not storage faults.

  1. Never copy or move a bin with Finder or Explorer while it is open. Use MC's own bin operations. Copying underneath a running app is the classic corruption path.
  2. Close the bin before renaming it. On macOS, renaming with it open crashes the app (SSENG-44555).
  3. Respect read-only. A locked bin means you are on a copy. Save under a new name or wait.
  4. Close bins you are done with. An open bin holds its lock until the app quits.
  5. After a hard crash, assume stale locks. Reboot before reopening.
  6. Keep the tree sacred. Media in Avid MediaFiles/MXF/<n> and nowhere else. Stray files or renamed numbered folders force a rebuild mid-session.
  7. Cap folder size. 10,000 files per folder. Past it, listings slow then fail — roll a new MXF folder on long shows.

Withdrawn releases

07

2025.5.0 — withdrawn, not recommended for any system.

2025.2.0 — withdrawn, not recommended for any system.

2023.7.0 — withdrawn. Do not upgrade an on-prem system to it.

2025.5.5 — Storage Manager assertion causes Media Pack disconnections. Superseded by 2025.5.7, the minimum recommended on-prem release.

Also avoid, without being formally withdrawn: 2025.5.3 (workspace list and permissions bugs), 2025.2.2 (workspace delete cascade). Everything from 2022 down, including the 2019 and 2018 lines and the older ISIS 6.x/7.x era, is out of support entirely. Downgrades are unsupported in all cases.

Pre-flight checklist

08

Before every build, upgrade window, and show turnover. Progress saves locally.

0 of 13 complete

Support floor

09

2025.5.7 — minimum recommended on-prem NEXIS release.

MC 2025.12 — minimum build for the crash list above to be solved.

10,000 files per folder · 10 clients per High Performance group · 255 bytes per path component.

macOS 26.5 / 15.7.1 / 14.x · Windows 11 25H2–23H2 · Server 2025–2019 — current client floor. Monterey is gone from MC as of 2025.6.

ASCII only for LDAP · Rx flow control on every port facing an engine or client.