10.2. Generation and Candidate Problems

Mix generation targets the requested track count. If it cannot fill every position, it keeps the longest compatible route it found, preferring the stronger route when lengths tie, as long as every lock is preserved.

The requested track count stays unchanged so another Generate can retry the full target after you adjust the Library or constraints. If no compatible progress can preserve the locks, the current tracklist is left unchanged.

Common causes of a partial or unchanged result include:

• Too few ready and unique tracks in the selected groups
• A focused transition profile with too few compatible edges
• A strict BPM rule or narrow pitch-shift range
• Allowed roots or modes that exclude most of the Library
• Required stable or changing start/end keys
• Locked positions that cannot be connected
• Position, segment, or whole-Mix exclusions

Gem Finder intentionally ignores Mix groups and exclusions, but it still requires an unused track that passes BPM, Allowed Keys, key matching, and any start/end relationship requirement. A shared candidate can be planned but not auditioned until local audio is added normally.