When having playlist tree enabled, save-load-save action on the playlist (xspf format) results on playlist nesting
Here is the example ofor file "file1.ext" inside playlist folder "One" and "file2.ext" inside playlist folder "Two":
First save:
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/" xmlns:vlc="http://www.videolan.org/vlc/playlist/ns/0/">
<title>Playlist</title>
<trackList>
<track>
<location>file:///file1.ext</location>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:id>0</vlc:id>
</extension>
</track>
<track>
<location>file:///file2.ext</location>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:id>1</vlc:id>
</extension>
</track>
</trackList>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:node title="One">
<vlc:item tid="0" />
</vlc:node>
<vlc:node title="Two">
<vlc:item tid="1" />
</vlc:node>
</extension>
</playlist>
Clearing the VLC playlist, loading the just saved xspf playlist, and saving it again results in:
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/" xmlns:vlc="http://www.videolan.org/vlc/playlist/ns/0/">
<title>Playlist</title>
<trackList>
<track>
<location>file:///file1.ext</location>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:id>0</vlc:id>
</extension>
</track>
<track>
<location>file:///file2.ext</location>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:id>1</vlc:id>
</extension>
</track>
</trackList>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:node title="test.xspf">
<vlc:node title="One">
<vlc:item tid="0" />
</vlc:node>
<vlc:node title="Two">
<vlc:item tid="1" />
</vlc:node>
</vlc:node>
</extension>
</playlist>
As you can see there is an additional "vlc:node title=text.xspf" after.
This results in the VlC playlist displaying a new "Playlist" super-folder in which there is a "test.xspf" sub-playlist that includes "One" and "Two".
I do not know whether it's a windows-only thing but since I cannot test it on any other system, I post it in the windows forum.
Is this something intentional or a bug?