Waldorf Quantum/Iridium: reference internal memory (3:) in QPAT sample paths

[douglas-carmichael]

Problem

A QPAT preset created by ConvertWithMoss and placed on the SD card of a Quantum/Iridium does not load its samples automatically — the device shows the "Find Sample Map" screen and asks the user to locate the samples by hand.

Cause

The sample-map paths embedded in the QPAT are written with the drive prefix 4:. On these devices the prefix selects a specific drive — 1: SD card, 2: USB, 3: internal memory — so 4: ties the preset to one particular drive and does not match a samples folder placed on the SD card. Since samples are always played from internal memory, the device cannot resolve them and falls back to the manual "Find Sample Map" step.

Fix

Write the sample paths with the internal-memory prefix 3:, the same prefix the device uses in its own sample maps. The workflow then becomes drive-independent: copy the preset together with its samples sub-folder to either the SD card or USB, and on the device use Load > Actions > Import to select the folder. The device copies the samples into internal memory and the preset resolves them automatically, regardless of which drive was used.

(The previous 4: prefix was documented in a comment as triggering the copy to internal memory, but in practice it only matches a USB drive; importing a 3: path copies to internal memory from either the SD card or USB.)

Reading is unaffected — the detector already strips any N: drive prefix. The detector's drive-number comment, the CHANGELOG, and the format documentation (a new "Loading the result on the device" note) are updated to match.

[douglas-carmichael]

Verified on hardware (Iridium): re-exported a preset with this change, copied the preset and its samples folder to the SD card, then Load > Actions > Import → clean import — every sample resolved into internal memory automatically, with no "Find Sample Map" prompt. Same result from a USB drive.

@git-moss — I own an Iridium, and from an owner's seat this has to be fixed. As it stands, every QPAT placed on the SD card forces you to hunt down the samples by hand through "Find Sample Map" on load — and depending on how loaded the CPU already is, that resolution step can noticeably tax it. That's broken for real-world use: a usability and a performance problem for anyone running sample-based patches off the card.

The fix is minimal and low-risk: write the sample-path prefix as 3: (internal memory, matching the device's own sample maps) instead of 4:, so the import just works from either the SD card or USB. One line in the writer plus a comment/doc update, and reading is unaffected (the detector already strips any drive prefix). This should go into the next release — I'll gladly make any changes you want.