Latency on Startup?

TheLongColdDark

TheLongColdDark

Member
Has anyone experienced significant latency on the FM3 after it first powers on? This has never happened to me before today. I was working on a new preset last night that pushes my CPU to maybe 80% or so, which is slightly more than my main preset that I have been using since I got my unit. But when it booted up, I noticed major latency between what I was playing and what I was hearing.

This resolved itself when I switched to another preset, then back to my new one. But still, this has never happened before and I'm just wondering if anyone else has experienced the same.
 
I mean is the pitch shift set to zero? If so, that's a known bug. The workaround is to set the shift offset to anything other than zero, then save the preset.
 
The answer to your original question is "yes". If you need more than that, you should upload the preset.
 
This can happen when the CPU is starved. Booting up has some background processes for a bit which can starve it even further.

This is normal and clears up within 20 seconds or so unless you’re really pushing CPU.
 
chris said:
This can happen when the CPU is starved. Booting up has some background processes for a bit which can starve it even further.

This is normal and clears up within 20 seconds or so unless you’re really pushing CPU.
Click to expand...
Correct and ‘zactly. The units load the cabs in the background. Power it up, get some coffee, tea or tune-up, and it’ll be ready.

Think of it as if you were waiting for the tubes in an amp to come up to temperature or had just started your computer and it was doing some housekeeping, reindexing, etc.
 
Last edited:
If y'all want startup latency, sit down with an original hardware Kemper (not a Stage, but an earlier toaster or rack) and power that on. If you want to stretch it even farther, plug in a Kemper controller. Make sure you have a cup of coffee and a comfy chair as you'll be waiting awhile.

I did notice the other day that the Kemper Stage boots faster than a FM3. But not by much.
 
MKB99 said:
If y'all want startup latency, sit down with an original hardware Kemper (not a Stage, but an earlier toaster or rack) and power that on. If you want to stretch it even farther, plug in a Kemper controller. Make sure you have a cup of coffee and a comfy chair as you'll be waiting awhile.

I did notice the other day that the Kemper Stage boots faster than a FM3. But not by much.
Click to expand...
I don't think he was talking about 'boot up time', he was referring to hands to ears latency.

But yeah, the Kemper rack I used to have....OMG what an incredibly long boot process!
 
Reviving this because it's still an issue on my particular preset. Even after upgrading to firmware version 6, which did reduce the CPU load of this preset quite a bit. But for whatever reason, this particular one always boots up with crazy latency from hands to ears. I switch to another preset, which is spot-on, then switch back to this one, and the issue seems to resolve itself. I have no idea why.
 
TheLongColdDark said:
Reviving this because it's still an issue on my particular preset. Even after upgrading to firmware version 6, which did reduce the CPU load of this preset quite a bit. But for whatever reason, this particular one always boots up with crazy latency from hands to ears. I switch to another preset, which is spot-on, then switch back to this one, and the issue seems to resolve itself. I have no idea why.
Click to expand...
is there a pitch block with a whammy or similar set to 0 semitones?
 
TheLongColdDark said:
Reviving this because it's still an issue on my particular preset. Even after upgrading to firmware version 6, which did reduce the CPU load of this preset quite a bit. But for whatever reason, this particular one always boots up with crazy latency from hands to ears. I switch to another preset, which is spot-on, then switch back to this one, and the issue seems to resolve itself. I have no idea why.
Click to expand...

No, there hasn't been a fix to the "very high latency when pitch shift is initially set to zero" bug, if that's what you're asking. The only workaround AFAIK, is the one I mentioned above. Alternatively, you could initially bypass the pitch block, then unbypass with autoengage when you first use it.
 
TheLongColdDark said:
So my Pitch block settings are attached.

Is this the known bug?
Click to expand...
for some reason, if the unit boots with a pitch block set to 0 for the shift, there is delay in the signal. i think changing to a different preset fixes it until you turn off again.

it's been discussed before, but not sure a solution was reached.
 
You must log in or register to reply here.
Back
Top Bottom