On high-res display: The minimum size of the selected skin is bigger than your screen resolution

[Nico Schlömer]

I just tried running mixxx for the first time on a 1920x1080 laptop display. Much to my surprise, almost all themes fail to display properly with the warning message
```
The minimum size of the selected skin is bigger than your screen resolution
```
Indeed, the top section with the knobs and wheels is way too large. (Screenshot attached. -- Geez, launchpad is clumsy about that.)

[Daniel Schürmann (daschuer)]

In Mixxx 2.1 you can adjust the skin size in interface preference.
Even though it has an auto mode it should be at 100 % by default which is not the case in your screenshot.ile

Please Look into your ~/.mixxx/mixxx.cfg
Ther should be none of these for default settings:
ScaleFactor
ScaleFactorAuto 0

Did you copy this file from your old laptop?

[Be (be.ing)]

Please test whether this issue is still present in the 2.2 release candidate.

[Nico Schlömer (nschloe)]

Thanks for the replies.

> Ther should be none of these for default settings:

Indeed. (See below.)

> Did you copy this file from your old laptop?

No, I deleted the `~/.mixxx/` config and started anew.

```
[Auto DJ]
EnableRandomQueueBuff 0
RequeueBuff 0
Transition 10
UseIgnoreTimeBuff 0

[BPM]
AnalyzeEntireSong 1
BPMDetectionEnabled 1
BPMRangeEnd 140
BPMRangeStart 70
BeatDetectionFixedTempoAssumption 1
FastAnalysisEnabled 0
FixedTempoOffsetCorrection 1
ReanalyzeWhenSettingsChange 0

[Channel1]
keylock 0
quantize 0
vinylcontrol_enabled 0

[Channel2]
keylock 0
quantize 0
vinylcontrol_enabled 0

[Channel3]
keylock 0
quantize 0
vinylcontrol_enabled 0

[Channel4]
keylock 0
quantize 0
vinylcontrol_enabled 0

[Config]
InhibitScreensaver 1
Path /usr/share/mixxx/
Version 2.1.3

[Controls]
PositionDisplay 1

[Deere]
sampler_row_current 0
show_bpm_info 1
show_crossfader 1
show_more_hotcues 0
show_parallel_waveforms 1
show_starrating 0
show_track_info 1

[EffectRack1]
show 1

[EffectRack1_EffectUnit1]
focused_effect 0
group_[Auxiliary1]_enable 0
group_[Auxiliary2]_enable 0
group_[Auxiliary3]_enable 0
group_[Auxiliary4]_enable 0
group_[BusCenter]_enable 0
group_[BusLeft]_enable 0
group_[BusRight]_enable 0
group_[BusTalkover]_enable 0
group_[Channel1]_enable 1
group_[Channel2]_enable 0
group_[Channel3]_enable 0
group_[Channel4]_enable 0
group_[Headphone]_enable 0
group_[MasterOutput]_enable 0
group_[Master]_enable 0
group_[Microphone2]_enable 0
group_[Microphone3]_enable 0
group_[Microphone4]_enable 0
group_[Microphone]_enable 0
group_[PreviewDeck1]_enable 0
group_[Sampler10]_enable 0
group_[Sampler11]_enable 0
group_[Sampler12]_enable 0
group_[Sampler13]_enable 0
group_[Sampler14]_enable 0
group_[Sampler15]_enable 0
group_[Sampler16]_enable 0
group_[Sampler1]_enable 0
group_[Sampler2]_enable 0
group_[Sampler3]_enable 0
group_[Sampler4]_enable 0
group_[Sampler5]_enable 0
group_[Sampler6]_enable 0
group_[Sampler7]_enable 0
group_[Sampler8]_enable 0
group_[Sampler9]_enable 0
mix 1
show_parameters 0

[EffectRack1_EffectUnit2]
focused_effect 0
group_[Auxiliary1]_enable 0
group_[Auxiliary2]_enable 0
group_[Auxiliary3]_enable 0
group_[Auxiliary4]_enable 0
group_[BusCenter]_enable 0
group_[BusLeft]_enable 0
group_[BusRight]_enable 0
group_[BusTalkover]_enable 0
group_[Channel1]_enable 0
group_[Channel2]_enable 1
group_[Channel3]_enable 0
group_[Channel4]_enable 0
group_[Headphone]_enable 0
group_[MasterOutput]_enable 0
group_[Master]_enable 0
group_[Microphone2]_enable 0
group_[Microphone3]_enable 0
group_[Microphone4]_enable 0
group_[Microphone]_enable 0
group_[PreviewDeck1]_enable 0
group_[Sampler10]_enable 0
group_[Sampler11]_enable 0
group_[Sampler12]_enable 0
group_[Sampler13]_enable 0
group_[Sampler14]_enable 0
group_[Sampler15]_enable 0
group_[Sampler16]_enable 0
group_[Sampler1]_enable 0
group_[Sampler2]_enable 0
group_[Sampler3]_enable 0
group_[Sampler4]_enable 0
group_[Sampler5]_enable 0
group_[Sampler6]_enable 0
group_[Sampler7]_enable 0
group_[Sampler8]_enable 0
group_[Sampler9]_enable 0
mix 1
show_parameters 0

[EffectRack1_EffectUnit3]
focused_effect 0
group_[Auxiliary1]_enable 0
group_[Auxiliary2]_enable 0
group_[Auxiliary3]_enable 0
group_[Aux...

[Nico Schlömer (nschloe)]

> Please test whether this issue is still present in the 2.2 release candidate.

Couldn't find the RC [1]. Is there a working PPA?

[1] https://github.com/mixxxdj/mixxx/releases

[Be (be.ing)]

Mixxx 2.2 RC is here: https://mixxx.org/download/

[Nico Schlömer (nschloe)]

@Be Thank you.

I now installed 2.2 RC from the PPA, wiped ~/.mixxx/ and fired it up. Same issue unfortunately.

[Be (be.ing)]

What distribution and what version of GNOME are you using? Try running "export QT_AUTO_SCREEN_SCALE_FACTOR=0" then running Mixxx on the command line.

[Nico Schlömer (nschloe)]

This is on Ubuntu 18.10 with Gnome 3.30.1. The variable QT_AUTO_SCREEN_SCALE_FACTOR is unset by default. When explicitly setting
```
export QT_AUTO_SCREEN_SCALE_FACTOR=0
```
it works fine. (In fact I'd like the interface a little bit larger now; not sure if that can be achieved.)

[Be (be.ing)]

I am surprised that Qt is deciding to scale the GUI with a 1920 x 1080 screen. What are the physical dimensions of your screen? What is the make and model of your screen?

What is the scale factor you have configured in the Display section of GNOME Settings?

I am also confused why this happened with Mixxx 2.1. Did you compile Mixxx 2.1 yourself with the "qt5=1" option? The PPA builds for 2.1 use Qt 4.

You can manually set a scale factor with the QT_SCREEN_SCALE_FACTORS environment variable as documented here: http://doc.qt.io/qt-5/highdpi.html#high-dpi-support-in-qt Note that the waveforms will flicker if you set a fractional scale factor (Bug #1762092).

[Nico Schlömer (nschloe)]

> What are the physical dimensions of your screen? What is the make and model of your screen?

This is a Thinkpad X280 (12.5 inch 16:9, 1920 x 1080 pixel, 176 PPI).

> What is the scale factor you have configured in the Display section of GNOME Settings?

100%. I do sometimes enable "Large Text" from the Accessibility settings though. I tried it enabled and disabled, doesn't seem to matter.

> Did you compile Mixxx 2.1 yourself with the "qt5=1" option?

I just took mixxx from Ubuntu.

[Be (be.ing)]

Qt uses the EDID information from your monitor to determine the scale factor. Maybe your monitor's EDID information is incorrect?

[Nico Schlömer (nschloe)]

An interesting suggestion.
```
xrandr --props
```
gives
```
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 280mm x 160mm
 non-desktop: 0
  supported: 0, 1
   1920x1080 59.96*+

```
Looks alright. Perhaps the `maximum` setting is off?

[Daniel Schürmann (daschuer)]

Ubuntu has packed a qt5 build of Mixxx 1.3
See: https://packages.ubuntu.com/cosmic/mixxx
So we have strong issue that every Ubuntu cosmic user uses an untested alpha build.
It is probably better to use the 2.2 alpha instead.

Since Ubuntu usually does not update Mixxx this issue will last for years. odd.

[Daniel Schürmann (daschuer)]

Reported the bug upstream
https://bugs.launchpad.net/mixxx/+bug/1804513

[Daniel Schürmann (daschuer)]

Since 2.2 is also effected we should try check a workaround for Ubuntu cosmic.

[Be (be.ing)]

What version of the qtbase-opensource-src do you have installed? Qt 5.12 has changed how it calculates scale factors to prefer rounding down:
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=5e6bbbc1b86905c4c64aba34632b668ef44dc8f4

Debian has backported this patch to Qt 5.11 and previously had their own patch for Qt 5.10:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884956
https://salsa.debian.org/qt-kde-team/qt/qtbase/commits/c4ce48d999a05317c281d3746b5f82316ae47fc3/debian/patches/hidpi_scale_at_192.diff

[Nico Schlömer (nschloe)]

> What version of the qtbase-opensource-src do you have installed?

Ubuntu 18.10 has qtbase-opensource-src 5.11.1+dfsg-7ubuntu1. Apparently, the fix is not contained there yet.

[Be (be.ing)]

That package has an earlier version of the patch from Qt, which is not what was ultimately merged for Qt 5.12:
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=23b139038a1dc9a769a358ab112453abcdd39290

Although it looks like the latest patch in Debian is a mix of the old and new patch from incorrectly resolved merge conflicts... :/
https://salsa.debian.org/qt-kde-team/qt/qtbase/commit/0c8694457c117a082f3d9831f164e22939f68102

I am marking this as Invalid and removing from a milestone because it is an upstream bug, not a Mixxx bug.

[alexandre meerson (alex-or)]

Hi, I'm using Ubuntu Disco 19.04 and I have the same problem with mixxx 2.2 about the skins files size, on a 1920x1080 HDMI monitor, and it doesn't load any low res. additional skins (1280x800 w-xga or uxga...) ;
But I use too, now, the the great "DarkMetal" skin wich one is a little bit smaller and have a resizable songs list.
I've tried to modify the mixxx.conf as described previously but it doesn't take care of the new parameters. Anyway I think mixxx is still a great DJ software ! I hope an update will come to resolve the problem on Ubuntu 19.04...Thanks.
If someone heard about an extension to zoom out a window without downscaling the desktop it could be great.

[ronso0 (ronso0)]

Please also try this solution from the Troubleshooting wiki:
https://www.mixxx.org/wiki/doku.php/troubleshooting#graphical_user_interface_gui_is_too_big_or_too_small

Quoted for Linux:

Open a shell console and type:
export QT_AUTO_SCREEN_SCALE_FACTOR=0
before running Mixxx from that shell.

Alternatively, you can manually set a scale factor by running
export QT_SCREEN_SCALE_FACTORS=your-scale-factor

To avoid needing to run these commands every time you run Mixxx, you can add them to /etc/profile or ~/.bashrc (assuming you are using Bash as your shell), log out, and log back in.

[alexandre meerson (alex-or)]

Hi, it works perfectly with this command ! Thank you very much !

[alexandre meerson (alex-or)]

By the way, after spending some time about "avoid needing to run the command every time", I've found this solution too :
edit the "mixxx.desktop" file in "/usr/share/applications" folder, and replace the "Exec=mixxx" line with this one :

"Exec=gnome-terminal -e /usr/share/applications/mixxx.desktop & export QT_AUTO_SCREEN_SCALE_FACTOR=0 mixxx ;mixxx"

After it's done you have to "allow the permission to execute..." in properties, and it looks to work fine when starting Mixxx from the Dock. Thanks.

[ronso0 (ronso0)]

@alex-or Are you sure this works? Or is it just a typo?
inside mixxx.desktop you're calling mixxx.desktop again?

Apart from gnome-terminal not being available on all distros,
shouldn't the Exec command be
Exec=gnome-terminal -e "export QT_AUTO_SCREEN_SCALE_FACTOR=0 && mixxx"

[ronso0 (ronso0)]

@alex-or
Sry for the noise, your launcher command just looked so unusual compared to those I encountered so far.

Re: DarkMetal fix
please post fixes &/ mods for unofficial skins in the respective forum thread and link them here.
thx!

[alexandre meerson (alex-or)]

@ronsoO
Hi, about the upscaling command in the mixxx.desktop, while spend some times on an update patch on the DarkMetal skin upscaling, I've noticed that it's now possible to use a more std command in the file.
So I would like to share it ; the command is :

gnome-terminal -e /usr/share/applications/mixxx.desktop & export QT_AUTO_SCREEN_SCALE_FACTOR=0 && mixxx

It now seems to works with the officials skins too.

Greetings.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9524