-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HiDPI seems broken #9
Comments
This is still a problem as far as i'm aware. I'd say this probably has the highest priority as it makes the program unusable in certain use cases, followed by #7 and then #6 Unrelated, but i wasn't sure where else to ask. I was also speaking to some other interesting folks just today about expanding the capabilities of this project in some interesting ways. One idea that was had was to write some python bindings for Project M and use it to allow for much, much more varied visualization options to layer over images. Would you be open to an idea like this? |
ok, I'll look into fixing this issue. I am interested in providing different visualizations with this project. I see a challenge in using the real-time approach of Project M in a way that is compatible to the frame-by-frame method currently used. Also I don't know if I can do that all myself, but I am glad to help if there are others who support that task. |
I pushed some fixes to https://github.com/djfun/audio-visualizer-python/tree/feature-hdpi |
Sadly i don't have access to a HiDPI display atm, so i can't test it myself, but i'll see if i can't find someone to test it. |
tests show it is working better now with c622f29 |
At least under HiDPI gnome, the text size in the preview looks pretty messed up:
And that continues into the exported product:
My current working theory is that UI scaling is messing with the font size, waiting on someone with HiDPI to try in a non-scaled environment to see if it corrects the issue and if so we can continue from there. Could also be something else, though.
The UI looks a bit messy as well, but that's somewhat expected, tbh. It looks about as bad on the mac, so that's a separate issue.
The text was updated successfully, but these errors were encountered: