Wish Wish: Ability to Reorder Songs in the Song List

Yeah, the setlist indexes the songs by their position in the list (1 through 128), so if you move the song in the song list, any setlist that uses that song would then point to the wrong spot. You'd have to rebuild your set lists anytime you reordered the song list.

As a work around, you can export the song list to a file and use a text editor to move the XML entries around and change their "id" property accordingly to match the song's new position in the list. Each song and its sections are defined between <Song id="" name=""> and </Song> tags. The "id" property is the list position index ( 0 to 127) and "name" is the label for that song (up to 10 characters). After you reorder things, save the file and import it back into Axe Edit. You'll then need to rebuild all your setlists so they match the new song positions in the list.

Save an unchanged copy of the exported Song List, just in case you screw something up editing the file.
 
Last edited:
I'm sure it could be done, but you'd still have to rebuild the setlists anytime the song list order changes unless they changed the way each song in the list is indexed. It might be possible to create a translation table that could auto-correct the setlist index references, but that would likely only work for the 4 currently loaded setlists.

Keep in mind that the song list is searchable in Axe Edit, so even if it's not sorted, you can use the search field to pull up specific songs to drag over.
 
I'm sure it could be done, but you'd still have to rebuild the setlists anytime the song list order changes unless they changed the way each song in the list is indexed. It might be possible to create a translation table that could auto-correct the setlist index references, but that would likely only work for the 4 currently loaded setlists.

Keep in mind that the song list is searchable in Axe Edit, so even if it's not sorted, you can use the search field to pull up specific songs to drag over.
You can display things in different orders and not be destructive to the data.
 
That's a good point. The index list doesn't have to be in sequential order. The song's id would then reflect the order in which it was added to the list and not it's displayed position in the list. They could add an additional parameter to each song entry for saving it's displayed position in the list as well. That one could be changed and reordered as much as you want and it wouldn't affect the referenced id used by the setlists.
 
Remember that the memory available for implementing setlists has been used up so changing the data structures in the modeler probably won’t happen.

Any changes to the order could probably occur in the editor and then be pushed to the modeler to refresh it; there’s already precedents for that sort of action that happens in the computer only. Or someone could write code that manipulates the exported XML and rewrites it.
 
Displaying a different sort in Axe-Edit can have nothing to do with the hardware.
Right. That’s why I said

Any changes to the order could probably occur in the editor and then be pushed to the modeler to refresh it; there’s already precedents for that sort of action that happens in the computer only.

It’s totally optional whether it’s pushed back.
 
Back
Top Bottom