Organize Module

Applying changes

On the second wizard page, Session Settings, the forward action reads Organize. Nothing is ever applied silently: the button opens a confirmation dialog, and only after you confirm does the job run, through the queue like every other fMusic job.

The confirmation dialog

The dialog is titled Organize a Pro Tools session? and summarizes what is about to happen. When lanes were removed in the editor, it lists the deletions explicitly, for example Deletes 2 tracks from Pro Tools: Kick, Snare. (with more than three, only the count is shown). Confirm with Organize N Tracks or go back with Keep Editing.

Confirming with Organize queues the job, starts it immediately, and takes you to the Processing screen. Add to Queue, next to it, queues the job without running it and returns you to Home, so several sessions can be organized in one unattended run later.

Only changes are applied

Organize compares the editor against what it loaded. Tracks are matched by the name they loaded with, so a rename in the editor becomes a rename in Pro Tools, and a track whose name did not change is not renamed at all. Colors are applied in place on the existing tracks, and the editor's lane order becomes the session's new track order. A lane you removed becomes a track deletion; audio files you added in the editor are imported as new tracks.

Deleting tracks

Deletions carry a safety rule: they run only against the same session the changes were read from. If a different session is open in Pro Tools when the job runs, fMusic refuses to delete anything and reports The session open in Pro Tools ("X") isn't the one these changes were read from, so fMusic won't delete tracks in it. Reopen "Y" and organize again. Only audio tracks actually present in the session are deleted.

What happens in Pro Tools, step by step

The job applies your changes in a fixed order:

1. Connect to Pro Tools and verify every routing destination against the session before anything is touched. A destination that does not exist stops the job before any change is made. (In Match template mode, the template's session data is imported first.)
2. Delete the tracks removed in the editor.
3. Merge split stereo pairs (.L/.R) into stereo tracks. Merging is best-effort: if one side of a pair is no longer in the session, that pair is skipped with a warning instead of failing the job.
4. Rename, only where the name changed, and recolor the existing tracks in place.
5. Import the tracks added in the editor.
6. Recall Track Presets (Track preset mode) on existing and added tracks.
7. Route every track to its destination.
8. Apply track height, run Strip Silence only on the tracks added in the editor (existing clips are never cut), and set the session tempo.
9. Reorder the tracks to match the editor, always the last step.

While the job runs, its card in the queue shows each phase as a checklist: Deleting removed tracks, Merging stereo pairs, Organizing tracks, and so on. When it finishes, the card reports anything that was skipped, refused, or not verified, so a partial result is never silent.

Stopping a run

Stopping an Organize job mid-run asks Stop organizing? and warns that Changes already made in Pro Tools aren't undone. Deletions happen near the start of the run and there is no rollback, so stop early or let the job finish. For where Organize fits and what it is for, see What is Organize?.