W10-14393.0 RAM OS hotkey errors

[arvind]

Hi Peter,

My audio pc is booted into 14393.0 RAM OS, (previous version was 10586.0 RAM OS) since yesterday & I am operating XXHE from my laptop (music server) connected to the audio pc via RDC/Ethernet.

I have noticed repeatedly that if I change track with Alt+N, XXHE goes into stop mode. I tried killing the engine & repeating it but every time I change track it stops playing (red light appears on stop button).

Besides this, in general I find that everything has slowed down considerably. Like play start, bringing up XXHE with Alt+X. These processes take around 20 secs. Previously it may not have been more than 10 secs.

Best regards,

Arvind

[PeterSt]

Hi Arvind,

I think that your observations on the speed are not correct. That is, after you played a first time after a longer period of doing nothing (which includes a plain reboot). However, if you now set all to the large(r) settings like SFS=120 and Q1 = 10x14 while you were used to lower, then this is just normal (annoying but normal).
Anyway I don't recognize this and actually I am a kind of pretty sure that 14393.0 starts up quicker.

The Alt-n I don't recognize either, but this may depend on many other things which even are beyond me;
I don't use it so often but when I use it I see that it fails for proper working maybe 1/3 of times. This is not about stopping but about skipping the next track (so we go from 1 to 3 while it should have ended up at 2).
If you consistently end up with a Stop then something else must be going on. And you know ... I have a hunch already that this may happen with large files (say more than 10 minutes).

It is good that you mention these things but it is not convenient that I don't recognize it. If others experience the same then hopefully they will come forward and from there I may be able to see similarities.

Best regards,
Peter

[arvind]

The Alt+N -> stop doesn't occur with large files only, even a 4 min file playing & a next track of around the same size exhibits this problem. In my case it happens 9/10 times.

Anyway this is not an emergency situation, if others too report it then it can be tackled accordingly. I too don't use it often either.

I guess I just have to accept the general slow response. It's just getting  used to it.

Arvind