Add adjustable time periods as a rule for smart playlists

Feature description:

Add adjustable time periods as a rule for smart playlists, like periods between 3 days and 365 days as a person would like to choose.

Problem solved:

It helps to create a most listened playlist where a person would only like to see songs for a specific period rather than the total amount of most listened tracks.

Brought benefits:

It adds a rule that would enable a most listened track playlist for the week, the month or the year as a person would prefer to make rather than having to rely on only the total most listened songs playlist on the homescreen.

Other application solutions:

 

 

Additional description and context:

 

 

Screenshots / Mockup:

    

You can set times as you want and as explained a lot already there’s no full history of each plays only the last played time …

These are the available filter targets, I don’t see any target for time periods

A time period is 2 values apply them to last played.

I’ve tried and it’s not working the way I imagine it should, it doesn’t display the most listened to songs within the time period, rather it just displays all my most listened to songs depending on how it’s sorted. If I sort by most played within the past 7 days, it just shows the total most listened songs.


This is how it shows

My set up

You mean what I explained a couple of time including in this thread that there’s no full history and only a lastplayed and that this is normal … ?

@darkwiiingduck
As much as I welcome this function and understand your concern, it cannot work.
The complete playing history of all tracks would have to be saved. However, the database only saves one value per track. (Last played, how often played, how often skipped, etc., but not all the data of its playing history).
It is not possible to filter out time periods from this data.

You would therefore need an additional database that chronologically records all tracks played with a time stamp. This is what last.fm does, for example.

1 Like

Thanks for the explanation

1 Like