It was unplugged from the power cable overnight.
Snakepit666 It was your post that made me try it again this morning.- Thanks for that.
Oh no its died on me
-
sheguitarplayer -
March 4, 2012 at 12:49 AM -
Closed -
Thread is marked as Resolved.
-
-
It was unplugged from the power cable overnight.
Snakepit666 It was your post that made me try it again this morning.- Thanks for that.Perhaps Tony McKenzie could give you a hint where the fuses are located in the device. In his videos he disassembled the KPA.
-
I wonder if this could be some sort of overheating issue that trips the PSU..................when it cools down and you switch it back on, it works again.........just a thought!
-
Did you contact support about this phenomenon?
I would love to hear their take on this... -
Yes I did contact support. Haven't heard anything yet but it is Sunday...
Hope to hear from them tomorrow. -
The very same thing happened to me today - it's a matter of the cache getting corrupted when power is taken out abruptly. It's easily fixed via unplugging it from the power supply for a bit.
It does worry me at venues where the power supply is more on the hectic side, but since this is 1.0.4 still, time will tell if it actually is a permanent thing for me to worry about.
-
It does worry me at venues where the power supply is more on the hectic side, but since this is 1.0.4 still, time will tell if it actually is a permanent thing for me to worry about.
Hmmm that is a worry.
-
Typically will 15 minutes unplugged be fine to get it back to live.
All you would need to do is to read my page
-
Yeah - mine ended up disconnected for an hour, as I suck at bass and was tracking it, so...
-
This sounds more like a hardware overheating issue than a cache issue to me though I hope i'm wrong. Its good to hear your back up and running again
-
It was unplugged from the power cable overnight.
Snakepit666 It was your post that made me try it again this morning.- Thanks for that.That could explain why I never have problems: mine is plugged on a switchable power socket and I switch it always off when not in use...
-
This sounds more like a hardware overheating issue than a cache issue to me
I really hope that is not the case, otherwise the KPA would be seriously handicapped for live usage. This would be an error by design and I just cannot imagine Kemper having done this...
-
That could explain why I never have problems: mine is plugged on a switchable power socket and I switch it always off when not in use...
FWIW, mine is always plugged in and always just put in the off position... even when it's not being used for days
-
Edit. Sorry Feck, it was your shiva profiles. Love them btw.
Glad you got sorted.
Has anyone else had issues with these profiles? I really want to check them out from the responses.Did you just factory reset?
-
Had been having a blast playing audioholics shiva profiles thru a 'direct' cab profile into power amp/cab.
Edit. Sorry Feck, it was your shiva profiles. Love them btw.
Err... I think sheguitarplayer was just correcting himself that he was having a blast with Feck's profiles and not audioholics, as he had initially written.
It doesn't mean that Feck's profiles have issues. They work fine and are excellent btw.
-
Yep ur dead right schneidas. Sorry if I scared anyone.
KPA has been running fine again since yesterday afternoon.
Must have been that cache thingy everyone was talking about. (not good with computers) -
Must have been that cache thingy everyone was talking about. (not good with computers)
Hi,Cache thingy being fixed according to the developers I spoke to friday last week.
Cheers,
Mats N
-
Got replies both from my dealer (The Guitar Store, Southampton) and Kemper, both of whom were very keen to help, although thankfully it wasn't needed in the end.
Kemper confirmed what Mats said in that they are working on the cache problem (whatever that is lol) -
Cache is just a way to decrease loading times by keeping static data stored, thus preventing the need to reload all the data.
For example, you'll notice that a web page loads faster the second time you visit it, and that's the browser's cache at work, storing static elements such as images, backgrounds used by the .css, etc.. If the data in the cache is corrupted, it is customary for the application to acknowledge the damaged information and attempt to fetch it again - it may be this process that's still not fully tuned in with our beloved space lunchboxes.
-
Ahh, DOH!!
I should have read it correctly.Awesome, I will install these bad boys ASAP
Cheers guys
-