If you look closely, the program divided 26 channels into two columns of 13 each, so the division is done correctly.
The problem is that since the channel names don't fit on one line, the application generates a second line.
We're improving the way we calculate column widths to avoid this issue, and we hope to release an update tomorrow.
Titio Produções de Áudio
•
Aug 8, 2025
Hi Desarrollo.
I hadn't noticed the channel split (13/26).
It's perfect now.
Thanks.
Titio Produções de Áudio
•
Aug 7, 2025
Hello Desarrollo.
Talking to a friend about this topic, he thinks the input list should be executed as shown in the attached image.
I agree with him, as it's clearer for the people on stage.
Furthermore, with this layout, we're considering more columns in the list to accommodate more information.
Currently, we can only create three columns, correct?
It would be nice for the user to have the option to adjust the width of each column, but I believe that would be much more complicated to do.
But here's my suggestion as well.
Thank you.
mcidesarrollo
Team•
Aug 8, 2025
Hi Titio, thanks for your feedback!
We've resolved the issue with calculating column measurements when the channel name is long.
It's now averaged differently and never allows jumping to a second line to make the input list (and the output list) more consistent and readable.
Please reload your page with CTRL+F5, test it, and let us know if it works for you now.
Regarding your suggestions about adding more columns and customizing column widths, due to the nature of the RiderMaker core and the external library we use to convert to PDF, this is extremely complicated, and we also believe it would make things a bit more complicated for users.
However, we haven't ruled it out completely and will continue to think about whether developing this would be feasible and find a way to make it simpler.
Log in to comment and vote
Comments5
mcidesarrollo
Aug 7, 2025
Hi Titio, thanks for reporting this issue.
If you look closely, the program divided 26 channels into two columns of 13 each, so the division is done correctly.
The problem is that since the channel names don't fit on one line, the application generates a second line.
We're improving the way we calculate column widths to avoid this issue, and we hope to release an update tomorrow.
Titio Produções de Áudio
Aug 8, 2025
Hi Desarrollo.
I hadn't noticed the channel split (13/26).
It's perfect now.
Thanks.
Titio Produções de Áudio
Aug 7, 2025
Hello Desarrollo.
Talking to a friend about this topic, he thinks the input list should be executed as shown in the attached image.
I agree with him, as it's clearer for the people on stage.
Furthermore, with this layout, we're considering more columns in the list to accommodate more information.
Currently, we can only create three columns, correct?
It would be nice for the user to have the option to adjust the width of each column, but I believe that would be much more complicated to do.
But here's my suggestion as well.
Thank you.
mcidesarrollo
Aug 8, 2025
Hi Titio, thanks for your feedback!
We've resolved the issue with calculating column measurements when the channel name is long.
It's now averaged differently and never allows jumping to a second line to make the input list (and the output list) more consistent and readable.
Please reload your page with CTRL+F5, test it, and let us know if it works for you now.
Regarding your suggestions about adding more columns and customizing column widths, due to the nature of the RiderMaker core and the external library we use to convert to PDF, this is extremely complicated, and we also believe it would make things a bit more complicated for users.
However, we haven't ruled it out completely and will continue to think about whether developing this would be feasible and find a way to make it simpler.
Titio Produções de Áudio
Aug 8, 2025
Hi Desarrollo.
I see the layout issue has been resolved.
Perfect.
Thank you very much again.