I was trying a bit around with Ableton but noticed lots of problems with plugins...
On my system I have Windows set to 150% scaling...
I.e. Captain plugins (which have native scaling) show up with broken GUI when auto scaling for them is turned off:
and of course blurry GUI when I leave auto scaling turned on...
...
Rapid shows up like this:
All of these plugins are running fine in FL Studio, Studio One, Reaper...
I was searching a bit but I couldn´t find many topics where user claimed something like this...
Am I doing something wrong here???
Ableton with 4k???
-
- KVRist
- 256 posts since 9 Jun, 2018
No you're not doing anything wrong. Ableton just has shit High DPI handing for plugins on Windows. For best looking plugin support, right click the executable -> Properties -> Compatibility -> Change high DPI settings -> Check "Override high DPI scaling behavior. Scaling performed by:" -> change drop down to "Application". Then relaunch Live.
For best use, favor VST 2 versions of plugins. Lots of problems with VST 3's. Hard to say who is to blame, obviously Ableton should fix this, on the other hand it's been like this for a long time and vendors should make their plugins work, it must be possible because Fabfilter and some others can do it.
I have contacted Ableton support about it, I did get them to open a development ticket for it, but who knows how long that could take. I'm not holding my breath.
The other alternative is to use a different DAW, both Cubase and Bitwig have good high dpi support, at least at 200% scaling.
For best use, favor VST 2 versions of plugins. Lots of problems with VST 3's. Hard to say who is to blame, obviously Ableton should fix this, on the other hand it's been like this for a long time and vendors should make their plugins work, it must be possible because Fabfilter and some others can do it.
I have contacted Ableton support about it, I did get them to open a development ticket for it, but who knows how long that could take. I'm not holding my breath.
The other alternative is to use a different DAW, both Cubase and Bitwig have good high dpi support, at least at 200% scaling.
-
- KVRist
- 256 posts since 9 Jun, 2018
Not really, but neither are some others. Studio 1, and Reaper both suck the same or worse... at least last I tried them.
-
- KVRAF
- Topic Starter
- 5068 posts since 27 Jul, 2004
No, not really...rageix wrote: Wed Mar 16, 2022 11:31 pm Not really, but neither are some others. Studio 1, and Reaper both suck the same or worse... at least last I tried them.
Reaper does a quite good job with plugin scaling as does S1...
They all just struggle with the free Cloud Seek Reverb plugin...
Reaper isn´t perhaps the best when it comes to upscaling plugins without scale functions but at least it shows everything properly... Captain Plugins scale properly, Rapid does...
I already find quite silly in Ableton that every plugin is set to auto scale by default...
Right clicking every plugin and changing it to auto scale off...really??
-
- KVRian
- 898 posts since 26 Jul, 2018 from Germany
Fo what reason?
I use a 5k iMac, I scale the applications individually. For example, Google Chrome is set to 110% (page zoom), Ableton Live is set to 125% (zoom display).
-
- KVRAF
- Topic Starter
- 5068 posts since 27 Jul, 2004
Because for my eye sight even with a 43" monitor I feel most comfortable when having set windows to 150% and this is what the other programms follow (by default)...Rastkovic wrote: Thu Mar 17, 2022 2:29 amFo what reason?
I use a 5k iMac, I scale the applications individually. For example, Google Chrome is set to 110% (page zoom), Ableton Live is set to 125% (zoom display).
I could live with 125% if I had to but the gained work space difference is too small as that it would be worth to consider...
-
- KVRAF
- 9146 posts since 7 Oct, 2005
All the plugins I have are running fine in Ableton Live 10/11. I have 4k 27" monitor with 150% scaled Windows OS.
Actually, I feel that Ableton Live is the standard that the plugins developer test on before any other DAW! For example, Rob Papen vst3 version of the plugins, run well in Ableton Live but they run just like the first image in the first post in Cubase and Studio One! So, one of the reasons that I'm using Live mostly now (also Bitwig) is because it is the most problems free when it comes to plugins (and also most midi hardware!).
Plugins that I use are from Arturia, NI, u-he, Ozone, Synapse Audio, XLN Audio, Steinberg, Rob Papen, Tone2 and some others.
Actually, I feel that Ableton Live is the standard that the plugins developer test on before any other DAW! For example, Rob Papen vst3 version of the plugins, run well in Ableton Live but they run just like the first image in the first post in Cubase and Studio One! So, one of the reasons that I'm using Live mostly now (also Bitwig) is because it is the most problems free when it comes to plugins (and also most midi hardware!).
Plugins that I use are from Arturia, NI, u-he, Ozone, Synapse Audio, XLN Audio, Steinberg, Rob Papen, Tone2 and some others.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRian
- 898 posts since 26 Jul, 2018 from Germany
Okay! I can only suggest to scale the applications individually. I don't use the OS scale function, so I never experienced the problems like you mentioned in the first post.Trancit wrote: Thu Mar 17, 2022 9:23 amBecause for my eye sight even with a 43" monitor I feel most comfortable when having set windows to 150% and this is what the other programms follow (by default)...
-
- KVRAF
- Topic Starter
- 5068 posts since 27 Jul, 2004
You are right...Rastkovic wrote: Thu Mar 17, 2022 11:34 amOkay! I can only suggest to scale the applications individually. I don't use the OS scale function, so I never experienced the problems like you mentioned in the first post.Trancit wrote: Thu Mar 17, 2022 9:23 amBecause for my eye sight even with a 43" monitor I feel most comfortable when having set windows to 150% and this is what the other programms follow (by default)...
I set the scaling of Windows to 100% and scaled Ableton internally and now the plugins load normal...
Weird...
-
- KVRAF
- Topic Starter
- 5068 posts since 27 Jul, 2004
Ableton behaves really weird...
I set the OS scaling to 100% where all plugins load in Ableton like they should...including Captain Plugins and Rapid...
Later on I set the scaling back to my 150%...
Captain Plugins continue to load correctly but Rapid fell back into it´s previous behaviour...
I cannot leave it at 100% though as the text/icons i.e. in Ableton and for Windows of the OS is simply too small for me and i.e. Reaper hasn´t got an internal scaling for the programm itself... just for the tracks...
I set the OS scaling to 100% where all plugins load in Ableton like they should...including Captain Plugins and Rapid...
Later on I set the scaling back to my 150%...
Captain Plugins continue to load correctly but Rapid fell back into it´s previous behaviour...
I cannot leave it at 100% though as the text/icons i.e. in Ableton and for Windows of the OS is simply too small for me and i.e. Reaper hasn´t got an internal scaling for the programm itself... just for the tracks...
-
- KVRian
- 643 posts since 28 Oct, 2010
I've had a ton of issues with plugins running in Live and 4K on Windows. It's like Live doesn't always know how to properly communicate the window size, resolution, and scaling to all plugins. All sorts of weird things happen like plugins rendering at a huge but being cropped even or rendering in low res no matter what you do.
Bitwig is much better than Live in this regard, but I've found Cubase to be the best when handling VST plugins at hiDPI.
Bitwig is much better than Live in this regard, but I've found Cubase to be the best when handling VST plugins at hiDPI.
-
- KVRAF
- Topic Starter
- 5068 posts since 27 Jul, 2004
I didn´t found a difference between Cubase, Studio One and Reaper... while Cubase is worse than the other 2 as it has problems with Image Lines Maximus...
Maximus is clearly resizeable which works flawless in the other 2 but Cubase refuses to show the resize handles on the plugin... this may not happen that competitors seem to know the VST specs better than the inventor itself...
On my system Ableton is by far the worst...
But here the one which did the best job in terms of HDPI and plugins is by far FL Studio...
Of these it is the only one which can handle i.e. the free CloudSeed and I do not have any plugin installed which causes any errors in FLS
Maximus is clearly resizeable which works flawless in the other 2 but Cubase refuses to show the resize handles on the plugin... this may not happen that competitors seem to know the VST specs better than the inventor itself...
On my system Ableton is by far the worst...
But here the one which did the best job in terms of HDPI and plugins is by far FL Studio...
Of these it is the only one which can handle i.e. the free CloudSeed and I do not have any plugin installed which causes any errors in FLS
-
- KVRAF
- 4589 posts since 7 Jun, 2012 from Warsaw
Nah, works for me.Ableton just has shit High DPI handing for plugins on Windows
I've been using Ableton in 4K with custom scaling on Windows for 4 years now. No issues at all apart from one free, boutique plugin.
This. So what exactly you find wrong with Ableton?For best looking plugin support, right click the executable -> Properties -> Compatibility -> Change high DPI settings -> Check "Override high DPI scaling behavior. Scaling performed by:"
Blog ------------- YouTube channel
Tricky-Loops wrote: (...)someone like Armin van Buuren who claims to make a track in half an hour and all his songs sound somewhat boring(...)
Tricky-Loops wrote: (...)someone like Armin van Buuren who claims to make a track in half an hour and all his songs sound somewhat boring(...)
-
- KVRist
- 256 posts since 9 Jun, 2018
First off you shouldn't need to force Ableton to not scale your plugins by changing the executable DPI settings. I don't have to do that with Cubase or Bitwig, they both just work.
Secondly Ableton has issues with various VST 3's even with said DPI settings in place, although VST 2 seem to work for the most part.
In short Ableton handles windows scaling > 100% like shit and it's been broken for over 5 years.