Ernst 29 Posted November 1, 2013 Share Posted November 1, 2013 Hi, I have some obeservations on CoverArt 4 that don't seem to have been discussed yet. Here goes: MB Server Version 3.0.5050.37565 CoverArt version 4.0.3.2 Windows 7 ultimate @ 1920:1080 DPI(PPI) @ 125% CoverArt Indicator overlays: I have my monitor (actually my TV) set at 125% DPI/PPI (windows setting for scaling) so it is no to small to read. When I apply indicator overlays is CoverArt, the ovelays are getting cropped or cut of at the lower right corner. When I set my screen to 100% DPI however, this is not the case. Furthermore, this did not happen in MB2 with CA3. Ebr, could you make the indicator overlays DPI independent? Below is an example at an even worse 150% DPI Link to comment Share on other sites More sharing options...
Solution ebr 14898 Posted November 1, 2013 Solution Share Posted November 1, 2013 Yeah, this is actually a known issue. I think it is a bug in the GDI stuff but, honestly, I haven't had time to try and track it down much further. It only affects a small number of people because CA runs on the server machine. So, it only affects you if your server is also an HTPC and you have your DPI bumped up. 1 Link to comment Share on other sites More sharing options...
Ernst 29 Posted November 1, 2013 Author Share Posted November 1, 2013 That is very unfortunate, as you guessed, I am running the server on my HTPC and it sucks to have to fall back to 100% to have the items processed by CA and then go back to 125%. It does do the trick though untill the next item gets added (the cashed images will be unaltered) I thought it might have been an easy thing to do as MB2 or rather CA3 doesn't have this issue. Pardon my ingnorence, but what is the "GDI stuff" ? Anyway, thanks for the reply. Link to comment Share on other sites More sharing options...
ebr 14898 Posted November 1, 2013 Share Posted November 1, 2013 Sorry - code-speak. GDI is the built-in graphics processing in the platform I'm using to develop the app (.net). The reason it is only in MB3 is because all of this graphics processing was re-done for better performance and memory management. So, I'm using different functions/features of the library. Link to comment Share on other sites More sharing options...
Ernst 29 Posted November 1, 2013 Author Share Posted November 1, 2013 Got it, hope it will someday be solved though Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now