Home » The PARIS Forums » PARIS: Main » New pc for Paris at 21 (Problem with Memory Manager in w10?)
|
Re: New pc for Paris at 21 [message #109571 is a reply to message #109568] |
Tue, 11 December 2018 18:37 |
mikeaudet
Messages: 477 Registered: February 2009 Location: Canada
|
Senior Member |
|
|
Hi lastlaf51,
I'm sorry that this response has taken so long. I've gone back to school, and it's been hectic.
The short answer is that I'm not sure.
The original post came from Vincent Burel at VB-Audio. He noted that any non-locked memory could cause long delays under Windows 10 as compared to Windows 7. The PARIS ASIO uses locked buffers anyway. This was supposed to be fixed in the spring update, but I could never get a confirmation one way or the other. I'm not seeing any problems on my system, even at 32 sample buffer sizes.
I did notice that there was something off under Windows 10 in terms of thread priorities. I recently found some undocumented Windows functions, and using them to boost the thread priority of the main buffer switch thread is working out perfectly. Windows 10 now works just like Windows 7 as far as the PARIS ASIO is concerned.
Windows 7 goes out of support in just over a year. In my view, it doesn't make sense to do a new Windows 7 build now given that you will just have to upgrade in twelve and a half months anyway if you want to be able to go online. That's just my take on things. Windows 10 is having more than it's share of issues lately, but I'm not having any problems on the Spring update.
I just made some changes to the ASIO control panel about a week ago. I'm going to test them tomorrow. My last exam was last night. If everything works, I just have to remove a bit of debugging code, and it's done. The change was so that +4/-10 expansion card settings will follow the expansion card, not the bank. So, if you have two 8 in cards, with a mix of +4 and -10 gear plugged into them, you'll be able to switch between them and the driver will load the right level settings automatically. It's not a big thing, but I though it was worthwhile. I also changed the C16 mode so that it is saved per ASIO host. So, if you save the C16 as Mackie HUI in Pro Tools 12 and also save it as Reaper OSC in Reaper, the driver will just load the right one by detecting the host.
It's really just little things at this point.
I did have to increase the output latency by 64 samples (as compared to the 4.15 ms I reported before, not compared to the old 32 bit ASIO driver), unfortunately. higher index outputs were being garbled at the lower setting.
That's all the news for now. I haven't been posting, but I've been working on the driver every chance I get.
All the best!
Mike
|
|
|
|
|
Goto Forum:
Current Time: Sat Dec 14 16:47:22 PST 2024
Total time taken to generate the page: 0.01164 seconds
|