To avoid that, I use "2" for the setting "Add when the playback position is X items or less from the end".
I don't know if it's a known bug, or if it can be circumvented ?

Hello @fbuser, I just noticed that, with FB v2 beta 34, the "Check for updated components" did not report as new your 3 components: Random Pool 2.0.0., SQLTree 4.0.0 and SQLite Utilities 3.0.2. (this did not prevent me from installing all them manually).
Said that, I also noted that FB v2 beta 34 can detect other updates, thereof I think there is a problem with your components versioning reporting.
Regards, Andrea

Component update: Checking for: foo_uie_sql_tree / SQL Tree / 4.0.0
Component update: Found a match - 4.0.0 vs 4.0.0
Component update: Checking for: foo_sqlite / SQLite Utilities / 3.0.2
Component update: Found a match - 3.0.2 vs 3.0.2

Yes, as soon as fb2k v2 becomes stable.

my PC is an old 32bit running Win 10.

I have a large library

Can you help me troubleshooting the problem? I really would  like to get back to a decent performance.

Stated this, the previous version was able to generate a 50 tracks random playlist in few seconds (I have a large library).
The new V2.0.0 takes 20 times (or so) longer!!!!

I've updated plugin today, v2.0.1, and it crashes foobar2000. Windows 11 64 bit, v2.0 works.

I have multiple crash logs I can upload - let me know if this one works.

• Did you upgrade from random pools version 2.0.0 or did you newly install version 2.0.1?
• If it was a new installation, did you use the configuration from a fb2k version < 2?
• If you used the configuration from a fb2k version < 2, what are the versions of fb2k and random pools you take the configuration from?

I upgraded from 2.0.0. When foobar relaunched after installing 2.0.1, it immediately crashed.

I upgraded from foobar 1.6 where I also had Random Pools installed, so probably yes.

Ok, that explains the cause of the crash. It should be fixed now with the lastet version.

Sorry for late reply, it was the same for me - I've migrated config from 1.6 when installing beta 2.0, 32 to 64 bit. randompools weren't available then, so I waited final version of 2.0, installed 2.0 of randompools, it worked, and then upgraded to 2.0.1, had crash.

Anyone out there can help me understanding what's going wrong?

Quote from: AndreaT on 2023-05-24 21:39:36

Anyone out there can help me understanding what's going wrong?

Please, post your settings. Besides this as you are obviously using a SQL query, ensure that you are using a materialized media library table, not the virtual table directly. This should be always faster on your system.

The queries and materialization instruction you provided me in: Reply #318 – 2022-08-19 21:56:15 and Reply #331 – 2022-08-23 19:21:06 of this thread.

WITH
Albums AS (
  SELECT album||'|'||coalesce("album artist",artist) Album
  FROM MMediaLibrary
  GROUP BY 1
  ORDER BY random()
  LIMIT 10
)
SELECT path, subsong FROM
MMediaLibrary
WHERE album||'|'||coalesce("album artist",artist) IN (SELECT album FROM Albums)
ORDER BY album||'|'||coalesce("album artist",artist),coalesce(discnumber,1),tracknumber;

I noted that the SQL query you provided me in Reply #318

still remaining the big question: why it was anyway working decently in the past with MediaLibrary and not anymore today?

I want a playlist of one song per artist, that song being the oldest played from that artist.

One small issue is lots of duplicates