Hm, don't like the sound from FW 1.6 (Edit Fixed now)

  • Not that anyone cares, but I'm going to offer my thoughts on how this thread was handled by Kemper owners and CK. First, as I've stated before, I'm probably one of the least technical Kemper owners on this forum. When this thread started and users started popping up with the sound/feel change when downloading FW 1.60, I waited for CK to post that his team was working on the problem or have found and fixed it. When CK posted that his team had not been able to find any difference, it left me a bit confused. By this time there were more people popping up with the sound/feel issue. I had not personally upgraded to 1.60, so I no experience either way. But at that time, what struck me most was a sense of dissapointment and fear that maybe I had gotten in over my head by buying the Kemper. I had not expected CK to pretty much dismiss the problem to "Imagination". It was my gut feeling that there was indeed a problem with some Kemper owners and I thought that was going to be the end of it. In other words, there is no problem and if you think there is, live with it. What a relief it was when the "Reset" popped up as a solution and it indeed solved the problem with sound/feel with 1.60. What I find puzzeling about this is the reset idea came from a Kemper owner and not CK. I thought this would have been a perfect time for CK to appologize to those he had doubted in previous post. I know CK didn't take this lightly. I know CK and his team worked very hard to find a problem, or prove there was no problem. Maybe it's a language issue and we miss or take things wrong. One thing this proves to me is never assume. It can come back to bite you in the ass.


    At any rate, I'm back to feeling good about being a Kemper owner.


    Agreed, and we do care :thumbup: . 1st rule of customer relations : never tell your customers they are talking bollocks (even when they are). Thank them for thier input and say you are working on it to find a solution. My company manufactures computer controlled jacking systems and we put a log file in the computers that customers can send us when they encouter a problem. This tells us all the setttings and parameters on thier system at the time of the problem. Maybe Kemper should do the same. There could be the option to create a system snapshot which could be sent to support.

  • Anyone care to please tell me where i can find the right procedure for installing 1.6?
    79 pages is a lot of reading in order to find the answer...
    Thanks!


    At the moment the consensus is: Update normally. If your KPA sounds 'wrong' afterwards, do a system reset.

  • Can this thread be moved to somewhere else, like an archive somewhere?
    At the moment it's the "first impression" created for potential new owners or general 'lurkers' when they arrive here for the first time...of course it's a completely WRONG first impression.

  • You might understand our reaction when I tell you a background story:
    During the last year we have received a couple dozend messages about a change in sound, when we released our software updates.
    We checked this every time, and assured that there is no change in sound.


    We go deeper, when we have hints that we can follow. That was the case with the Green Scream beeing modified eventually. Was a good work.


    We have done some Sunday work to follow that trace with the system reset. No results unfortunately.


    I still wonder how people can notice a big difference after updating even the other day, then make a reamped A/B comparison, where this difference should be so obvious, cause it's much more immediate, but no significant difference can be seen or heard. We are following MadH's hint with the slight changes in the waveform view.


    MadH, do you hear that difference in your tracks? Is it the same change that you have noticed, when you updated to the 1.60 the first time?

  • I know but I am talking about the presets.


    I understand, but there are only a few acoustic rigs, so you don't have to wade through all the other rigs and whack them. In other words, an easier solution ...

    Go for it now. The future is promised to no one. - Wayne Dyer


  • I understand, but there are only a few acoustic rigs, so you don't have to wade through all the other rigs and whack them. In other words, an easier solution ...


    He means Stomp and FX presets

    "Music is enough for a lifetime, but a lifetime is not enough for music" Serghei Rachmaninoff


  • I just wonder if it's possible that it depends on the number of user rigs?
    My KPA has currently 1179 profiles and 138 local cab presets.


    i updated to 1.6 and had the same sound as before. Even did a gig at fairly high volume and the kemper was the same. I have 'only' 220 profiles.


    nevertheless I'm in doubt about the sound and I was thinking to perform a reset. I'm a bit lazy though to do it since then I have to set everything to the current setting.


    Kinda of not having the time but for playing......and prefer playing instead..........

    "...why being satisfied with an amp, as great as it can be, while you can have them all?" michael mellner


    "Rock in Ecclesia" - new album on iTunes or Google music

  • Mine had less than 400 rigs and still I got the dreaded "dullness" problem, solved after a system reset.

    Just out of curiosity, weren't you able to reproduce the error by 1) installing 1.54, 2) doing a system reset (maybe a flash wipe/init) and 3) installing 1.60? The difference is very subtle and more noticeable if you select a mid gain patch and play varying picking dynamics and slightly muting the strings with the palm of your right hand. To my ears it sounds like the "compression" parameter in the amp section was dialed to a negative value (if that'd be possible).

  • Don did some more extensive tests.
    He has set his Profiler to the factory state, loaded 1.10, loaded 1.54. loaded 1.60.
    Played the sound. Made a reamped recording. Made a system reset.
    Played the sound. Made a second reamped recording.


    No difference at all. We have no trace.


    If there is a bug, it seems to be killed by the system reset. And it might not reappear. (Please post, if it did, btw.)
    So we cannot ask those, that have performed a system reset already.
    A conclusion is, that units with a certain history of updating and data import will reveal this bug on the 1.60, before a system reset is performed.


    We are looking for users that have not done the update to the 1.60 yet, because it's a public beta.
    We ask for updating to 1.60 and examing the sound.
    As you've seen there is no risk to do that, since you can always go back to 1.54. Many have done these steps, as you can read on this thread.
    If you feel the sound is different, then don't do the system reset but wait!


    If you come to this point, please make a recording of a clean track through the direct out (Spdif is not necessary) and reamp that 'wrong' sound by the clean track.
    Keep both tracks and make a downgrade back to the firmware 1.54. Chose the same rig and make a second recording of the presumably 'correct' sound using the same clean track.
    By using the same clean track as a source you make both recording of that sound comparable, as stated many times in this thread.


    Compare both tracks. There should be a sound difference that might be as easy to notice as the altered sound on version 1.60.
    If you don't hear a difference, play 1.54 for a while. Then upgrade to 1.60 and play this for a while. Please stay on the same rig for the whole test, as it makes your perception more reliable.


    If you still feel a difference, in 1.60, while you haven't heard that same difference when comparing the recordings, then send a post to this thread, or a private message to me, or to our support.
    If you hear a difference when you compare both tracks, even better. Send the tracks to our support. It would help.


    In both cases, please do not perform a system reset, but wait for further instructions from us.
    We will at least ask you to send a backup that we can examin. Also running this backup we might have the chance to reproduce a bad behaviour, that we cannot get on our units.


    If you have questions about the reamping procedure, please ask us.
    If you send me PM's during the next week, I might have to pass it over to our product specialists, since I am leaving for the Namm Show soon. But you don't bother me in that case, it's just one click for me.


    Btw: This will not result in a blind test or so.



    Thanks!
    CK

    Edited 2 times, last by ckemper ().


  • I do hear a difference in the tracks I posted for 1.6.0 before and after the reset but only if I focus the audition on small parts. To be completely honest I still hear a difference between 1.5.x and 1.6.0 reamps after the reset but it is much subtle than before and could be due to the new antialising. If I listen the whole track in one shot and then the other one I would not be able to tell one from the other.


    Like others here I noticed it more while playing than when listening to the reamps. You said that part of it could be due to the feel change due to the latency differences. I agree with that. When the feel changes that makes you adjust your playing unconsciously and as a result everything changes more dramatically than when doing reamps. A part from that there must be something else, as demonstrated on the clips I posted since the wave shapes are different. So one thing and the other combined could be causing what some users are noticing while they play but maybe is most of the cases it is just the latency.


    There is another factor that I have been thinking about related to the loudness while you play. If you don't play very loud you will still hear your guitar and pick combined with the sound coming out of the speakers. This could also contribute with the other 2 factors to the change in perception of the sound and feel globally.


    Can I ask you what do the wave shapes differences tell you? Could it be related to a difference in the dynamic range?


  • Just out of curiosity, weren't you able to reproduce the error by 1) installing 1.54, 2) doing a system reset (maybe a flash wipe/init) and 3) installing 1.60? The difference is very subtle and more noticeable if you select a mid gain patch and play varying picking dynamics and slightly muting the strings with the palm of your right hand. To my ears it sounds like the "compression" parameter in the amp section was dialed to a negative value (if that'd be possible).


    As mentioned, we did exactly that. Not the slightest difference between the 1.60 before and after the system reset. The waveform views were spot on.

  • Christoph,


    I for one really appreciate your concern and focus on such complaints/problems - thanks for working so hard to get to 'the bottom line'...

    All modelers known to man 8o

  • What I noticed after a system reset is that the output settings were quite different, in a positive way.


    I did notice an improvement in the sound. More live and a little brighter.