So it seems to me from the positive results I’ve had with my quick tests this morning (SO FAR) the hyperthreading issue appears to be FIXED in C12.02, or am I kidding myself?Īnyhow, so far so good, C12.02 is very much usable. This would have been IMPOSSIBLE within C12.01 on my ThinkPad. With hyperthreading still engaged, I pushed C12.02 further by reducing the record latency down to 8 ms and loaded a HALION SE track for a “play along keyboard session” within the C11 project with an additional Groove Agent 5 track on a drum loop loaded (2 cores in GA5), and NO ISSUES! Previously, this project was unplayable in C12.01 with hyperthreading ON. So I then rebooted after switching hyperthreading = ON and played the same C11 project with NO ISSUES. Lowered the ASIO settings to more normal (Yamaha THR30 ASIO 20 ms playback, ASIO guard normal) and NO issues with hyperthreading OFF. Next I loaded a previous C11 project of mine which suffered dropouts and glitches under C12.01, even with hyperthreading OFF. Ram is just 8GB, SSD 260 Gb internal drive.
with the built-in GPU disabled (very old intel HD 3000!). Video driver is an old external NVidia GTX 650 ti. My lowly WIN 10 (21H2) 2012 ThinkPad i7 2640M, 2.8 GHz CPU had hyperthreading switched OFF in BIOS running only 2 cores, so I don’t expect to be able to run Austin MIXED without issues, ever, to be fair. Switched to Austin MIXED demo, and it would ALMOST play the entire song. Keeping all my ASIO latency settings on maximum for playback, I could play back the Austin UNMIXED demo OK.
This is a good news post, so please delete it if it’s not what you want in this thread.ĭownloaded 12.0.20 this morning.
0 kommentar(er)
