Closed jcorporation closed 2 months ago
Hi,
Thanks for reporting. It's due to the fact that it computes a playlist with all the songs of the user's library, and then crops it to the desired number of songs.
I'm working on optimizing it, but it's not as trivial as it sounds, unfortunately. I'll keep you updated :)
Thanks, it would be a great feature!
it took a fairly big rewrite of the playlist module, but it should be working faster now :)
I just published blissify 0.4.1
, --seed-song
should return faster there.
Great, ~I will test it soon.~ Tested and it works wonderful fast.
Hi, sorry that I must open another issue...
I just tested the --seed-song option as it sounds interesting.
In my setup (current master) it does not return or is so slow that I can not await it. You mentioned in the README that this option is somewhat slower, but I think not so extremely slower?
With --seed-song option set. I aborted the task after 2 minutes of 100% CPU usage of blissify.
I tested also without the --dry-run and --from-song options, but that does not help. Lowering the number of songs does also show no success.