Exactly. The Set and Song lists remove the need to move individual presets around.
If I needed to move presets, I'd probably keep track of what went where, either with a screenshot, or keeping the Preset Manager open so I can see the list. We can export the Setlist and Songlist to disk where it'll be an XML file, and is importable into a spreadsheet or text editor where it might be easier to manipulate. Export it from the spreadsheet back to XML then import it into Edit and into the modeler. Here's what the files look like:
Songlist example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<All-Songs version="1" deviceId="18" deviceMajor="4" deviceMinor="1">
<Song id="0" name="Song 001">
<Section name="Sect 1" preset="427" scene="0"/>
<Section name="Sect 2" preset="0" scene="0"/>
<Section name="Sect 3" preset="0" scene="0"/>
<Section name="Sect 4" preset="0" scene="0"/>
<Section name="Sect 5" preset="0" scene="0"/>
<Section name="Sect 6" preset="0" scene="0"/>
</Song>
.
.
.
<Song id="127" name="Song 128">
<Section name="Sect 1" preset="0" scene="0"/>
<Section name="Sect 2" preset="0" scene="0"/>
<Section name="Sect 3" preset="0" scene="0"/>
<Section name="Sect 4" preset="0" scene="0"/>
<Section name="Sect 5" preset="0" scene="0"/>
<Section name="Sect 6" preset="0" scene="0"/>
</Song>
</All-Songs>
In this example I'd set Song
ID=0
, section 1, to point to preset
427
, then swapped the song with an empty preset, and Edit showed that the preset hadn't updated.
Setlist example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<Setlists version="1" deviceId="18" deviceMajor="4" deviceMinor="1">
<Setlist id="0" name="Set 1">
<SongId id="0"/>
.
.
.
<SongId id="0"/>
</Setlist>
</Setlists>
The format is pretty self-explanatory if you understand XML, though the files aren't documented that I remember. Because the song list points to preset slots it's easy to see why the list would break by moving presets around. Wishes exist to improve how User Cabs are tracked because moving them breaks presets also so maybe both would be touched at the same time, but when we'd see that mechanism enhanced is only known to Fractal. The modeler allows duplicate preset names, but doesn't have a compound key of the slot+name or a hash of the contents of the preset to uniquely identify the preset, so we get to work with what we got.
PS -
<All-Songs version="1" deviceId="18" deviceMajor="4" deviceMinor="1">
looks like how Edit can track what version of the file format its in, the model of the modeler, and the firmware the modeler is running. I don't know how critical those are but currently I expect that
version
is most important.
Note:
Manipulating the XML and reimporting it isn't a documented or an officially approved practice, so if your modeler catches on fire or your hair falls out remember "I was out of town when that happened."