Not a Bug Axe Edit Song Export doesn't appear correct

[quark]

I was playing around with the new setlist function and created some "dummy songs" for test. The first Song has presets 68, 69, 70,71,72,73 for Song 001 sections 1-6. When I exported this song list, the exported file contained the following data:
<Song id="0" name="Song 001">
<Section name="Sect 1" preset="69" scene="0"/>
<Section name="Sect 2" preset="70" scene="0"/>
<Section name="Sect 3" preset="71" scene="0"/>
<Section name="Sect 4" preset="72" scene="0"/>
<Section name="Sect 5" preset="73" scene="0"/>
<Section name="Sect 6" preset="74" scene="0"/>
Which shows that the exported preset #'s are 1 higher than those in the system.
May be related to how preset numbering is set up on the Axe - either start at 0 or start at 1. My display offset is set to 0.
Can anyone verify this so that I know whether it is a local problem or a problem with the software. Thanks ...

 

[Michael Pickens]

This is not a bug. Please update your post heading.

The data in the file is in a format used by the hardware and is not meant for the end-user to update by hand. For instance, a preset value of zero means "not assigned", which makes assigned presets one-based integers.

 

[quark]

Okay, got it. I was planning on using the import/export function as a way to create multiple setlists for various purposes and I was going to edit the exported setlists with a python script to input data. Easy enough to "add 1" to the preset number in the python code. Thanks ..