Still no editor then?
FW 4.0 beta experiences thread.
-
Kim_Olesen -
April 5, 2016 at 9:38 AM -
Thread is marked as Resolved.
-
-
Why would firmware include an editor?
-
Is there any to hook up Pure Cab with say... the Looper button on the Remote? I'm looking for a quick, onstage way in which to engage and disengage the pure cab (useful for eg. @djmass's new acoustic EQ'd profiles, which don't like pure cab). I know I can set that page up as a 'Quick' link and hit the soft button for pure cab, and if there's no other way I'll do this, but this is rather cumbersome onstage.
Anyone have a better solution for this?
This could be done when pure cab was under the rig menu. But now that it's under the output section, there's no way to change the setting once it's on or off without manual intervention.
-
This could be done when pure cab was under the rig menu. But now that it's under the output section, there's no way to change the setting once it's on or off without manual intervention.
Thanks, that's what I thought. -
This could be done when pure cab was under the rig menu. But now that it's under the output section, there's no way to change the setting once it's on or off without manual intervention.
What would you think of putting pure cab under cabinet settings where under 3.* the cab volume was located?
-
What would you think of putting pure cab under cabinet settings where under 3.* the cab volume was located?
I personally love the idea. It is, after all, a setting called "Pure Cab"This would allow us to adjust it per rig as well.
-
Being able to turn purecab on /off via one of the foot pedal slots would be the way to go for some
-
Being able to turn purecab on /off via one of the foot pedal slots would be the way to go for some
...or with MIDI !!!
-
I'm not sure why someone would want to be able to turn it on/off in realtime with a footswitch or with MIDI.
But, an on/off Pure Cabinet parameter that can be stored per rig/slot would be useful, I think.
-
I'm not sure why someone would want to be able to turn it on/off in realtime with a footswitch or with MIDI.
But, an on/off Pure Cabinet parameter that can be stored per rig/slot would be useful, I think.
I opened up a feature request: Per Rig Pure Cab Option
Feel free to join in!
-
I'm not sure why someone would want to be able to turn it on/off in realtime with a footswitch or with MIDI.
But, an on/off Pure Cabinet parameter that can be stored per rig/slot would be useful, I think.
If it would be stored per rig, no use for switching it with Midi/Remote... That´s right.
-
I'm not sure why someone would want to be able to turn it on/off in realtime with a footswitch or with MIDI.
I think the rationale behind this was to exclude\include it for the proper rigs in real time, since it is not a Rig parameter.
(PS, NB to Mr. Lapalisse: I know, I know )
-
paults wrote:
I'm not sure why someone would want to be able to turn it on/off in realtime with a footswitch or with MIDI.I think the rationale behind this was to exclude\include it for the proper rigs in real time, since it is not a Rig parameter.
That's right Gianfranco, my original reason for this was to be able to do exactly this, onstage, for those rigs that sound better without pure cab. If this could in future be saved per rig of course this would be better. Either way, it could be of use based on the profile. -
Definitely +10 for making it a Rig parameter! It wold be the be all, end all solution Eng. Kemper has acknowledged the request already.
-
Had yesterday first gig with FW 4.0.2 without any problems.
So looking forward for a FW 5.0 beta -
Used the private beta 4.0.2 yesterday on a gig and noticed some delay when switching between rigs on my KP remote... anybody else experienced this issue?
-
Yes, I submitted a ticket for this. The rig seems to load faster than the remote visuals do.
-
Two gigs this weekend, with NO problems!
-
Two gigs this weekend, with NO problems!
-
I tried 4.0.2 today and lost my performance in slot 6 (i use only this one performance). The restore of the last backup (made with 3.3.0) did not change anything.
Downgrading to 3.3.0 brought my performance back. Is this a known problem?
Regards
jock -