Studio One 4.1 is out and “Enable High DPI Mode” option is back :-)

[SLiC]

Studio One 4.1 Release Notes


New features and Improvements:

• Support for PreSonus ATOM Production and Performance Pad Controller
• New Pipeline XT plug-in for routing of external effects
• Extended Note Repeat with keyboard remote
• Tempo Automation
• Beat-linear timeline option
• Improved manual tempo mapping with Scale Time tool
• Tap tempo via keyboard shortcut
• AAF export options (including embedded AAF support)
• Import Song Data from song template
• New “Cue mix mute follows channel” option
• New look for External Device panels and QWERTY Keyboard
• The macro bar now stores the last page viewed per editor
• Select Highest or Lowest notes more accurate when overlapped
• Key command mapping for "Song Setup" dialog
• Tempo map added to rendered click file
• Improved zoom and scroll behavior in Pattern Editor
• [Windows 10] System DPI scaling option for third-party plug-ins
• [Windows] “Enable High DPI Mode” option is back

The following issues have been fixed:

• [macOS Mojave] Scrambled icons in message boxes
• [macOS] Accessibility zoom breaks context menu
• [macOS] Deadlock on clicking main menu bar with system file selector open
• [Windows] Help Viewer doesn't adapt to different monitor DPI
• [Melodyne] Editor not immediately opening on edit
• [Chord Track] Wrong detection inside arpeggios
• [Chord Track] Accidentals not displayed correctly in the pop-up selector
• [Drum Editor] Unwanted double notes when duplicated
• [Drum Editor] Duplicating notes with swing are placed in wrong location
• [Track Inspector] Automation controls background missing
• [Track Inspector] Event FX container doesn't remember size
• [Track Inspector] Automation parameter select-box text is hidden by color field
• [Presence XT] Ping Pong looping issue with short samples
• [Presence XT Editor] Crash on copying zones
• [Impact XT] Amp envelope should be exponential
• [Impact XT] Missing "Cancel" button on initial sample search
• [Impact XT] Pad Names are overwritten while editing (user vs file name)
• Macro toolbar scripting error
• Pitch editing doesn't accept B from keyboard, changes it to A#
• Enabling Note Repeat aftertouch + playing aftertouch causing infinite note
• REX file import issue when song sample rate is different from file
• Playback of stretched audio sometimes incorrect
• Remotes do not generate undo steps for all parameter changes
• Wrong waveform drawing when creating loop range
• Potential crash when opening detached audio editor
• Channel macros lost connection to parameters on Import Song Data
• Steps placement is incorrect when duplicating a Pattern
• Plug-in thumbnail icon not inverted in light theme
• Applying Mute on mouse down causes audible clicks
• Crash on save after removing Multi Instrument
• GUI artifacts while scrolling w/ TAB thru track name fields
• Copying an event from a folder pastes it on a new track
• Song parameters are reset when Time Base is changed to Frames
• Wrong inverted note selection in a duplicated (shared) part
• Wrong automation result after moving arranger section
• "Move" and "Copy" w/ Ripple Edit on the same track deliver different results

[chk071]

• [Windows] “Enable High DPI Mode” option is back

THE INTRANCER... THE INTRANCER... calling THE INTRANCER....

[SLiC]

Works great- I can see Dune 2 again at 125%

[THE INTRANCER]

• [Windows] “Enable High DPI Mode” option is back

System DPI scaling option for third-party plug-ins

Yay... the time and effort I spent posting here and on GS threads and talking with Presonus employees to get them to fix this issue seems to have paid off now regarding the Hi-DPI.

As for Hi-DPI scaling of plugin's, they state as an option with 'Windows 10' in the release notes... from my understanding, this wasn't just an issue with Windows 10, but earlier versions of Windows 8 / 7 as well.. so whether this is addressed for everyone I don't know with still having to download this update...Others will confirm I expect...
___

As for other issue's they have fixed..I've still to look at from that list... for myself right now.. I've trying to fight off a cold virus I've caught, whilst busy working through the nights creating a 3D animated film.. which incidentally does involve using Studio One for the composing of music and effects...

I'll check out the 4.1 update later though with the free version as the trial version I had has long expired...

[tuzemec]

Hope that the work on Pipeline XT will lead to external synths integration in the next release.

[SLiC]

• [Windows] “Enable High DPI Mode” option is back

System DPI scaling option for third-party plug-ins

Yay... the time and effort I spent posting here and on GS threads and talking with Presonus employees to get them to fix this issue seems to have paid off now regarding the Hi-DPI.

As for Hi-DPI scaling of plugin's, they state as an option with 'Windows 10' in the release notes... from my understanding, this wasn't just an issue with Windows 10, but earlier versions of Windows 8 / 7 as well.. so whether this is addressed for everyone I don't know with still having to download this update...Others will confirm I expect...
___

As for other issue's they have fixed..I've still to look at from that list... for myself right now.. I've trying to fight off a cold virus I've caught, whilst busy working through the nights creating a 3D animated film.. which incidentally does involve using Studio One for the composing of music and effects...

I'll check out the 4.1 update later though with the free version as the trial version I had has long expired...

Enable High DPI Mode has been re-enabled to improve system DPI scaling for Windows 7 users.

[Elektronisch]

But still pitch audio without time stretching is not an option

Most basic feature every daw has Studio One does not

[antic604]

• [Windows] “Enable High DPI Mode” option is back

This wasn't really an issue - v4 automatically would run in high-DPI mode but you could disable it by right-clicking the S1 icon / properties / compatibility. Good it's back, bot not really relevant

• [Windows 10] System DPI scaling option for third-party plug-ins

Now this is a real game changer. However, it's not perfect, comparing to the implementation in Bitwig or Live:
- the plugins appear more blurry in S1, probably because of some added filtering? I'm using a 200% scaling, so I'd prefer them to be pixelated but sharp, instead of blurry
- not everything works, for example NI plugins (Massive, FM8, Reaktor) do not: their GUIs are indeed larger, but their logic doesn't scale so knobs, buttons & sliders are drawn in one place, whereas the plugin "sees" them somewhere else, eg. a knob that's visible in left bottom corner, actually is interacted with in the middle of the plugin GUI

Still, it's a VERY welcome step in right direction and actually those issues are the same that Live 10 struggled to in early betas last year, so there are some solutions that can be applied to fix this.

[chk071]

But still pitch audio without time stretching is not an option

Most basic feature every daw has Studio One does not

You can add a request for it here: https://answers.presonus.com/questions/ ... e-requests

Although i'm not sure if someone hasn't added that feature request before. I guess someone has.

[daw.one]

But still pitch audio without time stretching is not an option

Most basic feature every daw has Studio One does not

You can add a request for it here: https://answers.presonus.com/questions/ ... e-requests

Although i'm not sure if someone hasn't added that feature request before. I guess someone has.

Yes: Tape / Repitch / Sampler / Turntable mode for Timestretching

[THE INTRANCER]

This wasn't really an issue - v4 automatically would run in high-DPI mode but you could disable it by right-clicking the S1 icon / properties / compatibility. Good it's back, bot not really relevant

That wasn't the case with those running Windows 7, there was no solution even vie the properties of the Studio One.exe. as was clearly explained and demonstrated vie screen capture recording. Only those running Windows 8 / 10 were able to change the Hi-DPI settings within the Studio One 4.0.exe. So that really was a big issue for those unwilling or unable to change OS versions for any particular reason.

---
In addition to Hi-DPI toggle switch for screens...the Hi-DPI scaling of plugins requires a specific revision version of Windows 10 with that being at least 1803.

[Elektronisch]

But still pitch audio without time stretching is not an option

Most basic feature every daw has Studio One does not

You can add a request for it here: https://answers.presonus.com/questions/ ... e-requests

Although i'm not sure if someone hasn't added that feature request before. I guess someone has.

Yes: Tape / Repitch / Sampler / Turntable mode for Timestretching

its been over 2 years since that request and it seems Presonus cant be satisfied with this tiny amount of 191 users vote

[chk071]

As far as i'm concerned, that feature request is a bit unspecific/requests a few things at the same time. You can always add another one, which is more specific to the thing you want (pitch), and maybe gets some more attention that way. I would vote for sure.

[daw.one]

As far as i'm concerned, that feature request is a bit unspecific/requests a few things at the same time.

It are a few examples from different products for the same thing, pitch+time shifting. The Cubase example is a good one because Studio One also uses the Elastique Pro Algorithm, but lacks the Tape variant.

[Elektronisch]

As far as i'm concerned, that feature request is a bit unspecific/requests a few things at the same time. You can always add another one, which is more specific to the thing you want (pitch), and maybe gets some more attention that way. I would vote for sure.

You dont have to be einstein to understand as a developer that any of those features would be great for users that put up theyr time for a vote. But any single one of them were added in more then 2 years. In my eyes thats really bad not only because voting doesnt mean shit but its a basic feature that even samplers have and its being skipped since v1.