After the update to 2.8, my dynamic playlists broke. After a song finishes, Amarok adds a new song to the current playlist, but these newly added tracks do not follow the dynamic playlist rules. I started a bug report here: https://bugs.kde.org/show_bug.cgi?id=325094
Can anybody shed some light on this for me?

Maybe something went wrong in the update and the XML file was modified. We need to check this.

Thanks for your reply. How can i check this file?

Isn't it the file you added to the bug report?

Ah, that one. Ive made dozens of different ones to test, and they all result in the same behavior. I just deleted dynamic.xml and made a new playlist....same thing is happening.

I just noticed another interesting behavior. In .kde/share/apps/amarok, there are dozens of files called amarokcollectionscanner_batchscanner.xml, amarokcollectionscanner_batchscanner.xml_ , amarokcollectionscanner_batchscanner.xml__ etc. each new one having an additional "_" on the end of the name. There are at least 20 of them.

Just to test again, I made a very simple dynamic playlist. It should add songs with ratings of 1, 2, 3, 4 or 5 stars to the current playlist. If I click on "Repopulate" it does just that, but when playing through the playlist, it adds only songs with 5 stars. Here's the playlist file:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<biasedPlaylists version="2" current="0">
    <playlist>
        <title>Rating</title>
        <partBias>
            <tagMatchBias weight="0.07">
                <field>rating</field>
                <numValue>0</numValue>
                <numValue2>0</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
            <tagMatchBias weight="0.12595">
                <field>rating</field>
                <numValue>2</numValue>
                <numValue2>0</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
            <tagMatchBias weight="0.164525">
                <field>rating</field>
                <numValue>4</numValue>
                <numValue2>0</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
            <tagMatchBias weight="0.1674">
                <field>rating</field>
                <numValue>6</numValue>
                <numValue2>0</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
            <tagMatchBias weight="0.154949">
                <field>rating</field>
                <numValue>8</numValue>
                <numValue2>0</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
            <tagMatchBias weight="0.317177">
                <field>rating</field>
                <numValue>10</numValue>
                <numValue2>0</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
        </partBias>
    </playlist>
</biasedPlaylists>


Also, when I run Amrok in deug mode, I get quite a lot of these messages. i don't know what they mean, but they seem relevant here.

Code: Select all

BEGIN: void EngineController::slotMetaDataChanged()
amarok:   [EngineController] slotMetaDataChanged() triggered by phonon, but we've already seen exactly the same metadata recently. Ignoring for now.
amarok: END__: void EngineController::slotMetaDataChanged() [Took: 0s]
amarok: BEGIN: void EngineController::slotMetaDataChanged()
amarok:   [EngineController] slotMetaDataChanged() triggered by phonon, but we've already seen exactly the same metadata recently. Ignoring for now.
amarok: END__: void EngineController::slotMetaDataChanged() [Took: 0s]
amarok: BEGIN: void EngineController::slotMetaDataChanged()
amarok:   [EngineController] slotMetaDataChanged() triggered by phonon, but we've already seen exactly the same metadata recently. Ignoring for now.
amarok: END__: void EngineController::slotMetaDataChanged() [Took: 0s]
amarok: BEGIN: void EngineController::slotMetaDataChanged()
amarok:   [EngineController] slotMetaDataChanged() triggered by phonon, but we've already seen exactly the same metadata recently. Ignoring for now.
amarok: END__: void EngineController::slotMetaDataChanged() [Took: 0s]
amarok: BEGIN: void EngineController::slotMetaDataChanged()
amarok:   [EngineController] slotMetaDataChanged() triggered by phonon, but we've already seen exactly the same metadata recently. Ignoring for now.
amarok: END__: void EngineController::slotMetaDataChanged() [Took: 0s]
amarok: BEGIN: void EngineController::slotMetaDataChanged()
amarok:   [EngineController] slotMetaDataChanged() triggered by phonon, but we've already seen exactly the same metadata recently. Ignoring for now.
amarok: END__: void EngineController::slotMetaDataChanged() [Took: 0s]


whatthefunk wrote:After the update to 2.8, my dynamic playlists broke. After a song finishes, Amarok adds a new song to the current playlist, but these newly added tracks do not follow the dynamic playlist rules. I started a bug report here: https://bugs.kde.org/show_bug.cgi?id=325094
Can anybody shed some light on this for me?

I experienced this exact same issue when I upgraded from Amarok 2.7.1 (on Fedora 17/XFCE) to Amarok 2.8.0 (on Fedora 20/Gnome). All of the playlists began behaving oddly and the "Verbose" Playlist Layout showed inconsistent data. Even after resorting to the default ~/.kde/share/apps/amarok/dynamic.xml , dynamic playlists did not conform to their rules, playlists no longer loaded when double-clicked, and some playlists would not load at all.

The issue appears to have been some incompatibility between my 2.7.1 database and Amarok 2.8.0. I fixed mine by downgrading back to 2.7.1 with my backup of my 2.7.1 database and then upgrading to 2.8.0. If you don't have your older backup, it *might* work by simply downgrading to 2.7.1 and upgrading again... Here were my steps, kubuntu/kde will be slightly different, i.e. ktrash, apt, and the kubuntu version of amarok.

# backup existing
for filename in ~/.kde/share/config/amarok* ; do cp $filename $filename.bak ; done
cp -r ~/.kde/share/apps/amarok ~/.kde/share/apps/amarok.bak
# delete existing
killall amarok
gvfs-trash ~/.kde/share/apps/amarok
gvfs-trash ~/.kde/share/config/amarok*
# remove amarok
yum remove amarok
# restore 2.7.1 backup
tar -C ~ -xvpf home_directory.tar.gz ./.kde/share/apps/amarok ./.kde/share/config/amarok*
# downgrade amarok
wget --directory-prefix=/tmp "ftp://ftp.pbone.net/mirror/download.fedora.redhat.com/pub/fedora/linux/releases/19/Everything/x86_64/os/Packages/a/amarok-2.7.1-2.fc19.x86_64.rpm"
wget --directory-prefix=/tmp ftp://ftp.pbone.net/mirror/download.fed ... x86_64.rpm
wget --directory-prefix=/tmp ftp://ftp.pbone.net/mirror/download.fed ... x86_64.rpm
yum install /tmp/amarok*
# run amarok 2.7.1 to verify all the playlists work
amarok -d
# exit amarok
CTRL-C
# update amarok to 2.8.0
yum update amarok

Hello,

I had this issue and I found a bunch of files amarokcollectionscanner_batchscanner.xml____ ....

Go to settings, Configure Amarok, Metadata :
uncheck "Write statistics to file" and "Write covers to file".

Here is, it has definitively solved this issue.
It seems there is a race condition to write the metadata and update the playlist.