Amarok 2.80 on KDE 4.12.4, openSuse 13.1 seems to be scanning excessively.

If I stop a track and clear the playlist there is a scan, Switching from one application to Amarok often causes a scan. The whole program waits for the scan to finish before anything else can be done.

Not a major bug (if a bug at all), just a bit of an irritation.

John F.

but what does it scan? You can see at the bottom if you click on the bar when the scanning happens, or check the output from the konsole if you start amarok with 'amarok -d --nofork'

The terminal output is:

Code: Select all

amarok: [EngineController] slotStateChanged from  Phonon::PlayingState  to  Phonon::StoppedState 
amarok: MPRIS2: Queueing up a PropertiesChanged signal
amarok: [AbstractDirectoryWatcher] addDirToList for "/VolB/Music/A Hawk And A Hacksaw-Cervantine"
amarok: BEGIN: virtual void GenericScanManager::requestScan(QList<KUrl>, GenericScanManager::ScanType)
amarok: END__: virtual void GenericScanManager::requestScan(QList<KUrl>, GenericScanManager::ScanType) [Took: 0s]
amarok: BEGIN: virtual void AbstractScanResultProcessor::scanStarted(GenericScanManager::ScanType)
amarok: END__: virtual void AbstractScanResultProcessor::scanStarted(GenericScanManager::ScanType) [Took: 0.001s]
amarok: [AbstractScanResultProcessor] got 1 directories
amarok: BEGIN: virtual void SqlScanResultProcessor::scanSucceeded()
amarok:   BEGIN: virtual void AbstractScanResultProcessor::scanSucceeded()
amarok:   END__: virtual void AbstractScanResultProcessor::scanSucceeded() [Took: 0.2s]
amarok: END__: virtual void SqlScanResultProcessor::scanSucceeded() [DELAY Took (quite long) 17s]
amarok: void StatSyncing::Controller::slotUpdateNowPlayingWithCurrentTrack() this track already recently submitted, ignoring



Does that tell you anything?

Thanks

John F.

The only thing that seems a bit strange is the time it takes for the scanning, is your database located somewhere else than local?

No, it's local, I assume: /home/john/.kde4/share/apps/amarok/mysqle

That is indeed local. So if it scans when you change something in the playlist, that is most likely due to the "watch folders for change" option in the collection settings, try disabling this and see if this helps.
Another option is to disable the metadata synchronization, which could also cause some scanning. Try if this changes something.

As for the GUI not being responsive when the scanning happens, this is a bug that is already fixed in the upcoming version.

Yes, turning off the watch feature does seem to stop the frequent scanning. However, it is a pity to lose useful feature.

John F.

Well, you can't have both, sorry, and the GUI freeze is a different issue anyway, and will be solved in the upcoming Amarok 2.8.1

questions:
- what folder is configured to be scanned by Amarok?
- what, other than music files, resides there?
- how often are music files being added to your collection?

google01103 wrote:questions:
- what folder is configured to be scanned by Amarok?
- what, other than music files, resides there?
- how often are music files being added to your collection?

Two, one in the home/music folder and one in the second disc music folder

Only music files & associated jpgs.

Every couple of days

John F.

Have you tried disabling metadata synchronization?

bcooksley wrote:Have you tried disabling metadata synchronization?

Yes, it seemed to have little effect.

John F