Search results

In the priority rules, if you could set hours ago (in addition to days), for the last playback. It would be useful for categories with high turnover.

This idea of this new function was a very good thing, but I don't think the graphic is the most appropriate. The way it is currently being graphed is not very intuitive. It is curious to wonder why the bars have different heights, now I understand it, but without documentation it is impossible...

How active? Big improvement Can you explain this better?

Bug: Exporting priority rules to a file in PLGen Pro does not save the tags

Dmitry, I'm looking forward to this. Do you think it is still possible to incorporate it into this beta? :)

In the tags that are now used as priority I have categories: Speed (3 possible values), Mood (3 possible versions).. and several more... a total of 65 tags. If a search engine could be added, it would be very useful, or a tag grouper. I'm working on PLGen and it takes a long time to assign tags...

A checkbox with 3 states is not possible? The idea is fewer clicks when only one day of the week is needed.:) nop :( Also: I'm working with filters and priorities in PLGen pro and there are missing buttons to delete all filters and priorities rules. I have 20 categories with 5 filters that I...

In Playlist Gen Pro you can only drag the categories on the left side only if they are global. Also, if the buttons are used to go up and down the list, it throws an error. (report sent)

MariaDB 10.5 working ok here after installing the beta on the production system

Also after updating: The configuration of visible columns and their width in the playlist is lost.

Minor comment. After updating to the latest version RB did not automatically start with the 1st track, despite being configured. After the second start it did.

This was something highly anticipated. We have not yet tested it in production since the presets must be rebuilt. But in the meantime I have the following doubt: Values between 1 and 100 are accepted. Is it a percentage? Wouldn't a default value of 50% be more appropriate? So work the same as...

Great improvement. Maybe a select all/unselect would be faster to work in the interface

Why not graph it as a table? In this case it is per week, which in my case would be more useful. This is an old example from the forum, for this implementation I would make much taller columns with the time, and all the events there with the start time

Creé 3 eventos que reproducen una canción y el gráfico fue el siguiente. Ni siquiera puedo ver uno de los eventos. (se muestra superpuesto y no lo está) ¿Me estoy perdiendo algo?

Great idea. Minor problem: when using the dark style, there is a very annoying blink when passing over the viewfinder. Idea: When there are overlapping events at the same time it could be shown in another way, for example crossed out. Also a filter by category is very necessary, so as to check...

Dmitry, I'm trying this and so far it's a great first step. I see that they can be edited without being lost as separate artistsBut I would like to have an array of artists in readtag, that would be the most convenient to avoid false separations, is that possible?. the same for writetag. PLGen...

This for us was a significant improvement. Maybe a trackbar is more appropriate?

Thank you Dmitry for this new version, there are some new features that I have been waiting for years :D

Does this already exist? Also: Is it possible to add the buffered audio ms to the playbackinfo command when it is stream? The purpose here is to start an event via API from RB in header. But the receivers should take into account the buffer limits for a synchronized start of advertising.