about PLGenPro

[xzsaimon16]

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)

OR

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.

 

[xzsaimon16]

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

 

[djsoft]

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.

 

[xzsaimon16]

+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.

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

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.

 

[xzsaimon16]

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.

RadioBOSS 7.0 [beta]

Demitry, Came across a fault when working with Teasers. It seems under settings ->Track Exceptions that when I change exclude tracks shorter i change to 110 secs. However, It changes back to 30 secs as soon as I click out of the box or it I just click Ok. Enter back into settings to check...

www.djsoft.net

 

[djsoft]

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.

 

[djsoft]

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.

 

[xzsaimon16]

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.

 

[djsoft]

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?

 

[xzsaimon16]

Hello, I would like to request a review or an additional option to strictly enforce the rules of priority or non-repetition. Some time ago, I wrote about this, but I am still experiencing these types of problems, as the rules I am setting are not being followed.

In the screenshot, you can see my configuration, which should:

1. Give priority to songs that haven’t been played for the longest time. In this case, priority should be given (over 100) to those that haven’t been played for more than a day.
2. The repetition option is set to 6 hours, meaning the same song should not be repeated within 6 hours.

These rules are not being followed. In the screenshot, you can see there are songs that haven’t been played for a while and could be selected. Additionally, there are times when the 'no track repetition' rule is not adhered to, and tracks that played 3 hours ago are selected, as shown in the capture Number 3.

 

[xzsaimon16]

Another question I have is whether PLGenPro takes into account the computer's time or RadioBOSS's time when selecting songs. I set (-) 5 hours in RadioBOSS, and it seems to me that the Playlist Gen Pro module does not read RadioBOSS's time since it is a separate module.

 

[djsoft]

Hello, I would like to request a review or an additional option to strictly enforce the rules of priority or non-repetition.

I'm not sure what option there could be, as rules are already applied as they should

Give priority to songs that haven’t been played for the longest time. In this case, priority should be given (over 100) to those that haven’t been played for more than a day.

Priority of 100 means that the track will have about x4 more chance of being selected, compared to the default priority.

But here's one thing: your rule adds +100 priority for all tracks that were played more than one day ago. Meaning, all tracks except for those that played during the last 24 hours, will get +100 priority. Roughly, 24 hours is about 350 tracks, and if your library is 10000 tracks, then there will be 9650 tracks (97% of all tracks!) with +100 priority. Which, in turn, means that those 97% tracks will have equal priority, and, effectively, priority rule doesn't really work in this case.

These rules are not being followed.

This is not true. I can guarantee you that all rules are applied as they should. It's tested for every release, both automatically with unit tests, and manually.

The repetition option is set to 6 hours, meaning the same song should not be repeated within 6 hours.

Yes, but it still can happen due to misconfiguration, e.g. repeat protection rules can be disabled for some category and track can come from there, or option to consider tracks in the playlist window is not configured properly and tracks to be played were not accounted for.

The "Do not repeat track" checks the full file name. So if the the same track exists in different folders, this option will consider those as different tracks.

 

[xzsaimon16]

But here's one thing: your rule adds +100 priority for all tracks that were played more than one day ago. Meaning, all tracks except for those that played during the last 24 hours, will get +100 priority. Roughly, 24 hours is about 350 tracks, and if your library is 10000 tracks, then there will be 9650 tracks (97% of all tracks!) with +100 priority. Which, in turn, means that those 97% tracks will have equal priority, and, effectively, priority rule doesn't really work in this case.

In my case, how would this be applied correctly? For a category that must necessarily select between 12 or about 15 tracks from said category, and where no track should be repeated for at least 6 hours, playing 3 songs from this category within a two-hour period. I’m not sure how you would configure it

This is not true. I can guarantee you that all rules are applied as they should. It's tested for every release, both automatically with unit tests, and manually.

I understand, but it doesn’t work for me in the way that, according to my criteria and configuration, it is supposed to.

Yes, but it still can happen due to misconfiguration, e.g. repeat protection rules can be disabled for some category and track can come from there, or option to consider tracks in the playlist window is not configured properly and tracks to be played were not accounted for.

The "Do not repeat track" checks the full file name. So if the the same track exists in different folders, this option will consider those as different tracks.

"In the screenshot, you can see the configuration I have to avoid repeating tracks. I decided to enable it directly from each category because I have several categories that work differently. I have a T40 category (40 tracks) and one for high rotation (at least 12 tracks). So, each one has its own different configuration.

I don’t have the same tracks in other folders since a duplicate finder is used, and we try not to have any repeated tracks.

Another question I have is whether PLGenPro takes into account the computer's time or RadioBOSS's time when selecting songs. I set (-) 5 hours in RadioBOSS, and it seems to me that the Playlist Gen Pro module does not read RadioBOSS's time since it is a separate module.

 

[djsoft]

In my case, how would this be applied correctly? For a category that must necessarily select between 12 or about 15 tracks from said category, and where no track should be repeated for at least 6 hours, playing 3 songs from this category within a two-hour period. I’m not sure how you would configure it

Repeat protection is easy, you just specify the rules, general or per-category. Per-category rules override the general settings.

I understand, but it doesn’t work for me in the way that, according to my criteria and configuration, it is supposed to.

If a majority of tracks have high priority, it's almost the same as if all tracks have the same priority. You need to configure your priority rules so that they are only applied to a smaller subset of tracks, not for 90%+ of the category contents.

Another question I have is whether PLGenPro takes into account the computer's time or RadioBOSS's time when selecting songs. I set (-) 5 hours in RadioBOSS, and it seems to me that the Playlist Gen Pro module does not read RadioBOSS's time since it is a separate module.

For repeat protection it uses the time as set in RadioBOSS. Also ensure that you use the most recent RadioBOSS just in case.