about PLGenPro

xzsaimon16

Active member
I would like to consult how playlists are generated, their generation order with PLGenPro.

Since I have had problems based on how I want the playlists to be generated.

I have categories with few songs which should rotate a lot during the day, example: "high rotation" category which has 10 songs and should not be repeated after 6 hours. The problem that happens to me sometimes is that there is a song which can be selected meeting the requirement that it has more than 6 hours without playing and does not repeat the artist, etc. PLGenPro doesn't select it, so it skips the category selection (it doesn't place anything in the PL) and I have to fix it by placing it manually.

I try applying the priorities option. But still it doesn't select and it can take up to 3 days skipping the track.
(This option also seems to me that it does not work 100% since I set these options increasing the probabilities and still the songs with the established priorities are not selected)

1717357114709.png
OR
1717357162767.png



I think the "Priority" option should be above some rules like "no repeat artist" or at least make the user give more weight to this option and be stricter.

It also happens to me in the large categories with more than 400, 500, 1500 songs. But I'm more concerned about the categories with fewer songs.

I need to understand why this happens, as well as how to improve and make RB work for my slightly more closed musical pattern.




Example In this category there are songs that could be solved since it complies with the option of not repeating for 23 hours. I set the priority of increasing the probability of songs older than 1.5 days and it still does not select.


1717357877399.png
1717357905787.png

1717358030230.png

1717357996039.png
 

Attachments

  • 1717357893488.png
    1717357893488.png
    72 KB · Views: 84
Last edited:
Additionally, for a few days now, I have noticed that songs from the same day are being selected, very closely as they see the capture. Which I find very strange since the selection should be more random with respect to the last time label. And yes, I have many songs which can be selected so that this does not happen. but it happens
1717360364908.png
 
I think the "Priority" option should be above some rules like "no repeat artist" or at least make the user give more weight to this option and be stricter.
Priority goes before repeat protection rules. That it, it first selects at tracks from category's track source according to priority (and before that, Filters are applied, on category load). After a track is selected, it's checked with Repeat Protection rules. If it passes the rules - it's added to the playlist. If not, it will select another track, considering priorities.

Example In this category there are songs that could be solved since it complies with the option of not repeating for 23 hours. I set the priority of increasing the probability of songs older than 1.5 days and it still does not select.
What does it select? Are there any error messages in the log? +100 priority will be capped at +90, and, roughly, it'll be 4x more chance for a track to be selected, compared to a track with the default priority of 50.

Additionally, for a few days now, I have noticed that songs from the same day are being selected, very closely as they see the capture. Which I find very strange since the selection should be more random with respect to the last time label. And yes, I have many songs which can be selected so that this does not happen. but it happens
It doesn't really consider last played tag when randomly selecting a song (but you can define priority rules for it to do so), but by default, with no priority rules, a track played 100 days ago and track played couple of hours ago, are the same.
 
+100 priority will be capped at +90, and, roughly, it'll be 4x more chance for a track to be selected, compared to a track with the default priority of 50.


It doesn't really consider last played tag when randomly selecting a song (but you can define priority rules for it to do so), but by default, with no priority rules, a track played 100 days ago and track played couple of hours ago, are the same.
I understand, but the priority does not work for me since, as seen in this screenshot, priority is given to songs older than 14 days and it does not select them. Just select the songs, there are many songs older than 14 days which have not been selected. From what I see, a very generic selection is made that only respects the 7 days of not repeating the songs.

1717435805286.png


It also happens in this category and others, just give these two examples.



1717435908830.png


According to me and from what you explained to me, with that probability of 100 or 90 they should not be omitted and it should not happen that songs are left behind. This has been happening to me for a long time, I wanted to report it but maybe it was me with my configurations that I can't get it to work well. That's why I consult on the subject.


What does it select? Are there any error messages in the log?
Regarding this, you just don't select anything. But if it shows errors it does not meet the artist repetition criteria. But I think this is not a problem. The problem itself is that if there are songs that can be selected (meeting the criteria) why not select them?

I made a similar report a while ago. That you couldn't select a song and the RB skipped it completely for days.
 
Last edited:
I made a similar report a while ago. That you couldn't select a song and the RB skipped it completely for days.
Here is the report with the same situation. With the difference that now I don't use the playrequestedsong command.

 
I understand, but the priority does not work for me since, as seen in this screenshot, priority is given to songs older than 14 days and it does not select them. Just select the songs, there are many songs older than 14 days which have not been selected. From what I see, a very generic selection is made that only respects the 7 days of not repeating the songs.
This is random selection, it can happen sometimes, priority does not guarantee a song will be selected, it only increases its probability. I don't think there are bugs. I did a quick test with this, two songs, one has +90 priority, and in the resulting playlist it appears roughly 4x times more often than the other. Maybe you should also add more rules e.g. to decrease priority for songs that played recently.
 
According to me and from what you explained to me, with that probability of 100 or 90 they should not be omitted
Those songs can still be eliminated by repeat protection rules. Or they may not be selected in the first place. +90 priority does not guarantee anything.

Regarding this, you just don't select anything. But if it shows errors it does not meet the artist repetition criteria.
If you see any errors, they must be corrected, otherwise the results will not be good.
 
This is random selection, it can happen sometimes, priority does not guarantee a song will be selected, it only increases its probability. I don't think there are bugs. I did a quick test with this, two songs, one has +90 priority, and in the resulting playlist it appears roughly 4x times more often than the other. Maybe you should also add more rules e.g. to decrease priority for songs that played recently.
Ok, I will continue testing with the instructions mentioned.

Now as for the categories that have the rule of not repeating themselves for 6 hours, how do I decrease the priority of these? From what I understand, I think the minimum would be 0.5 days, which translates to 12 hours.
 
Now as for the categories that have the rule of not repeating themselves for 6 hours, how do I decrease the priority of these? From what I understand, I think the minimum would be 0.5 days, which translates to 12 hours.
Can you please provide more information about it?
 
Back
Top