I am getting a too long file name issue and file is stopping to compile

[GeorgeZaher]

[othmar52]

filenames are indeed very long as it holds the keynumber and the hex color for each key

f41#f1b4b0-42#8f1f17-48#ed9e98-49#bf2a1f-50#DE4439-56#DE4439-58#DE4439-66#DE4439-67#DE4439-71#DE4439-72#DE4439-74#DE4439-76#DE4439-82#DE4439-84#DE4439-.png

for this frame

i have to admit that i never used this on windows. on *nix machines this seems to be not an issue but it is indeed a quick & dirty approach.
maybe i'll find some time soon to replace the current filenames for the frames with a checksum to get rid of this compatibility issue. but i can't promise...

actually i was aware of this potential problem back in the days when i created this script (see this comment in line 510)

[GeorgeZaher]

Hello, This is the output I got, also this is without audio is that normal? is there a way to get audio? [image: image.png] Best Regards George

…

On Tue, Jan 11, 2022 at 12:53 AM othmar52 ***@***.***> wrote: filenames are indeed very long as it holds the keynumber and the hex color for each key f41#f1b4b0-42#8f1f17-48#ed9e98-49#bf2a1f-50#DE4439-56#DE4439-58#DE4439-66#DE4439-67#DE4439-71#DE4439-72#DE4439-74#DE4439-76#DE4439-82#DE4439-84#DE4439-.png for this frame [image: example-frame] <https://user-images.githubusercontent.com/7056051/148851248-04c2623b-4bb5-4d3c-bb9f-081ec03e110f.png> i have to admit that i never used this on windows. on *nix machines this is not an issue but it is indeed a quick & dirty approach. maybe i'll find some time soon to replace the current filenames for the frames with a checksum to get rid of this compatibility issue. but i can't promise... — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVC7OQ4LJ6QKSOOGUYCGPDUVNPPZANCNFSM5LUWW67A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[othmar52]

... is there a way to get audio? ...

Please see the README.md of this project