Windows 10-When?

[CME]

Fwiw I'm a Mac guy at heart. But ran the preview of Windows 10 as a second OS on my hackintosh. While I still mostly used OS X, the times I used Windows it seems to work. There were some issues with ilok in a couple of releases. But those seem to have been sorted.

While I'm not recommending it. Definitely do at your own risk. I never had any show stopping problems.

[noiseboyuk]

Come on now, isn't it time we heard SOMETHING from Avid about this? There's talk of PT12.5 being released by end of Q2 2015, which puts us the full year after Windows 10 was released, and no sign whatsoever of it being compatible. And of course, that's when the free Win OS upgrades expire.

It's tempting to fold our arms and say "nothing wrong with Windows 7" - and there isn't. For now. Just as there wasn't with XP for years. But how many of us are still running rigs on XP? How many of us never want to buy new plugs? At some point, quickly or slowly, we all have to move on.

Steinberg resolved their compatibility issues many months ago. Still deafening silence from Avid.

[Jazzbass56]

Avid doesn't care, or at least I think they don't care about windows users

[Bob Olhsson]

Avid has to be able to guarantee that certain Avid hardware and PC workstations running certain operating systems are bulletproof for their corporate customers. I haven't heard of any problems and am not seeing any on my system but I don't use Avid hardware or the officially supported HP workstations and graphics cards.

[skajo87]

I'm trying to work in my win10 partition. i have 8.1 and 10 in separate partition.
The biggest problem of pt 12 in win10 is the insane cpu usage in 64buffersize... can't even imagine what happen in 32samples
PG Bias FX in 44100/24 64samples this is what you get.

without plugins .. even without a project it will get this

it do the same with any interface i have tried.
With 128 ou 256samples its stable and realistic. like 0% or 1% with 30 tracks,without plugins.

Other weird thing is, when i keep more then 1 or 2 hours with the project open.. its became almost impossible to arm, rearm, record or just a simple input path change. you click record, and have to wait like 3 seconds until it start recording. more time with project open, more time y wait to start record. if you close and open PT it will work perfectly again.

I' trying pt12 in win10 since win10 release... 12.2 12.3 12.4 i see no change.

Btw i'm using a I7 , i have tried same plugin with it the reaper trial at same 64samples. and the cpu drain dont even reach 1%

There is something nasty draining the PT engine in windows 10.

[Jazzbass56]

Thanks for the info, I find that Cubase Pro 8.x is much more efficient CPU wise, but I'm getting ok CPU usage with PT HD 12.4 with Win 10, what is your CPU usage with Win 8.1?

[skajo87]

in w8.1 the values are normal/realistic ..at 64samples. 0 to 1% a 20 track full project without plugins. 2 or 3% with all tracks with basic/stock plugins

with angry plugins like Bias Fx it can eat 3 to 4% alone ..

the weird thing with win10 is that at 64samples , without project. just the pro tools open. the cpu usage start to spike from 10 to 50% .
a simple track in monitoring like the 2nd image can touch 100% and dropout.
with a amp simulator plugin its impossible to play..

[Jazzbass56]

Woundering if anyone having success with win 10 could share their optimization settings, if they are different than 8.1
I optimized my system to 8.1 avid specs but sometime PT stops responding , I Wounder what could be causing this
Cheers

[JoelG]

I did the 8.1 optimizations, and made sure all my drivers were updated.

Joel

[WKG]

I am running fine in Windows 10. Upgraded direct from 8.1 Pro and didn't do much on anything really in regards to tweaking.

I did have to roll back the NVIDIA graphic driver as I was seeing spiking when moving plugin windows and getting some weird playback issues. I also found that unticking the Dynamic plugin processing box in preferences, closing preferences then opening and re-ticking Dynamic plugin processing stopped that issue. I haven't seen it since.

I run at 64 buffer with tons of plugins and a fair bit of VI's with no issues.