18 posts
Page 1 of 1
Once I launched 3.2.2 I was really astonished that the engineers at Presonus decided to put this into the "will not be fixed" pool as there is now a little message when you switch over to High DPI Mode: "some plugins will be shown smaller when they cant be scaled" - haha - is this real?

Cubase, Ableton, Bitwig, Reaper - every DAW can be run in something like "high dpi mode" WITH scaled VST plugins! (wether they can be scaled or not!)

So why this cant be also be done in S1?

Is it so impossible to add an option in the program to give the users the possibility to always scale the plugins in high dpi mode?

| monoPLAN | Deep House Producer | http://www.monoplan-music.com
Gear: Win 10 Pro 64-bit, i7 6700k, 16 Gig DDR4 RAM, 28" 4K monitor, Focusrite Scarlett 2i4, Studio One 3.2.2 Pro
User avatar
by renedale on Fri May 20, 2016 8:41 am
Here you can see two DAW's side by side: Studio One in High DPI Mode vs. Bitwig

http://i.imgur.com/ENotHgN.jpg

Windows Resolution: 3840x2160

Any comment?

| monoPLAN | Deep House Producer | http://www.monoplan-music.com
Gear: Win 10 Pro 64-bit, i7 6700k, 16 Gig DDR4 RAM, 28" 4K monitor, Focusrite Scarlett 2i4, Studio One 3.2.2 Pro
User avatar
by jpettit on Fri May 20, 2016 8:52 am
This is not a bug. It is a Feature Request.
S1 uses Windows Scaling built in to the OS. The Plugin has to use the same approach.
It looks like other DAWs have figures a work around. Your picture would be a good to add to your FR posted here. http://answers.presonus.com/questions/s ... e-requests

My Website, Free Studio One Advance Training
SPECS: Win 11 22H2, 18 Core i9: 32Gb DDR4 ram, 42" 4K monitor, StudioLive 24/16, Faderport16, Central Station Plus, Sceptre 6, Sceptre 8, Temblor T10, Eris 4.5, HP60, Studio One Pro latest, Test Platforms Reaper latest, Cakewalk latest
User avatar
by renedale on Fri May 20, 2016 9:01 am
jpettit wroteThis is not a bug. It is a Feature Request.
S1 uses Windows Scaling built in to the OS. The Plugin has to use the same approach.
It looks like other DAWs have figured a work around. Your picture would be a good to add to your FR posted here. http://answers.presonus.com/questions/s ... e-requests


Done:
http://answers.presonus.com/8138/plugin ... ton-reaper

But really - how can somebody say that this is not a bug?
I mean, NO one could use Studio One in that resolution in High DPI mode. It's just not readable.
Presonus cares? Does not seem so :cry:

| monoPLAN | Deep House Producer | http://www.monoplan-music.com
Gear: Win 10 Pro 64-bit, i7 6700k, 16 Gig DDR4 RAM, 28" 4K monitor, Focusrite Scarlett 2i4, Studio One 3.2.2 Pro
User avatar
by jpettit on Fri May 20, 2016 9:19 am
renedale wrote
jpettit wroteThis is not a bug. It is a Feature Request.
S1 uses Windows Scaling built in to the OS. The Plugin has to use the same approach.
It looks like other DAWs have figured a work around. Your picture would be a good to add to your FR posted here. http://answers.presonus.com/questions/s ... e-requests


Done:
http://answers.presonus.com/8138/plugin ... ton-reaper

But really - how can somebody say that this is not a bug?
I mean, NO one could use Studio One in that resolution in High DPI mode. It's just not readable.
Presonus cares? Does not seem so :cry:


I will vote for it.
I deal with it on a 40" 4K monitor.
It has been that way since the GUI was rewritten using new Windows graphic libs to support High DPI on Windows.
It would be interesting to see how the other DAWs are doing it.

Presonus cares? Does not seem so :cry

The developers are by the book in terms of normal OS behavior. They do not do software tricks or workarounds due to the side effects . If there is a legit way to do it by the rules they will support it.

My Website, Free Studio One Advance Training
SPECS: Win 11 22H2, 18 Core i9: 32Gb DDR4 ram, 42" 4K monitor, StudioLive 24/16, Faderport16, Central Station Plus, Sceptre 6, Sceptre 8, Temblor T10, Eris 4.5, HP60, Studio One Pro latest, Test Platforms Reaper latest, Cakewalk latest
User avatar
by profirhino on Fri May 20, 2016 2:36 pm
This would be a radical feature, no doubt ! :+1
Anybody using two or more screens will agree, the distance between your speakers dictates the distance between the screens and your eyes, in my example that means about 1m (2x 26" @ 1920x1200, a 3rd on the side - so not even 4k or something).
You absolutely cannot read anything in many plugin UIs, take those Korgs or Toontrack Superior as sad examples for abandoned UI development. :twisted:
At least Arturia have solved this longstanding problem yesterday ...
But allow me two remarks :
- to be really useful, you would have to be able to at least store "scaling on/off" per plugin, even better would be individual zoom factors, as some of the better UIs would not benefit from scaling, on the contrary.
Sounds like a lot of work.
- on a closely related note, the subminiature note name fonts in S1's piano editor are borderline unusable too here at max zoom, I'm sure there are other examples too.

any visibility improvements would be most welcome indeed,
Rhino

off to vote for the FR !
User avatar
by Funkybot on Fri May 20, 2016 5:23 pm
Uhm guys...there's been a feature request for this since April 2nd: http://answers.presonus.com/7151/plugin ... 7151#q7151

AMD Ryzen 3950X, ASUS Creator x570 Mobo, 32GB HyperX Predator RAM (3600mhz), Radeon™ RX 5500 XT 4GB GDDR6 graphics card, RME Fireface 800, Windows 10 Pro, Studio One 5, Reaper 6, Cubase 10.5, Avid Artist Mix (EuCon please), Behringer X-Touch One, MIDI Fighter Twister, various other MIDI control surfaces and hardware instruments
User avatar
by profirhino on Fri May 20, 2016 5:51 pm
Funkybot wroteUhm guys...there's been a feature request for this since April 2nd: http://answers.presonus.com/7151/plugin ... 7151#q7151

voted up, of course. :+1
sorry, keeping track of that database is a mighty challenge.
I like a regular forum better personally ...
ymmv,
Rhino
User avatar
by hebex on Sat Feb 11, 2017 3:39 pm
Wow, I guess this is the problem I am having. Just bought a highest spec Dell XPS 15 9550 laptop with a high screen resolution. Sending the monitor signal to a 26 inch monitor, my Omnisphere 2 plugin in S1 (latest version) is so small its practically useless.

Any solution in sight, PLEASE!?

:shock:
User avatar
by garryknight on Sat Feb 11, 2017 3:45 pm
I'm pretty sure that the problem is with Omnisphere, not Studio One, but have you checked the 'Enable High DPI Mode' option in the General tab of Stuio One's Options dialog?

I have exactly the same problem with some VSTs on my MS Surface Pro 3. I put in a feature request with the VST company to make a resizable GUI and some of them respond.

Garry Knight
Studio One 3 Professional
Melodyne Editor 4, NI Komplete 11
Focusrite Scarlett 2i4 audio interface
Windows 10 Professional 64-bit, 16 GB RAM, Core i5
Microsoft Surface Pro 3, Core i7, 8GB RAM, 128 GB SSD
Nektar Impact LX49+, Samson Graphite 25, and Korg microKey 25 MIDI controllers
Novation ZeRO SL MkII mixing control surface
Korg nanoKontrol 2 mixing control surface
Reaper, Logic Pro X, GarageBand
https://soundcloud.com/garryknight
User avatar
by jpettit on Sat Feb 11, 2017 3:48 pm
hebex wroteWow, I guess this is the problem I am having. Just bought a highest spec Dell XPS 15 9550 laptop with a high screen resolution. Sending the monitor signal to a 26 inch monitor, my Omnisphere 2 plugin in S1 (latest version) is so small its practically useless.

Any solution in sight, PLEASE!?

:shock:

Change your OS scaling factor for the UI to something higher than 100%.
You may have to run it at a larger amplification for a 26" screen.

My Website, Free Studio One Advance Training
SPECS: Win 11 22H2, 18 Core i9: 32Gb DDR4 ram, 42" 4K monitor, StudioLive 24/16, Faderport16, Central Station Plus, Sceptre 6, Sceptre 8, Temblor T10, Eris 4.5, HP60, Studio One Pro latest, Test Platforms Reaper latest, Cakewalk latest
User avatar
by hebex on Sat Feb 11, 2017 4:54 pm
Your tips helped, thanks guys, really appreciate it!
User avatar
by arthurklisiewicz1 on Sat Nov 26, 2022 12:21 am
so this was posted in 2016 and I am replying here with the question in 2022 (5 years later).
IS THE PROBLEM RESOLVED ?

just installed S1 v6 and I cannot use it because all plugins are super tiny small

Intel i9/24-core, RAM-64Gb, M.2-NVME-4TB, 4xHD-18Tb
Win10/64-Pro. Studio One + (v6.2+)
BEHRIUNGER-UMC-404, KompleteKontrol KBD Mk1/61key, Arturia-MINI-LAB mk2 (25key), Novation LAUNCH-CONTROL-XL, M-AUDIO - TrigerFinger, M-AUDIO Studio Monitors.
User avatar
by PreAl on Sat Nov 26, 2022 6:13 am
arthurklisiewicz1 wroteso this was posted in 2016 and I am replying here with the question in 2022 (5 years later).
IS THE PROBLEM RESOLVED ?

just installed S1 v6 and I cannot use it because all plugins are super tiny small


Ask Native Instruments.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by paulbrown4 on Sun Nov 27, 2022 10:52 pm
I have a 4K monitor and it happens to a lot of my plugins. The best solution I found so far is to change it for the S1 app in the Windows application directory by finding the Studio One.exe file (mine is in C:\Program Files\PreSonus\Studio One 5). Right click on it, go to Properties, then the Compatibility tab, then at the bottom click Change high DPI settings (or Change settings for all users, your choice), again at the bottom High DPI scaling override, check the box and pick Scaling performed by : System (or System (Enhanced), it seems to work the same). You can also do it for all users if you use that option. Hit OK 3x then restart S1.
User avatar
by AAV on Tue Nov 29, 2022 11:30 am
Many thanks to Paulbrown4 for this great tip! Older plugins like GForce's Minimonsta had been completely unusable for a long time, with their postage stamp sized GUI's on my 4K 32" monitors. This seems to have totally resolved the problem. Plugs like Kontakt which have been painful to use are now back to a useful and more useable size.
Awesome and thanks!

Studio One 6.5.2 Pro, Audient ID4 mark II,
Gigabyte Designair Z390, 32GB DDR4 3200, Intel i9-9900K 4.8 GHZ, 2 TB & 1 TB SSD, 3 x 1TB 7200 rpm HDD, Windows 11 Pro 64 22H2
User avatar
by ericma2 on Tue Nov 29, 2022 6:51 pm
Wow this is very good information. Thank you! This is very helpful.. unlike the canned responses we get sometimes in the forums.

2013 Mac Pro Trashcan 8 Core 64 GB Ram
macOS Monterey 12.7.3
Studio One 6.5.2
Pro Tools 21.12 <- Finally left Pro Tools - THANKS S1!!!!
Euphonix Artist Mix firmware 1.5.6.0
Eucon v4.8.3
User avatar
by PreAl on Thu Dec 01, 2022 12:21 pm
I agree a very good helpful response, I wish I had thought of that.

Ultimately this issue is with the plugins not supporting 4K, that's the reality of the situation.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.

18 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 61 guests