So the devs aren't solely relying on Win32 API ? I wonder why.....

 

Thanks to all, now I think we have the proof that s1-5 will never run on Win7.

I'm on Win7 and Win10 too so it doesn't really matter to me, it was mostly because of my curiosity.

https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/news

if it only S1 was open source

 

Windows 7 is dead. Move on. We loved 98 more when xp came. We loved xp more when 7 came. We love 7 more when 10 came. But with time, 10 has became a much better choice. It is rock solid now. I am on Core i3 9100 and it performs rock solid.

 

But how most of other programs run on W7 without any problems? Even Cubase 10

 

'Wild guess' because they don't rely on Win10 exclusive files?

No one is saying you can't make updates and stick to Win7.

 

I thoroughly agree with Ad Heesive:

"My W7 configurations will actually never become obsolete. They share space with W10 platforms and whatever W10 morphs into next. Currently W7 platforms still comfortably carry the lion's share of serious music work. There's enough hardware and spares in my workshop to ensure that these music boxes will probably last longer than me. I treat them all like instruments, they worked yesterday, they will work tomorrow. I wouldn't throw an old violin away just because it can't sound like a modern electric guitar.

So, please, politely please, to anyone that makes that mistake,
stop thinking of W7 users as luddites too scared to contemplate W10."

I have no use for 8/8.1 but I do and will continue to run Win7 and WinXP machines as well as Win10.
I have invested in some rather expensive hardware and software that require those platforms. Do I through
the baby out with the bathwater? Hell no and if it aint broke. I like Win1o just fine. But, as of now, Win 7
does most of the heavy lifting in music production and my XP workstation is a monster and handles most of
my mastering chores. I know a LOT of people that are stuck on the endless upgrade hamster wheel and have
to have the latest everything as soon as it hits the streets....but that aint me babe. I like shiny new objects
and I'm no luddite.....but I LOVE my '56 Fender Vibrolux...

 

Presonus writes that S1 V5 is only compatible with Win10.
If you don't use Win10, you can't use V5, it's as simple as that.
There are still old versions that still work on the old Win7.

 

move to windows 10 for a score editor?
no thanks

actually, i prefere cubase, ableton, reaper, logic, anything to this daw, but i was testing it, made some tracks on it and i'm fine without it

my windows 10 is slow even to click on things, zooming in ableton and cubase is slugish and my gbu is good, the response is much worse on everything, creating a midi ins'rt fluid and asio4all sucks on windows 10, my pinguin doesn't work on this, and i'm forced to use 48000hz.
Who wants to use this maaan

 

No one is forcing you to use Win10. You can definitely still work with Win 7 today. But then you have to give up some things. That's no problem, because we were already able to work with the software of that time 10 years ago. You just cannot work with some newer software if the operating system does not support it. (I also have only one i3-8100 CPU, with Win10)

 

Last edited: Aug 21, 2020

WinRT relies on Win32 and .NET API. So you have the convenience of using .NET features in C++ with the speed of C++. WinRT also relies on UWP which can never be backported. While Win32 is plain C mostly, its a pain to use and maintain it. WinRT is entirely standard C++ and is much easier for the devs.

 

Thanks @demberto. I found the hint about UWP helpful to explore.
https://en.wikipedia.org/wiki/Universal_Windows_Platform
Here's an interesting extract..
"Epic Games founder Tim Sweeney criticized UWP for being a walled garden, since by default UWP software may only be published and installed via Windows Store, requiring changes in system settings to enable the installation of external software (similarly to Android). Additionally, certain operating system features are exclusive to UWP and cannot be used in non-UWP software such as most video games. Sweeney characterized these moves as "the most aggressive move Microsoft has ever made" in attempting to transform PCs into a closed platform."

A few thoughts about that... (sorry just my rambling )

I note the 'walled garden' comment in that paragraph,
and I recognise the same 'walled garden' mentality with Presonus Soundsets.
I wonder how long before you the only way you can use Studio One v7 is by renting it from the Microsoft Store?
I can't legitimately criticise Microsoft or Presonus, or any other company, for heading in that direction,
but I can and do still despise it,
and for me, it's always a no brainer to just avoid walled gardens and look elsewhere.

For example, I would like to exploit Presonus Ampire (Guitar FX) outside of Studio One.
It's taken Presonus ages to enable that, now possible using their Hub, but hey the Hub won't install on anything pre W10.
It doesn't matter how attractive Ampire might be, (and I will definitely dabble with it on W10)
But for me, it now won't compete with all the lovely alternative Guitar FX that I can use far more openly on W7 (and/or W10).
Walled gardens at any level are always a major disincentive.
New generations of 'walled users' probably won't care about their ankle bracelets (they just won't know any better)
but to me it's just bollox.

I am really glad that the world has already given us far more Music Production toys and tools
than any of us can find time to fully exploit - lovely toys and tools that are NOT in a walled garden.
In the not too distant future I'm sure I'll find myself...
- still enjoying exploring, and taking the piss out of, the new stuff
- but making music mostly with all the beautiful and infinitely capable antiques.

I pity future users who might not know how to enable themselves to exploit the old stuff.

 

So, v4 didn't use WinRT ? WIN32 is indeed a garbage programming interface but gives the highest performance on Windows platform so....I hope they do a revision of the Win32 API without dumping C for C++.

 

Win32 isn't all C. Infact DirectX, WASAPI, and many other technologies are based on COM, which relies on C++. However, COM is a pain to use and you don't find much info about it anyways. .NET simplified COM, and WinRT does the same thing. Even WinRT at its low level is indeed C, because finally kernel32 etc. are required everywhere.
In Win32, you need to mix, standard C++, legacy C and go by Microsoft's conventions (utter shit) as well as COM. In WinRT, you almost never need to use COM, C and the naming conventions are similar to that of .NET. The only reason WinRT isn't that popular is UWP was a great failure. Windows Phone, failed. Microsoft Store failed. And now we see MS apps like Teams written with JS (Electron).
While everyone can agree that Win32 is garbage today, it wasn't the case until almost recently when Python and JS became the standard.
And WinRT will give you comparable or even better performance than Win32, because it was designed for that.