Bug 56269 - random play on really large hayes playlists takes forever
Summary: random play on really large hayes playlists takes forever
Status: RESOLVED DUPLICATE of bug 56268
Alias: None
Product: noatun
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-23 12:09 UTC by Michael Bauer
Modified: 2003-03-23 12:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Bauer 2003-03-23 12:09:16 UTC
Version:           unknown (using KDE 3.1.1)
Installed from:    Gentoo
Compiler:          gcc version 3.2.2
OS:          Linux (i686) release 2.4.20-gentoo-r1

Hi,
i have a really large mp3 collection (~50 Gigabyte) mounted via nfs. Hayes is the perfect solution to handling these files, but when doing a random play on the whole collection CPU load goes to 100% and all noatun windows freeze. 
I think the problem is that in random mode noatun starts to scan all available files, which naturally takes a very long time for such a large collection. (i killed noatun after waiting for about 10 minutes...) The network speed should not be the problem, the server is connected via switched fullduplex 100MBit.
So i am not sure if theres a simple solution. Either changing the "randomize" algorithm or maybe as a interim solution starting another thread that collects the info to at least prevent the GUI from freezing?

Maybe its just a bad idea after all to start a random play on 50 Gigs of data ;-) but i just wanted to inform you there are potential problems regarding the randm play...

Anyway, thanks for that great product! Beeing a longtime xmms-user i actually only started using Noatun when i recognized the impressive Hayes playlist. That really made my day ;-)

thanks
Michael
Comment 1 Michael Bauer 2003-03-23 12:13:38 UTC
Sorry, this is a dupe to #56268! 
Pressed submit twice due to some network problems :-( 
Comment 2 Stephan Binner 2003-03-23 12:21:50 UTC

*** This bug has been marked as a duplicate of 56268 ***