Yes it is a bit different to have the same setting in 2 places at once. I set my Global PC that's in the Output section to zero so it won't over-ride my individual rig setting and then set the Pure Cab I want for each rig manually.
4.2 Beta OS bug? - Pure Cabinet in CABINET different that Pure Cabinet in MASTER
- skoczy
- Thread is marked as Resolved.
-
-
Yes it is a bit different to have the same setting in 2 places at once. I set my Global PC that's in the Output section to zero so it won't over-ride my individual rig setting and then set the Pure Cab I want for each rig manually.
Well thats a good idea. For me it makes not so much sense to mix global setting and Rig setting.
All who want to use pure cab as global (like untill now) can continue.
Those who want to set it per rig (is was a feature request) can do it now .I like this new feature
-
Maybe its me but things seems to be getting more complex than before?
-
Maybe its me but things seems to be getting more complex than before?
Well with every additional function it becomes more complex.
Maybe there could be other solution, but we have now a solution which works good.
-
Yes it is a bit different to have the same setting in 2 places at once. I set my Global PC that's in the Output section to zero so it won't over-ride my individual rig setting and then set the Pure Cab I want for each rig manually.
And, as a variation on Booyah's setting of choice:
If someone wants to completely turn off Global PureCab, using a setting of "0" for Global PureCab USA is not the same as turning it Off. "0" sets the Global effect to its minimum value. There is a checkbox that can be un-checked, if you want it to be completely turned off.
However, if you do have Global turned off, using a "0" Rig PureCab does turn it off in the rig.
-
Is it intentional that the global pure cab value is shown in the cab even when global pure cab is unticked? I find this a little confusing.
This is so you know what value you'd need in your rig to override the global setting.
-
This is so you know what value you'd need in your rig to override the global setting.
I know, but there's no value to overwrite if global pure cab is switched off.
-
To me this is still very confusing UI wise, it's too ambiguous. Hopefully it will change to something a little more consistent later on.
To reiterate - IMO Either it needs an additional on/off switch in the Cabinet. Or the global option just needs to go completely and the individual parameter needs to be able to be locked..
-
Some of us use it Globally
-
Yes, the Global option must always remain IMHO; it saves much fiddling when browsing multiple Rigs.
-
Some of us use it Globally
Yes, the Global option must always remain IMHO; it saves much fiddling when browsing multiple Rigs.
My suggestions just before don't preclude the ability to use it globally.
The Kemper already has a workflow for global settings of per patch values - locking.
Alternatively if Kemper wants to keep things as they are in the Beta and break that existing consistent workflow then the alternative should at least be explicit i.e. an on/off switch for the override effect in the Cabinet section.
-
So is this the requested per-rig Pure Cabinet parameter? If so, you can't set lower value than global parameter.
Unfortunately Skocz, you are right.
Yes, this is it. If you want to go low dial in the global and rig pure cab values both low-ish.
What about situation, when Global PC is set to 8 and I need to set local PC for specific rig to 3? Looks like it is impossible to do now.
I would suggest soft-button tick for local PC which overrides the global value - independent of value. This way we will be able to set ANY value as global, with possibility to set ANY value for local. -
I just thought the new smart installer is that much smart to update the Manuals accessible by Rig Manager Help option. I think that would be another neat feature for Kemper <->Rig Manager ecosystem, to update the manuals in RM with newer OS.
RM knows which version of fw the KPA is running and should provide manuals for this version. This should not be of any problem to implement.
-
This way we will be able to set ANY value as global, with possibility to set ANY value for local.
I agree. Maybe it will come in one of the next version, if the user are unlucky with the momentary solution. (Principle I am glad we have one)
Generally I would say that the setting of pure CAB should not be rolling a dice. Everybody could have a strategy how he use the option Pure Cab.Maybe in praxis it will not cause to much confusion.
-
Unfortunately Skocz, you are right.
What about situation, when Global PC is set to 8 and I need to set local PC for specific rig to 3? Looks like it is impossible to do now.I would suggest soft-button tick for local PC which overrides the global value - independent of value. This way we will be able to set ANY value as global, with possibility to set ANY value for local.
Like I said, dial in the global value more low- ish, and if you need higher do it per rig. You have every freedom here.
-
Like I said, dial in the global value more low- ish, and if you need higher do it per rig. You have every freedom here.
So if Global value set to 8 works for 300 rigs from 301 and the remaining one rig sounds better with PC value of 3, you suggest I have to set global PC to 3 and edit 300 rigs and set local PC to 8?
I would not call it freedom.I know I push it far with the example, but you get the point I hope.
-
So if Global value set to 8 works for 300 rigs from 301 and the remaining one rig sounds better with PC value of 3, you suggest I have to set global PC to 3 and edit 300 rigs and set local PC to 8?
I would not call it freedom. I know I push it far with the example, but you get the point I hope.
What would you suggest instead?
-
I would suggest soft-button tick for local PC which overrides the global value - independent of value. This way we will be able to set ANY value as global, with possibility to set ANY value for local.
Already wrote it in post #32.
-
Already wrote it in post #32.
Ah, ok, why not make it a feature request then?
-
It's more of a bug report than a feature request, I think.
