PLAYER has conquered a lot of professional musicians, and paying for access to the full tone chain should be an option!
Many PLAYER users in my country are waiting for it, including some professional musicians!
Posts by AppleTreeChen
-
-
Can you please explain what happens in detail?
I'm not sure what kind of situation
After tuning with player, I realized something was wrong in the middle of playing, then opened rig manager to check it out, and yes, the tuner data had shifted!
Maybe an action at some point accidentally changed it, so there really needs to be a button that locks it in place -
I'm having this problem on windows as well, not sure what's causing it to be changed. I think it needs a locking feature
-
Been waiting for a paid upgrade for Player, hopefully the service will be available soon!
-
I've done detailed testing on this issue and there is no official follow-up response from kemper at this time
-
-
-
Happened here as well
-
-
-
Display More
I tested with a PROFILER Head with 11 OS public beta and MIDI OX
a. via a normal USB cable connected to the Head's USB B socket,
b. with an OTraki USB to MIDI interface plugged into the Head's MIDI IN socket.
In both cases the PROFILER executes the incoming MIDI comands correctly. No loops no hangs.
I made sure, Pedals to MIDI and UI to MIDI are not activated.
I suggest you take the other device out of the equation, so you know, the PROFILER used standalone with MIDI OX is not he trouble maker.
I guess, there is a risk, that you are building a MIDI loop, where MIDI comands get bounced in circles.
Mr. Burkhard, your help is also needed regarding the problems encountered with the KPA's MIDI communication via the USB-A port
-
Yea, I already saw your post, I guess it's a bug of the beta?? (first bug I experience in a beta so far)
Hope it can be solved fast, thanks!
And hope someone knows about the sysex for effects too
Maybe.
In the OS11 public beta, KEMPER added midi communication to the USB-A port of the Profiler Head/Rack for the first time, and I'm not sure what happened in between, and so far I haven't gotten any official clarification on the matter
-
I'm having a similar problem with MIDI command interaction with the KPA via USB-A, whether it's CC or PC or SYSEX commands, as long as it's Rig or Slot switching via midi commands, it inevitably crashes, and there's no workaround for that at the moment
-
@
oh.. and by the way: does the crash happen too when only DIN MIDI is used?
May 15 Test Progress:
Using two 5-pin midi cables, connect the Midi out and Midi in of the KPA to the MidiCaptain, send PC commands and CC commands respectively, and after a period of time running, there is no system crash, and the KPA works fine.
At this point, all the tests I can do have been done, and the situation is obvious, so is there anything special about the KPA's MIDI communication over the USB-A port, and does the kemper have any official recommendations for hardware MIDI pedals on the receiving end, or MIDI APPs on the mobile side (used via Bluetooth adapter connection)?
-
Supplement:
Using WIDI JACK to connect the KPA's 5-pin MIDI port's MIDI IN and MIDI OUT, and sending midi commands through the IPhone's MIDIPAD2, the system works fine without crashing!
-
@
can you record the midi data sent to the KPA?maybe we can reproduce the problem if we have a recording of that midi data (with exact timings)
Hi Mr. kpahuitsing, I did a few more tests and recorded some data:
In BROWSER mode of KPA:
1. Bluetooth MIDI adapter (M-VAVE) connected to IPHONE, using MIDI PAD2 to send CC49 and CC48 twice each for switching the RIG, the KPA crashes in about 9 minutes.
I have repeated this operation several times and this operation can be reproduced
2. MidiCaptain uses a cable to connect to the USB-A port of the KPA.
Switching back and forth between PC1 and PC2 twice to switch the RIG (I assigned a PC number to the KPA's RIG), the KPA crashed in about 9 minutes.
Switching back and forth twice between PC8 and PC9 to switch RIGs, the KPA crashed in about 10 minutes.
This operation can be reproduced
I'll continue DIN MIDI testing when I receive my purchased MIDI cable!
-
can you record the midi data sent to the KPA?maybe we can reproduce the problem if we have a recording of that midi data (with exact timings)
Okay, I'll try to keep a log of the operations for the next test.
oh.. and by the way: does the crash happen too when only DIN MIDI is used?
I don't have a DIN MIDI cable at the moment, I'll be purchasing one for testing as soon as I can!
-
Have you tried your midicaptain in one of the "standard" or super modes? Perhaps try an older firmware to elminate the problem could be with the midi-captian KPP custom firmware
Thanks for the suggestion, maybe I'll give it a try
The results of my new round of testing on the OS11 public beta are as follows:
1. So far, KPP (midi) works all right (M-VAVE Bluetooth MIDI adapter and MidiCaptain 10 switch version)!
2. KPA in both Browse mode and Perform mode with external MIDI controllers causes crashes (M-VAVE Bluetooth MIDI adapter or MidiCaptain 10 switched version) that have been reproduced from minutes to tens of minutes!
The situation may be clear, but I'll do some further testing as well
-
and this doesn't happen with the KPP ?
No, MidiCaptain is already adapted to KPP!
MidiCaptain tech support has not yet given a solution for the current situation with KPA
-
After several tests, the same thing happened in browsing mode, the KPA buttons, LEDs and display all crashed and recovered after powering off and rebooting
