High Latency problem with new Windows 10 machine

Try to update your audio drivers. I use Pianoteq with my old Core 2 Duo and new Windows 10. There is no problems with latency - very playable. I don't even use ASIO, just Win Audio. Try to increase sample rate to maximum through both audio device settings (windows) and Pianoteq settings.

My PT settings, that are fine:
Dev type: Win Audio
Host sample rate: 192000 Hz
Buffer size: 1920
Internal Sample rate: 48000 Hz
Max polyphony: 48

Windows audio sample rate (audiocard settings): 192000 Hz

Latency: is shown as 10ms (but, I guess, it is even smaller)

I also used Pianoteq with acer tablet. But in this case I decrease max polyphony

In my case higher rates
1. give lower latency (with the same buffer size)
2. produce richer sound
And don't tell me about bats and "that is impossible", I've heard it many times. Fact is a fact: 192KHz sounds for me noticeably better. May be it is due to drivers or my audio device, but I have this effect

That's not a fact, that's a subjective experience/opinion of yours. I hear no difference between 48k and 192k personally, so I don't waste CPU power on it. Also it's been mentioned by Pianoteq developers that pianos don't have a lot (if at all) spectral energy above 15k (or even less than that), which IMHO completely removes the need for processing Pianoteq at 192k.

The internal sampling rate of Pianoteq maxes out at 48kHz in any case, as far as I can gather from the UI (someone please correct me if I'm wrong). In that case I'd assume that Pianoteq engineers being the clever folk they are would make sure that the signal generated is properly bandwidth limited to the Nyquist limit of 24kHz. Then there is no point going beyond 48kHz sampling rate for output as far as sound quality goes.

The main benefits of oversampling beyond the hearing range are getting rid of aliasing artefacts (when the signal being sampled contains frequencies above the audible limit, i.e., the signal is not properly bandwidth limited), or as a brute-force workaround for less than optimal digital-to-analog conversion hardware (rarely an issue these days).

For compatibility with other hardware/software that uses higher sampling rates it may be useful to have the option of Pianoteq producing a matching output. But as far as quality of the sound goes it should not make any difference.

https://www.youtube.com/embed/cIQ9IXSUzuM

You may not be interested but others might be. There are valid reasons for Pianoteq to offer such high sampling rates (other than marketing gimmickry). If your setup sounds better at 192kHz then more power to you. There often are good reasons to oversample, and the maths and engineering behind it all is a bit involved (and more subtle than the way most lay or even some professional folk understand the problem). But in practice all you need to do is try out what works best with your equipment, as you @Kridlatec and @EvilDragon have both done.

PS. Sorry @OP @dklein for going off the rails, i.e., the topic of this thread: getting Pianoteq working on a Windows 10 machine.

First of all, ASIO4ALL is a kludge - but likely your only choice if you're using only onboard audio chip. But I would definitely recommend to invest in a proper audio interface that has its own low latency ASIO drivers (and its own MIDI ports, so you don't have to use a MIDI-USB cable, which is also a kludge of sorts...).

You could try to use Windows Audio (WASAPI) for Pianoteq's audio output instead of ASIO, perhaps. See if that helps. I can get reasonably low latencies with it on my now 4 years old laptop (also an i5)... But in any case, for real low latencies, investing in a good audio interface is the way to go.

Also, "near zero latency" is impossible (except in case of direct monitoring, but this doesn't work for virtual instruments). Refer to the Presonus article above. Even if the driver reports 1 ms latency, there's still at least 10 ms of additional latency that goes into DA conversion, USB buffers, etc.

Thanks again, evildragon, for your most recent reply.  I am starting to think that you are correct about my is one a dedicated MIDI processor – if nothing else, this will help a lot when it comes to plugging in some monitor speakers rather than just trying to convert from the mini plug headphone out on the tablet.

Well, as I better shower and get off to work, I will report when I did this morning: I went back to using the windows drivers rather than ASIO.  Curiously enough, they were faster.  And, for reasons I don't understand, using the windows driver rather than windows driver in "exclusive mode" was faster.  Still, even with my buffer turned way down (the lowest possible for each), there is still a perceptible latency, although things are playable unless I try to hit sixteenth notes – then my ear and my fingers get out of sync.  Still, for slow things, it's okay.  Also, another thing that I noticed had to do with the speed of the calculations – at 44 kHz, my relative latency was increased, and with a low buffer, there was a lot of clicks, pops, and trash.  When I changed it to 48 kHz, the latency decreased to its current lower level, and the trash went away, even at the lowest buffer setting.  Perhaps this is because the processing speed is running at approximately 24 kHz, half of forty-eight rather than an odd fraction of forty-four.

At least things are improving, though slowly…