It seems like such a small memory.
Can it ever be upgraded or is it hardwired?
What memory are you referring to? What makes you think it has a "small" memory?
Timo
It seems like such a small memory.
Can it ever be upgraded or is it hardwired?
What memory are you referring to? What makes you think it has a "small" memory?
Timo
Have you checked that you didn't had a different user name ("KPA owner name") during the profiling session? This could be the cause that the self made rigs are not recognized as "yours".
The KPA owner name is also being reset when resetting global settings or restoring the KPA with an older backup file where the owner name was different.
Timo
The defaults for "Monitor Out Boost" changed. They were +12db and are now 0db.
Timo
But unfortunately I lost all settings of the new ducking-parameter in the rigs that I edited under 1.6.0 beta
I can't imagine any way how this should happen. Can you really reproduce this? Updates don't touch the Rigs at all. You can't loose single parameters in the Rigs except you are editing them in an older firmware.
Timo
would someone explain to me what is a different between 1.6.0 public beta and this 1.6.0 release , which is beta again..?
tnx !
When it shows "Public Beta" during bootup, it is a Beta. If it shows "Release", it is the Release.
The "Public Beta" and "Release" tagged versions are the same binary, just tagged differently. When a Public Beta seems to be stable, the Release equivalent will be put to the downloads.
This time, the release build has a different build step (8106 against the 8079) since only a few default values have been changed.
In a previous version of the "Release" archive, the companion document contained the word "Beta" inadvertently.
Timo
Can anyone please confirm this, the culprit seems to be the "Mute Signal" in the Tuner mode
Do you turn the KPA on by setting the chickenhead to Browser? Does it help to move once to "Profiler" mode and back? Can you reproduce the "bad" behaviour again somehow?
Timo
It runs the same FW as the head, no difference (out of prolly a new beta in it)
It runs the 1.6.0 Release as minimum version which includes the support for the rack front panel. It will be the same firmware file for the head and the rack.
Timo
Keep in mind that already present rigs don't get re imported and section presets (like amp, cabs etc.) are sorted to the local presets.
If you still think it is a bug, Zip the shared folder you have imported and send it, together with a backup of your KPA to support.
Timo
Please read the document I mentioned. It explains that NRPN is only a series of CCs. With 1.5.1, there is also a controller that maps 0-127 to the full range of an 14bit (0-16383) parameter. This is also explained in the document.
Timo
Please go to:
downloads
Select the category "Documents" and download the "Profiler MIDI parameter guide".
Timo
Seems to work here. What is the link you want to insert?
But then Eq and Cab would apply to all stacks. What the OP wants to achieve is to have let's say 5 different sets of rigs with 5 different stacks and the changes applies only to the selected stack, not to the other 4.
I thought he meant the other way round.
Either way, you can do this with a bit of locking logic very easily. Additionally, the adaption of _all_ rigs for a gig to the venue shouldn't be done in the stack but in the output section.
Timo
Plus the fact that the OP wants to switch amps. Not possible with a locked stack.
Then, instead of locking STACK, lock EQ and CAB.
Timo
So if you didn't like your tone on that stack you'd still have to go back and edit each rig. Although you could fairly quickly edit the local stack and then go to your ten rigs and copy the edited version, but even that is a hassle to do on he fly during a sound check.
You can do this like that:
- load a Stack preset and modify it for your needs.
- you might store it again to keep it in the presets
- lock the stack section
- now browse through your rigs and when it should have the new preset, just press STORE twice.
done.
This is fixed in 1.6.0
Timo
so, rss, links and notifications are okay now?
do they work again now?
Timo
Should we do the reconfiguration before or after calibrating the integral quantum hall effect generator?
afterwards. use a sonic screwdriver.. (what else)
Timo