Perfect, thank you!
Forgot to add that you can also find all rig packs in Rig manager in 'Rig packs' folder.
You have an N4 ? love it!!!
Yes, few years ago I finally bought it use. I am Nuno fan since my teen age. It's the best guitar I have ever had. The neck has perfect shape for my hand. It's really pleasure to play it. Everybody should try this guitar.
I see Nuno, I upvote. Nice!
Thank you for two minutes of pleasure! Right now I am listening to early Marty's masterpieces Introduction and Scenes.
What a great albums they are.
All the feeling is in there, in your playing. Very nice!
I hate you!
As far as wireless, don't think it's possible as the Kemper does not have a bluetooth or wifi connection.
Why should not it be possible?
KPA has USB port, it is running well known RTOS, so it can be easily extended with WIFI and BT with external USB dongle.
KPA has few more hidden features that may be used in the future for new features.
Damian thank you for info and thanks to Kemper team for fix. It looks like it's fixed.
It's not normal. Looks like backlight LEDs contact problem. I would contact support.
On the other hand: You have first Kemper with touchscreen! Quite unique feature (bug).
Why will they give us OS betas, but not a RM beta???
Because nobody wants to see The end of world coming.
Because (RMbeta)OS7beta is not a good number.
New RM/Editor is probably heavily based on new software features that were introduced in OS7. Those features that we don't see and that are part of software structure. And it seems that some bugs have to be solved first.
Don't worry they will sort it out as they did it every time.
I am sorry, but this conversation leads to nowhere. You are trying to explain to me things, that I was not asking about.
From the Kemper main manual... Page 45...
Well, I didn't find anything in the manual that tells me that:
- You should store your snapshots as rigs in your pool while on OS6 and then upgrade.
- Snapshots should be treated as temporary until such time as you save them as rigs.
Am I missing something?
You should store your snapshots as rigs in your pool while on OS6 and then upgrade. Snapshots should be treated as temporary until such time as you save them as rigs.
Could you please provide any source of this recommendation? I am not aware of anything like that.
And even if it was true, it would be nonsense. Who would ever develop upgrade process like this? It's developers' task to think about such cases and make sure thing will work out.
I am still waiting for OS v7 which will handle my snapshots properly.
I have more snapshots. Whenever i like my tweaking, I just take snapshot. And I have many of them. Will I need them in the future? I don't know. Why on earth should I save them as rigs if I am not sure I like them?
Didn't CK say that 'guitarists should not lost any amp settings' - that's why Snapshots were introduced?
"fixed: lost snapshots during upgrade"
Doesn't work for me.
I tried latest 7.1.1. Tried = kaos 7.1.1 booted from USB directly. (I don't upgrade anymore to test new fw, instead I use direct load from USB)
My snapshots are still lost. If I use fw 6, they are back.
From what I experienced with OS7 versions and from what I read on forum, there was never any 'release' ready version. Release 7 shipped with Stage was problematic, it was really a 'beta' but renamed to 'release' so the Stage could be shipped to customers.
How is it that there are bugs in new versions not related to any added new functionality? I tried few OS7 for my Head, but there were bugs, so I went back to OS6. Two of bugs I experienced: all snapshots were not showing (after downgrade, they reappeared), gui frozen, waiting indefinitely when I tried to browse effects. Don't tell me to contact support. I am not beta tester and I don't want to become one. I just tried it, it didn't work I don't complain, it was 'beta'.
But I see, we have 'release' version with bugs such as, not responding to MIDI messages. Do the developers use any automated testing of new OS before they release it to public? I cannot imagine such bugs would come through automated testing.
Or maybe the sw has gotten to a state in which bugs like to pop out when unrelated functionality is changed?
Seeing this phenomenon, I didn't even bother to try 'release' version as it seems it's not ready yet.
In the past, I remember there was such period when we experienced similar problems with many bugs in new versions. Then the sw was rewritten and all went back to normal.
Hope it will get sorted out soon.