Unfortunately still can't reproduce the phenomenon over here. There are a couple of units on their way to us which supposedly showing the error consistently; we will analyze the problem using those units.
Posts by kpahuitsing
-
-
no this not the same: jjamiecollazo claimed his Stage was bricked...
you report a failing switch: please contact support.
-
warlus1 DamianGreda : the KPA's THRU function works as it should. So if you purely want the KPA to behave as THRU there should be no problems, and you will not nees a merger.
(note that in that case none of the KPA's out functions can be used on the THRU i.e. no progchg out)
like that, yes. but no, it doesn't work with editors...
so you claim that if the KPA is set to THRU (= case1 in my overview = device a+b both are not using THRU) --> the editor of the Strymon is not working?
really ?
can you confirm ?
-
so the situation is as follows:
- set the KPA into 'perform' mode (note that this settings can only be done in perform mode)
- open the system menu page 14/18: there are the 2 important settings
when at least one of both is set to 'THRU' the THRU port will in fact be function as OUT2 ! --> so in your case please verify that both are set to either 'OUT' or '-' (= case1, see below) because you want it to behave as THRU function.
the other thing that maybe a bit confusing is the fact that in your case the MIDI Clock is received by your external equipment. This is because regardless of the THRU port function mode, when 'Send MIDI clock' is enabled there will be a clock on the THRU port, when a MIDI clock is received!
A: port B: port KPA's THRU port function MIDI clock on THRU port 1 MIDI OUT or '-' MIDI OUT or '-' THRU clock coming from MIDI IN only
('Send MIDI Clock' has no effect for the THRU port in this case!)2 MIDI THRU MIDI OUT or '-' OUT2 (A) I) clock synced to MIDI IN's clock (when available)
or
II) clock from KPA's internal tempo generator
('Send MIDI Clock' has to be enabled !)3 MIDI OUT or '-' MIDI THRU OUT2 (B) same as case 2 4 MIDI THRU MIDI THRU OUT2 (A+B) same as case 2 remarks:
a) so only in case '1' the THRU port really is THRU function (!)b) when a MIDI clock is applied to KPA's IN, and 'Send MIDI Clock' is enabled => the MIDI clock is output from KPA's THRU port
OK: it's kind of heavy going but I just verified it: and the KPA with 7.1.3 works correctly like we designed it to do.
-
OK.. AFAIK this works as it should, but I'll verify it and let you know
-
BTW a quick question: is there a way to set the MIDI output on a Stage to THRU (since the Stage doesn't have a physical THRU port)? Not that this is really an important requirement - I guess the Stage is typically more a MIDI sender than a forwarder...
no, this isn't possible.
Interesting observation: in the System menu of the Stage, it is still possible to select THRU for MIDI Device A and B, even though the Stage doesn't have a THRU port - maybe something to be fixed in a future OS update for the stage...
AFAIK: this is because it is possible to restore a backup from the head/rack onto the Stage, and this indicates & retains/keeps the 'impossible' setting in that case.
-
yes: exactly this! (you described it more clearly I think
and you're right: it would be a good addition to the KPA to have a 'merged-out' of some kind: this is a good feature request !
-
-
-
when set to OUT mode, the KPA will not merge incoming MIDI into it's out.
when set to THRU, it will be a THRU port (=an exact forward of all INcoming data)
so what you want to achieve can't be done with the KPA directly, you will need a MIDI merger for that.
-
Is this in reference to the TAP-TEMPO LED being in sync now?
If so, mine definitely still does its own thing.
no: that's a other issue which still needs some attention.
-
that's what the LCD adjust is meant for: so you're all OK
-
try to adjust the LCD contrast
-
it's most probably a software issue.. we're working on this
-
yes it is fixed (and should have been included in the change list)
-
it can be solved in several ways, but as said already: it has low priority right now atm, and we have to use our available software development capacity wise
-
this is not a hardware problem at all, it is 100% software: but it is relatively low on the priority list to solve.
-
hi: we've found the cause, and fixed the issue: it will be in the upcoming firmware
-
Yep.....i have had this issue with the remote even getting it on in the first place.... sometimes have to restart the Kemper 6 or 7 times, unplug and re-plug the remote back in to get it on.
this indicates that something is wrong with your hardware: most probably the cable, but maybe the connector inside the KPA or the Remote
QuoteI have tried so many bloody ethernet cables and still the same crap.
You only would need to try the official supported cable that came with the remote. Most other cables are not adequate: the wire-gauge is not thick enough !
QuoteEvery gig is a crapshoot and a headache with this remote issue. One would think that Kemper, being such an amazing company could have sorted this issue out ages ago..... I guess the small things are not that important to them, but at least it sounds good.
By the way: using a proper PoE injector will enable you to use any off-the-shelf cable (up to 100m).
-
OK... I'll check with support tomorrow and see if we can find-back your ticket