Kemper Amps Forum

Daniel, so you measured 3.3ms with 1.0.5?

Could you send an error report to support regarding that glitch with 1.0.6?

Quoted from "DanielRigler"

Sure, I'll drop a mail to support.
Well based on my measurements I'm pretty confident that both 1.0.5 and 1.0.6 have the same latency: around 3.3 ms if my measuring method was correct. (I have used CEntrance LTU program + my RME 9632 card).

Daniel, I update my previous post and do more accurate measurements:
1.0.4 latency was about 207 samples (4,7 ms);
1.0.5 latency was about 107 samples (2,43 ms) (and THE BEST TILL NOW reached and that really meets the specifications);
1.0.6 latency was about 134 samples (3,04 ms)...

So, based on my tests, from 1.0.5 to 1.0.6 latency is very similar but not exactly the same... And thanks for your additional testing!

Quoted

Omg!! I've just read this thread and all the comments. I haven't updated my unit to 1.06 yet. Tomorrow I' ll check this bug,my current Fw is 1.05 but I didnt notice this problem previously. I'll let you know asap

Just for the record - it isn't present in .6895

Quoted from "DanielRigler"

Maybe my measuring setup is not as precise as yours... How do you measure it? Also what is the state of the STOMP / STACK / EFFECTS buttons. Do you measure on the same patch? Did you do a system initialization? Do you use the analog INs / OUTs?

I measure before the latency of a chain (without the KPA) with a Send/Return loop active (only a single cable), after I simply substitute the cable in the Send/Return loop with the KPA (Analog Input/Output) and re-measure the latency. So, the latency introduced by the KPA is simply the difference between the previous two.
Measuring it using the same chain and then make the "difference" with/without the KPA is very precise because it remains independent from all the other stuff used (cables, audio soundcard and so on). All measurements were done with only STACK module ON and using always the same patch. It's not easy to explain, so I hope it was understandable

Sorry,nothing helpful to add,just wanted to be part of longest thread ever!

In the version 1.0.6 when you link (as I do often) all the volumes together, Phones, Monitor, Main, Master and you turn the knob left and right the volumes have completely unexpected behaviour: every one after some turns has his own value; even some of them go to zero and so on. Then you have maually, one to one, restore the initial settings you want.

It seems as if the new idea behind the BUG was to link the volumes maintaining the relatives differences
(so, for example: if you set "Monitor Volume" to -10 and "Main Volume" to -5 and they are linked together, when you turn left "Master Volume" to -12, "Monitor Volume" automatically must become -17... but it doesn't work...). Does anyone can do some tests to see if it occurs only to me?

Thank you!
Maurizio