Windows 10 Fall Update

Thank you Pete for your FUD-fighting!

Pete, so glad to see you here on these forums, you’ve been a great addition to the gearslutz windows forums so it’s great to see you here as well. The fact Microsoft and Steinberg have a direct line of communication is a great thing, and also we have an insiders view of what is ACTAULLY happening.


MC

:slight_smile: Yeah, hi Pete! Welcome here, great job over at GS!
Looking forward to having you around!

Cheers,
Benji

And thank you for having a C64 as your avatar. :slight_smile:

Pete

Congratulations! The prize goes to you for being the first one to comment on it (and get it right)! :smiley:
Now … can anyone guess what that little C64 is doing? (no hints!)

Hi Pete,

heise and I don’t seem to be the only ones misinterpreting this one:
http://www.tenforums.com/windows-10-news/17993-windows-10-memory-compression-2.html

The behaviour of Cubase 8.0.20 on Win 10 1511 x86 is like this:
Open Cubase, load a big project (~ 1.2 GB). Leave Cubase open for a night as active window (not in background). Next morning, Cubase’s RAM use in Task Manager has dropped to 80 MB, the software stays completely silent. Even a restart of Cubase doesn’t help, only a reboot brings back normal behaviour. This was introduced with 1511; the RTM version of Windows 10 works different.

I use Cubase often on stage, and there’s always situations where you have to leave it open for an hour or two before you can start playback again. So it is essential for me that the software is immediately ready to use if it is needed. ATM it is not, so I would stay away from Win 10 for my live setup for the time being.

Four questions:

  1. Is it possible to limit Compression Store to modern UI apps and exclude legacy apps like Cubase?
  2. Is it possible to turn off Compression Store completely?
  3. When a ‘realtime’ software allocates physical memory to avoid paging (like sampler plugins have to for example), will compression store respect this and leave them un-paged AND un-compressed?
  4. Are there any options (e g via BCDEDIT, GPO or similar) one can change that have effect on Compression Store?

best regards
Timo

Running Pro-16?

r,
j,

Thanx for your concern;
It does add a lot of wear to people’s nerves, and (what’s more important, AND overlooked by majority of people) TIME. I have no doubts there’s gonna be new updates.BTW, SSD is my holly sacrifice, I bought a bunch of those, and if it dies sooner than average expectations would be, I don’t care. What I DON’T like here is - upgrading process messed the size of my System partition, and left some unallocated space. As I may have mentioned, I’m dealing with System partitions (imaging, deploying…etc) on regular basis, and I simply don’t like anyone to play with my partitions. Feel free to disagree playing with your OWN System. So, you may find reinstalling from scratch time consuming, I consider dealing with the system full of X-factor moments much more annoying. Reinstalling e-licenser only might solve one particular problem, but I cannot be bothered with possible similar issues.
I wish you have a good day.

SID programmer? It doesn’t look quite like a mod tracker. I’ve never heard of CIAB Software, and this is nothing I recognize off the bat.

Actually, found it, I think. It’s C-Lab, not CIAB. Looks like this software:
https://www.youtube.com/watch?v=cCigvkjnVTo

I used a Passport MIDI interface with my C128 back in the late 80s. :slight_smile:

Pete

WTH??? There is Cubase 8.1?

The Compression Store is a built-in core part of Windows. I’m not aware of a way to alter its behavior. It’s supposed to be completely transparent to applications. And, like I said, the engineers themselves told me it was in RTM/240, so that’s what I’m going by. There’s always a chance they’re mistaken, of course.

On your third question, the decision criteria is the same as what would have been paged to disk in the past. The difference is it gets compressed first.

You’re running x86 version of Windows? What’s the processor? Any particular reason you’re not running 64 bit Windows? Can you also share some specifics about the PC itself? (processor, memory, etc.) Using 32 bit versions of apps and OS is going to lead to a lot more memory pressure.

Also, have you tried 8.0.30 of Cubase?

Let me check with the Steinberg folks and our engineering and see what may be going on here. Is anyone else experiencing issues after the fall update, but not before?

Edit: Also, is all audio silent (including system sounds) or just Cubase?

Pete

To Basaristudio for your WTF question:
The subject is Windows 10 Fall Update.
It means two - Cubase on Win 8.1 machines. Everyone else seemed to have understood. Maybe you are attempting sarcasm?

Correct, it’s C-Lab SuperTrack, written by Gerhard Lengeling, who went on to bigger things (although that might be just a rumour :wink: ). The animation is much faster than the real thing … what you see there is about 5 minutes condensed, that’s how long it took to load from 5.25" floppy disk.

(Sorry for going seriously off-topic, mods can move this to the lounge if they want!)

I’ve verifed compression store changes. If there’s something going on here in the fall update vs. RTM, it’s likely not related to the compression store.

From engineering:

There are no changes to compression between 10240 and 10525. It’s enabled in 10240 the same way it is in later builds.

Memory compression takes place when pages would have been written to the pagefile, not proactively in some heuristic. Unless the system is very low on physical memory (last resort), memory compression will always occur at low CPU priority (below normal priority that all processes in Windows get by default) so it would not consume CPU that any normal process would otherwise need to consume.

On the decompression side, the pages are decompressed when they are accessed and the app would have likely taken a hard fault from the pagefile (disk read) so the CPU latency of decompression is much faster than disk IO (even on current SSDs).

IOW, the pages would have been written to the pagefile anyway, but are instead (or first) being compressed.

I want to drill a bit deeper into what’s going on here in your test, but it doesn’t seem likely that it’s related to memory compression.

Pete

Pete,
I’ve followed your “column” on Gearslutz during the Win 10 development (I’ve run W10 Insider since available, Win 10 Mobile too) and I would like to thank you very much for all the information, insight, suggestions, help etc you have given to us Windows users. You obviously put in a lot of your time and effort and it reflects your passion for the technology and creativity.

I started this thread just wanting to report my experience with the Fall Update to other Win 10 Cubase users. I also am responsible for the “Timo” vs, Steinberg Timo confusion related to the “memory compression”. I copied Timo’s memory compression paragraph from here to the Gearslutz Win 10 thread to hear your comments - and I should have said to you - from “Steinberg Forum” rather than - from Steinberg. But…
The good news is your here on the Steinberg Forum doing what you do best. Thanks again for your invaluable information. I hope you visit often.

WillB or sometimes WillBthr (not sure why!)

PS. Is it true that the upcoming Surface phone running Windows 10 Mobile is capable of running the new Cubase 10 Universal App (with mouse, keyboard and multiple monitors plugged into it) so I can ditch my HP desktop & Thinkpad workstations?

many thanks Pete - i’am very interested

On my windows 10 i had mostly latency problems- with Windows Store process winstore.mobile.exe

Process with highest pagefault count:                 winstore.mobile.exe

Total number of hard pagefaults                       13155
Hard pagefault count of hardest hit process:          4554
Highest hard pagefault resolution time (µs):          3123003.102273

After deactivate automatical app updates on Windows Store preferences this pagefaults was gone :astonished:

Same deal with mine. I kept getting a message informing me that:

“The Soft e-Licenser stored on this computer seems to be altered in an unrecoverable way.
Please contact your software vendor to solve this issue.”

On a Friday night? I don’t think so.

Fortunately, because of the resources of the great Cubase user community, I was able to find a solution and, yes, it only required running the e-Licenser maintenance program as an Administrator. From that moment on, all was well in Cubase Land, and so the adventure continues. Thanks once again to all of the wonderful Cubasers - my digital heroes - who play a great part in making Cubase the absolute best!