Play Mode track list out of sync with Setup Mode (Ghost Tracks & Divisi)

Dear Dorico Team,

I am currently realizing Antonín Dvořák’s Symphony No. 9 (2nd movement, Largo) entirely within Dorico Pro 6.2.30, hosted with Vienna Ensemble Pro 8 (using VSL Synchron Duality Strings, Studio Solo Strings, and Synchron Orchestra).

During score preparation and voice allocation, I encountered two significant issues regarding Play Mode synchronization and orchestral Divisi playback routing:

1. Persistent Ghost Tracks in Play Mode after deleting Divisi and Players

In Setup Mode, my player list is clean and structured. In Write Mode, I had previously tested a divisi section for a solo desk and later completely removed it (deleting the Solo signpost, which restored the staff back to a single line without any divisi signposts remaining in the score).

However, Play Mode (Track Inspector) completely fails to synchronize with Setup and Write Mode:

Screenshot 1: Here is the clean and properly organized player hierarchy in Setup Mode, showing the section players alongside the dedicated solo single players.

(

Screenshot 2: Here is the resulting desynchronization in Play Mode: obsolete deleted players (such as "Violine 2 neu") as well as cleared divisi staves ("Notenzeile (a)" and "(b)") permanently persist as ghost tracks.

As shown in Screenshot 2:

  • The cleared divisi staves Notenzeile (a) and Notenzeile (b) permanently remain visible in the Play Mode track list.

  • An obsolete, already deleted player ("Violine 2 neu") lingers as a ghost track alongside the active "Violine 2".

  • Saving the project, closing Dorico, and reopening the file does not purge these dead tracks or rebuild the track hierarchy.

Changes made in Setup Mode and Write Mode should automatically and reliably force a refresh of the Play Mode track inspector.

2. Playback Architecture Dilemma: Desk Solo vs. Tutti Routing in Divisi

When using Dorico’s native Divisi feature for orchestral desk solos (e.g., 1 Solo Desk / Tutti rest of section):

  • Hierarchically, Staff (a) continues the playback routing of the primary section preceding the divisi.

  • If Staff (a) is assigned to a Solo VST instrument in Play Mode, the entire Tutti section preceding the divisi is routed through that Solo patch.

  • If Staff (a) is assigned the Tutti section patch, the solo line must be written on Staff (b) (the lower staff), which fundamentally violates orchestral engraving standards where the solo desk must always be the top staff.

  • Because of this routing conflict, I had to abandon the Divisi feature entirely and resort to creating separate Single Players (Violine 1 Solo, etc.) alongside the Section Players. A dedicated routing mechanism is needed that allows Divisi staves to be assigned to independent VST channels without corrupting the pre-divisi tutti playback.

Application for the Beta Testing Program

I am an active, classically trained conductor, composer, and pianist. My daily workflow involves large-scale virtual orchestration (Dorico Pro 6.2, VEP 8, complex VSL setups) directly within Dorico without an intermediate DAW. Because I constantly work at the intersection of complex notation, voice allocation, and multi-endpoint playback, I regularly encounter edge cases and structural routing bottlenecks.

I would be very glad to contribute to the future development and quality assurance of Dorico as a Beta Tester. Please let me know how to apply or whom to contact regarding the Dorico beta program.

Best regards,

Stefan Meier

There are many threads discussing this limitation. To summarise:

  • Divisi only works for section players, not solo players
  • When Dorico creates a solo/gli altri division, the solo line continues the original non-divisi staff (it does not add a solo line above the original. It adds the gli altri line below)
  • If you want to hear accurate playback of the solo division, you must enable independent voice playback, reserve one voice for the solo, and route it appropriately.

More generally. If you remove a staff, but do not delete the music it contained, then it still exists! This is very useful for notating specific ornaments and is probably the source of your ghosting?

Empty voices are only removed when closing a project.

These apparent differences are a caused by the technical separation of the playback engine from the notation engine.

Thank you for your response. However, having investigated this further with detailed testing, the problem runs significantly deeper than just “hidden notes on removed staves.”

There is an evident architectural synchronization breakdown between Setup Mode, Write/Engrave Mode (Score view), and Play Mode (Track Inspector). Furthermore, the current handling of deleting players and linked events creates serious workflow traps.

Below is the complete breakdown of the issues, along with photographic evidence:

1. Desynchronization across Setup Mode, Score View, and Play Mode

Changes made in Setup Mode fail to propagate to the score and playback engines, even after saving, closing, and reopening the project:

A) Setup Mode vs. Staff Labels in Score View: In Setup Mode, the players were renamed and cleanly organized. For instance, the dedicated solo player was renamed to “Violine 1 Solo” (Short name: “Vln 1 Solo”).

However, looking at the actual score in Page View, Dorico completely ignores these names and structure:

As seen in Screenshot 3:

  • The solo players do not adopt the specified player names; instead, generic/default English names like "Violin" and "Double Bass" persist.

  • Obsolete, intermediate staves like "Violine 2 neu" are still drawn in the score margin.

  • The nomenclature in the score is completely disconnected from the player definitions in Setup Mode.

B) Ghost Tracks persisting in Play Mode: The Play Mode track inspector exhibits the exact same disconnect:

  • Even though the divisi was removed in the score (the solo signpost was deleted, reverting the music to a single staff), Play Mode permanently retains Notenzeile (a) and Notenzeile (b).

  • The deleted intermediate player "Violine 2 neu" lingers in the track tree.

  • A full application restart does not purge these dead endpoints. Setup Mode, Score View, and Play Mode should always remain strictly in sync.

2. Workflow Pitfall: Deleting Players & The “Linked Dynamics” Trap

Currently, cleaning up an erroneous or duplicated player that contains music is needlessly hazardous. Coming from a DAW environment like Cubase, deleting a track/player should be a clean, atomic operation protected by an explicit confirmation prompt (“Do you really want to delete this player and all associated events?”).

In Dorico, the manual cleanup before deletion reveals a critical flaw: Linked Dynamics.

  • When dynamics are duplicated or linked across the string section (e.g., via Alt+M or multi-staff input), Dorico links them semantically.

  • If a composer attempts to manually erase the music on a redundant staff prior to deleting the player, deleting those dynamics inadvertently wipes out the dynamics across all linked section players in the entire score.

  • Restoring or unlinking them requires tedious, bar-by-bar manual repair.

  • Feature Request: Deleting a player must automatically sever/unlink all shared dynamic links in the background, cleanly removing the player and its contents without corrupting the dynamic markings of the surviving orchestra.

3. Desk Solo vs. Tutti Routing in Divisi

Using Independent Voice Playback (IRV) across separate voice IDs remains a fragile workaround rather than a proper orchestral workflow. When creating a standard concertmaster or desk solo, scoring convention dictates that the solo desk occupies the top staff Staff (a).

Because Staff (a) permanently inherits the pre-divisi tutti routing, assigning a solo VST patch to Staff (a) forces the preceding tutti section through the solo patch. Forcing composers to split notation into different voice directions or banish the solo to the lower staff Staff (b) just to get correct sample playback contradicts professional scoring practice. A native mechanism to assign independent VST channels to divisi staves without altering the main tutti route is essential.

Application for the Beta Testing Program

I am an active, classically trained conductor, composer, and pianist. My primary production setup centers on realizing complex orchestral literature (such as Dvořák’s 9th Symphony) directly in Dorico Pro 6.2 hosted with Vienna Ensemble Pro 8 (VSL Synchron Duality Strings, Studio Solo Strings, Synchron Prime) without intermediate DAW tracking.

Because I rigorously stress-test Dorico’s score-based playback, multi-endpoint routing, and voice allocation on large-scale templates, I encounter these structural bottlenecks firsthand. I would be delighted to assist the development team as an official Beta Tester for upcoming maintenance builds and major releases. Please let me know the appropriate contact channel or application process for the Dorico beta program.

Best regards,

Stefan Meier

You can choose to show Instrument names or player names as staff labels.
You seem to have instruments name in Layout setting, have a look here how to show player names

Perhaps you are confusing Player Names and Instrument Names? (but there may be a language problem here)

Setup shows Player Names. Play mode shows Instrument names. The distinction is important, because solo players can hold more than one instrument.

Also, there should be no need for your setup to show separate solo players for this score. Dvorak 9 can be setup with only the normal section string players and using the divisi feature to create the solo divisions where needed.

Title: Feedback: Default Naming Sync across Modes (UX Philosophy), Ghost Tracks, and Divisi Playback Routing

Dear Dorico Team, dear Community,

Thank you to @TonH and @Janus for taking the time to explain the current mechanics.

While @TonH’s tip regarding the Layout Options switch explains the technical reason for the score labels, it highlights a fundamental usability question regarding Dorico’s design philosophy.

1. UX Philosophy: “Intuitive Defaults” vs. “Specialist Workarounds”

Dorico’s greatest achievement—and the reason so many of us embraced it after decades with legacy tools like Finale or early Sibelius—has always been its commitment to modern, intuitive workflows that remove unnecessary friction and protect the composer from hidden pitfalls.

From an ergonomic software design standpoint:

  • The Default Expectation: When a user creates and explicitly names a player in Setup Mode (e.g. "Violine 1 Solo"), the natural expectation is that this custom name establishes the primary identity of that staff across the entire project. Having Dorico silently default to hardcoded, generic instrument labels in English ("Violin", "Double Bass") in the score margin feels counterintuitive.

  • Defaults vs. Exceptions: Overriding a player name with an abstract instrument name should be an opt-in setting for edge cases, not the default stumbling block for everyday scoring.

  • The Disconnect in Play Mode: More crucially, while the score layout offers an override to display player names, Play Mode provides no such option at all. The Track Inspector strictly displays generic instrument names. When managing dedicated desk solos or chamber groups within an orchestral score, seeing identical generic tags ("Violin", "Viola", etc.) without their Setup Mode context creates unnecessary confusion.

A synchronized nomenclature across Setup, Write/Engrave, and Play should be the out-of-the-box standard, with divergence reserved for specific exceptions.

2. Native Divisi vs. Professional Sample Hosting (VEP 8)

To address @Janus’s remark that separate solo players shouldn’t be needed for Dvořák 9:

This holds true for pure engraving or integrated engines like NotePerformer, but it breaks down when hosting high-end multi-timbral libraries directly in Vienna Ensemble Pro 8 (e.g. VSL Synchron Duality Strings Con Sordino for tutti, VSL Studio Solo Strings for desk solos):

  • Staff (a) permanently continues the channel routing of the pre-divisi tutti section.

  • Routing Staff (a) to a Solo patch forces the preceding tutti section through that solo instrument.

  • Placing the solo on Staff (b) just to get correct playback routes the solo to the lower staff, conflicting with orchestral notation standards.

  • While Independent Voice Playback (IRV) exists, using dedicated single players routed to their own VEP channels remains far more stable and transparent in large-scale virtual orchestration templates.

3. Open Issues: Please Do Not Overlook the Underlying Bugs

Given the length of this thread, I kindly ask that the development team does not lose sight of the core bugs that initiated this post:

  1. Persistent Ghost Tracks in Play Mode:

    Deleted players (such as "Violine 2 neu") and cleared divisi staves (Notenzeile (a)/(b)) remain permanently visible in the Play Mode track tree. Saving, closing, and restarting Dorico does not purge these dead endpoints.

  2. The “Linked Dynamics” Pitfall upon Player Deletion:

    Manually clearing staves before deleting an erroneous player inadvertently deletes dynamics across all linked section staves in the score. Deleting a player should be an atomic, safe DAW-style operation that automatically severs dynamic links in the background.

I appreciate the continued exchange and look forward to the team’s perspective on these workflow areas.

Best regards,

Stefan Meier