FW 4.0 beta experiences thread.

Quote from klontart

And more crashes in 4.0.5. I've just had 4 crashes in a single 2 hour session here at home.

When the crash happens, in all cases I was:

• In Performance mode.
• Using the Kemper Remote.
• Using the Morph feature.
• Playing a beautiful Gretsch.

In all cases the crash looked like this:

• Remote becomes unresponsive, does not respond to buttons, screen goes dark and enters sleep mode.
• Profiler becomes unresponsive, does not respond to buttons.
• Last selected rig continues to play just fine, so the core engine is still running.
• Power down using the chicken head knob works, but takes seconds to respond. This suggest that the Profiler *is* listening, but very slowly.

It must be the guitar.

Hope this helps,
Robert.

Hi @klontart
Please send an email to support@kemper-amps.com describing the situation you faced.

Done. So Kemper is not watching this thread?

Quote from klontart

Will do. So Kemper is not watching this thread?

I think they rarely look here and if they do you need to report any bugs in official way (email, contact form).

Okay, understood. Message sent.

Quote from klontart

Okay, understood. Message sent.

Thanks. Please report back if your case will be resolved.

(SOLVED) see post below! Thanks Burkhard!
I found a new glitch with 4.5. Unfortunately during a performance (but that's my fault).

The glitch happened in performance mode. Toggling in between rigs with the volume pedal all the way back. Rigs would load on full volume until I push the pedal forward and back.

Quote from tommyguitar

I found a new glitch with 4.5. Unfortunately during a performance (but that's my fault).

The glitch happened in performance mode. Toggling in between rigs with the volume pedal all the way back. Rigs would load on full volume until I push the pedal forward and back.

Please contact support team at support@kemper-amps.com with your findings. Keep us updated how the story goes.

Quote from skoczy

Please contact support team at support@kemper-amps.com with your findings. Keep us updated how the story goes.

If the user is controlling Volume Pedal via Wah Pedal using the "WahPedal to Volume" link, this is normal behavior. Has always been this way and why is explained in the Reference Manual chapter Pedal Links.

Quote from Burkhard

If the user is controlling Volume Pedal via Wah Pedal using the "WahPedal to Volume" link, this is normal behavior. Has always been this way and why is explained in the Reference Manual chapter Pedal Links.

You are correct! Thank you.

Quote from klontart

And more crashes in 4.0.5. I've just had 4 crashes in a single 2 hour session here at home.

When the crash happens, in all cases I was:

• In Performance mode.
• Using the Kemper Remote.
• Using the Morph feature.
• Playing a beautiful Gretsch.

In all cases the crash looked like this:

• Remote becomes unresponsive, does not respond to buttons, screen goes dark and enters sleep mode.
• Profiler becomes unresponsive, does not respond to buttons.
• Last selected rig continues to play just fine, so the core engine is still running.
• Power down using the chicken head knob works, but takes seconds to respond. This suggest that the Profiler *is* listening, but very slowly.

It must be the guitar.

Hope this helps,
Robert.

I had that yesterday again. Happend at least 6 times in a 2 hour session. I'm not able to reproduce this behavior since some days it works flawlessly and other days it crashes all the time. I wrote Burkhard about it and I'm curious if they have a clue what this is about.

No, unfortunately, we havn't!

We cannot reproduce this issue and we don't think 4.0.5 is in that respect any different than for example 4.0.4 or our latest 4.0.6. I'm always using our latest Public Betas during rehearsals and never experienced this issue.

Would be interesting to know, if you experience the same under 3.3.0 with identical data.

We need a scenario to reproduce the issue. So far we don't even know, if this is software, hardware or data related.

Quote from Burkhard

No, unfortunately, we havn't!

We cannot reproduce this issue and we don't think 4.0.5 is in that respect any different than for example 4.0.4 or our latest 4.0.6. I'm always using our latest Public Betas during rehearsals and never experienced this issue.

Would be interesting to know, if you experience the same under 3.3.0 with identical data.

We need a scenario to reproduce the issue. So far we don't even know, if this is software, hardware or data related.

Would it help if I place my action cam in front of my Kemper and record it until it happens again?
Do you really think it could be hardware?

What do you mean by data related? Like my performances or even rigs may be corrupted?
Would you like to take another look into my backup?

Talking about rehearsals ... As long as I don't touch anything and just play and switch a performance or a slot from time to time I never experienced issues like that with the betas.
This happens at home while tweaking a lot and switch rigs a lot and fast and use the looper etc and store things.

I'm a little busy at the moment but maybe I can check what is going on under 3.3 next week.

Thanks, Burkhard!

Is Rig Manager connected at that time?

Quote from Burkhard

Is Rig Manager connected at that time?

Yes and no. Maybe this could be something!

RigManager was running but of course my MacBook went to sleep at some point. The USB was still connected. After the restart due to the crash the Kemper was trying to connect to RigManager but couldn't because the Mac was sleeping. Then I woke up my Mac and the Kemper finished booting and everything went fine until the next crash.

Press and hold RIG while powering on. Keep holding until "Initializing..." appears. No data nor settings will get lost.

Try, if you can reproduce any issue, if Rig Manager is not connected at all.

I will do! Stay tuned.

Quote from 10w73

Yes and no. Maybe this could be something!

RigManager was running but of course my MacBook went to sleep at some point. The USB was still connected. After the restart due to the crash the Kemper was trying to connect to RigManager but couldn't because the Mac was sleeping. Then I woke up my Mac and the Kemper finished booting and everything went fine until the next crash.

Had a freeze on the interface also with 4.0.5 if RM is connected via my notebook and notebook is sleeping. After a wake up of my notebook immediately the interface on the KPA is also alive!

Quote from Burkhard

We cannot reproduce this issue and we don't think 4.0.5 is in that respect any different than for example 4.0.4 or our latest 4.0.6. I'm always using our latest Public Betas during rehearsals and never experienced this issue.

Would be interesting to know, if you experience the same under 3.3.0 with identical data.

I used 4.0.5 maybe 10 minutes and lost all sound. All the lights remained on and I could still change stomps visually, not a sound. Didn't have this issue with previous beta 4.0's... will briefly try 4.0.6 before going back to 3.3.0 - gig tomorrow night, can't afford this type of crash.

(on further testing it appears my brand new Ernie Ball Music Man Majestic may be the problem, not a Kemper issue at all. I'm shocked... Sound totally cuts out after seconds of playing, and I've done a couple of successful gigs with it. Anyone else have Music Man guitar issues like this??

Quote from PETERFR

Had a freeze on the interface also with 4.0.5 if RM is connected via my notebook and notebook is sleeping. After a wake up of my notebook immediately the interface on the KPA is also alive!

Maybe we're on the right track (RigManager connection, laptop hibernation and so on). Right now I'm tweaking a little and unplugged the USB. After over an hour still no problems at all.

(on further testing it appears my brand new Ernie Ball Music Man Majestic may be the problem, not a Kemper issue at all. I'm shocked... Sound totally cuts out after seconds of playing, and I've done a couple of successful gigs with it. Anyone else have Music Man guitar issues like this??[/quote]

quite an expensive guitar to come with an electronics problem... likely a dead battery or switch setting. no expert on these but I know they have a bit more sophisticated electronics.Mono, stereo , piezo, blended. make sure you understand switch settings