Jean-Michaël Celerier

@yurivict yes it is optional, if it is not part of the build it justy won't be used

(it'd be nice to get it to work on freebsd though... on my linux it iterates so much faster compared to std::filesystem or fts it's not even funny, on folders...

ouch, actually you shouldn't be able to edit the code at all if the score is playing right now as it's unsafe

thanks, any chance you could build score with debug symbols? (-DCMAKE_BUILD_TYPE=Debug and no stripping). Here on ArchLinux the window correctly closes when deleting the device from the device explorer :|

this should have been fixed since 3.1.12, can you check on the latest release ? https://github.com/ossia/score/releases/v3.1.13

very weird, thanks for the report! @thibaudk would you be able to look into this maybe? Is it at any time, only when the window is maximized? Do you know...

hmmmm... I'm wondering if this is because score may try to access the soundcard exclusively, which would cause XFCE's sound volume widget disappear for a few milliseconds or something like...

thanks for the report, I'll try on windows with D3D. Most likely the shader uses a function name which is ok under opengl and not under direct3D

hello! are you trying to run the ./ossia-score binary directly or running it through the ossia-score-x11 scripts ?

for the icui18n.so.67 issue it's been fixed on master (see #1498 )