Andreas

The naive appraoch that is implemented now is adding all player UIs in a vertical list. So every player's UI uses the full width and the height is evenly distributed....

The new version that came with #180 implements the layout similar to USDX but using LayoutGroups. - An evenly distributed grid is created based on the number of players. -...

The current layout using UIToolkit and flex-box layout supports 16 players. It may not be optimal from a theoretical point of view, but it gets the job done IMO.

Actually, I wonder if the jokers are needed. I would also allow this option always. Why sing a song that you don't want to sing?

I never heard about `#START`. - You have an example txt file? - Which Unit (ms, second, beats)? - What exactly does this do? - Does it jump to this...

> decimal point or decimal comma, both are used I am not sure that the current implementation considers this. Will check it. > it does not affect #GAP or #VIDEOGAP...

From #245, the idea came up that the API and thus Companion App should allow to - add player profiles - select songs, players, and their mic for the next...

The performous api has some redundant endpoints, e.g., GET "/api/getplaylistTimeout". The GET http method and get in URL is redundant. As convention, I suggest to use GET http method for...

What should also be considered is some sort of whitelist for devices. If you have 20 players and everyone can add songs and change player profiles, then chaos will be...

> Pretty easy fix for this would be to add basic authentication. Actually I would want to avoid anything security related such as passwords. Sure, its just a game but...