Search results

Yes it's correct. It is understood, thank you.

Updating the request for this feature a bit, I saw some different examples and it would be good to consider the formats of how "last played" would be displayed (in some areas like Track Info), in addition to the "played approx. same" warning time now" example: Last played: Today(6:32 a.m.) 10...

This is possible. press ctrl+f in the playlist window

I understand. There is a small error and that is when the auto intro is played first than the track, the intro mark starts right with the auto intro and the intro bar ends before its set mark. This is only when the auto intro is longer than the intro mark and is set to end on the intro.

In that case, will there be any changes for the future? to make it work that way?

Based on the auto intro, how do I make it so that: IF a track meets the conditions and there is a SWP-ID programmed before the track, RB only plays the auto intro? omitting the SWP-ID. This is so that the SWP-ID and the Auto intro are not played back to back.

Could the calculation of days be added to the "last played" column or tag? example: 03/20/2024 (7 days ago). This in all areas: track info, search, playlist (tooltip), etc. This makes manual selection of songs based on time in days much easier for those of us who select tracks manually.

Thank you, this function is important for us who work during the day with the manual event scheduler

I understand, meaning that "run" will only open the PLGP and create the playlist? even if the event scheduler is in manual mode? Was this added in the last update 7.0.2.0?

True, but we would have to add at least the one to create playlists, that is, generate command (without loading it into the playback window)

It can depend on many factors. It almost never happened to me but as I adjusted repetition rules in the categories I think it has caused this problem to be repeated more frequently but as I say, it doesn't always happen but it does happen.

Yes, thank you, this option was disabled after presenting the problem, although it did not solve it but I suppose because the damage was already done, thank you

Yes, the problem is that it did not save the changes made from the track properties, and in the track tool it threw the aforementioned error. But no, it wasn't the database, because I installed the RB again and restored just the song database and it worked. Then I proceeded to open the backup...

I always use it, that's the problem

Yes, every time it happens it's because the song hasn't started yet. because as I said, the playlist is created with an interval of 1 minute to generate and load. So from what I see the last track that is between that last minute is always at risk of being selected again

sqlite... the detail is that, after the previous error, it lets me use none of the tools to save the information

no, I only use a single pc

In fact it just happened to me

It's strange. since something like this happens to me, on certain occasions. I have activated the option to take into account the tracks of the playlist, because a playlist of one hour is generated and this is generated 1 minute before 00 of each hour, to be loaded to the playlist window at 00...

In that case, what could cause the song not to be selected? That category only has the rule of not repeating the track for 6 hours. What am I supposed to do now? I installed RB again and the problem persists, it won't let me save the changes in any way, track tool won't let me either...