Organize Module

How Organize reads your session

When Organize opens a session, fMusic reads it from Pro Tools over PTSL: the track list and each track's clips, loaded into the editor as lanes. The read never modifies the session. Changes happen only later, when you apply them.

What you see during the read

While the session loads, a progress HUD sits above the timeline. Opening session in Pro Tools… covers the open; if it takes more than a few seconds the HUD reassures you that a large session, or a cold launch of Pro Tools, can take a while without anything having gone wrong. Analyzing track N of M… covers recognition: each track is classified from its audio, and long tracks take longer. A Cancel button is shown whenever the current phase can be stopped safely.

Recognition runs on the session's clips

Instrument recognition (AI-R) classifies each track from its audio, on device, using the same CoreML model as Import. When the model is not confident about a file, the verdict falls back to the name, which in a session read is the clip's name, not the track name. Clips with generic bounce names such as Audio 1_01 carry no instrument information, so they come out Unclassified: gray, uncategorized, and untouched by category routing until you assign them yourself.

The verdict only sets a lane's starting category. You can recategorize any lane by hand afterward: from the lane's context menu in the editor (Category), or by right-clicking rows in the routing table on the Session Settings page (Change Category).

Recognition can be turned off in Settings ▸ General with Use intelligent track recognition (on by default), and the switch governs Organize and Import alike. It applies to files analyzed after the change: tracks already analyzed keep their verdict. With recognition off, categories come from clip names alone.

Verdicts never repeat

Verdicts are stored per audio file: two tracks playing the same file share one verdict, and reopening a session never re-runs the model on files it has already analyzed. You can leave a session and come back without paying the recognition cost again, and without any risk of tracks being reclassified between visits. A file the model cannot read does not abort the rest of the batch.

Sessions built from an AAF

AAF is the file format video editors use to hand audio to the sound team. A Pro Tools session built from an AAF structures its media in a way fMusic cannot map yet, and the read refuses it with a plain error instead of loading empty lanes. It shows up in one of two ways:

• The error card AAF sessions aren't supported, always accompanied by Your Pro Tools session was not modified.
• The session opens but has no readable clips: Opened "…", but couldn't read its clips — the session may use media fMusic can't map yet (e.g. an AAF import).

Once the session is loaded, everything that follows works like an import: see applying changes for how your edits are written back.