Search results

the same thing happens frozen search

We still have the problem of stopping the song search. It freezes and does not continue. We have already commented many times and it is not solved, please Dimitri, quick solution.

Hello Dimitri, I would like to please ask to solve a problem. It is normal when an advertisement is out of date to see it in a poorer color than black, a very similar color, more like a light gray color, almost similar to black on our big screen. A more different color like the one I propose...

Yes, but in previous versions this was not necessary, RB detected that the time had exceeded and a yellow warning icon appeared. This icon is very good. Could you put this back?

Hello Dimitri. As always here helping his RB. Versions ago I have been seeing that there is NO yellow alert Icon warning of ad block past time. That is, alert at 3.30 minutes and your block has 5 minutes and no warning icon for time exceeded appears. Has this been solved in version 7?

see if you could put an option I think it's good.As you know in the ad planner, we can tell an ad to be broadcast until the selected day and time, for example (2023/6/12 23 hours), from that date the ad is canceled and will stop broadcasting.I would like that when that advertisement has been...

Looking at the search in the library, it turns out that in version 5.9.4 it was possible to search in the library, in version 6 it was not. So if I want to search for a file by library, I can't, or at least I don't see the option in the search engine. can only select all, nothing, folder

this has always worked fine, version 6.2.4.2 works fine. This takes work away from the station and is a very good option. The library needs to be updated. The search is very good, try to solve dimitri.

I don't use the library because we continually changed the songs in the folders. we use folder search which usually works fine, but in version 6 it's getting frozen. Try to solve please dimitri thank you

It is noted that they did not touch that area of the search. ha ha ha. It has failed again, by the way deactivate defend and that did not help to fix search freeze

Apparently this version has fixed the frozen search. I will comment in a few days, but quite a few searches have been carried out and there is NO failure at the moment. Dimitri, you are great.

I do not use any Antivirus outside of Defender included in windows. I'm going to try disabling it to see if it resolves and I'll keep you posted. thanks dimitry

Dimitri, I could see the possibility of viewing the Tracks according to the type of radioboss configuration file. If you select tracks, all the indicative tracks, publicity, music are mixed. Could you put the types of files below tracks? I give you an example Show record entries --> Tracks -->...

After carrying out 5 or 6 different artist searches, the search stops again.

I do a different search again and the search stops again this time as soon as it starts at only 9766 tracks.

I do a different search again and the search stops again this time as soon as it starts at only 2518 tracks.

It stopped at 18154 tracks and it doesn't happen as it says that it resumes later, it has been stopped for more than 10 minutes and it doesn't resume, so it stops the search. Although it does not happen as a previous problem that the entire Radioboss was frozen. in 6.3.0.5 the search stops...

t is the same artist chema rivas. Although at times he has also happened with multiple artists. I will capture multiples when it happens and let you know. Protection seems not to be fine

Chema Rivas came out and after 30 minutes Chema Rivas came out again, he was with another artist. In the protection it is marked multiple artists separated by , & , and, etc. and does not seem to respect too much. you have to review

hello dimitri the music browser sometimes hangs again. the same thing is hung at 11 thousand searches, that at 5 thousand, that at 20 thousand, it does not have an exact number. 2 of every 5 searches remain frozen, although this time the radioboss is not paralyzed as it happened in previous beta...