Posts by kpahuitsing
-
-
-
good to hear you have lift-off
have fun studying nrpn !
-
still: maybe on the other board the contrast voltage is provided in another way?
I'd double-check the contrast voltage, and rhe way it is provided.
-
black squares: maybe a contrast issue? is there a potmeter you can twist? or is it done with some PWM?
-
-
unfortunately the ATmega328p itself doesn't have a native USB-peripheral on-board
-
if you choose the right Arduino board (which has a freely programmable USB-device peripheral) implementing USB MIDI isn't hard.. a bit of searching on the webs should yield examples which could/should work directly with the KPA/KPP.
-
when an Arduino is acting as a std. USB MIDI device, it is supported directly on the KPA - no drivers needed.
The nature of an Arduino board/project is writing code for the board, so reflashing an Arduino board is almost a trivial task when working with such boards.
-
please contact support.
-
for you it seems to cause problems... for thousands of others it works fine
Did you consider that it _maybe_ isn't the Kemper, but _maybe_ your specific setup? (Windows version, USB driver version, USB interface hardware, USB hub, virus protection, CPU load, still a bad/too long cable despite being 'new' etc. etc. etc. )
.... just a thought
-
please contact support and provide them with the requested (backup) files.. we can investigate this further.
-
see also Midi Morningstar Mcp6 pro With kemper player latency
maybe the regular MC6 also has (the same?) USB issues?...
several other products reported to work fine (footcontrollers as well as USB interfaces) .. so it's not a general problem on the KPP's side.
-
from the picture on Amazon it looks like the *blue* LEDs on the interface should indicate MIDI measages... do you see any activity on the *blue* LEDs of the USB interface at all?
You can try this also when you connect the interface to a PC/Mac (I think the *blue* LEDs should always work ?)
-
- which MIDI to USB cable?
- did you connect the correct direction?
- does it have a MIDI indicator? (can you see any reaction when you press a button on the pedal?)
- did you set the KPP to receive on MIDI channel 1 ?
-
ah ok... sorry for the misunderstanding on my side.
so: verified is KPP-usbA <-> MC6 "DEVICE" (usbC)
and not working:
KPP-usbA <-> MC6 "HOST" (usbC)
which totally makes sense, because that is connecting 2 hosts.
when you want to use MC6's host function, you should connect it to KPP's device port:
KPP-usbB <-> MC6 "HOST" (usbC)
so you'll need to use a USB-B <-> USB-C cable. These cables sometimes are called 'USB-C printer cable"
(the remaining problem, being the delayed reaction/switching still could be an issue with the MC6 having to deal with the messages it receives from the KPP)
-
*Let me start off by saying I only use the MC6Pro for patch/program changes, so this may not be helpful for those with latency issues.*
*kpahuitsing replied as I was typing. His response was my initial problem. (charging cable vs data)*
I read where you tried several different cables, so this may all be useless?
For me, it was all about the cable. I couldn't get the A to C to do anything with my MC6Pro, even with a couple of different cables I had. I almost gave up until I read about so many people having success with the A to C. I decided to buy a cable from a music store instead of amazon, and it started working immediately. This is the cable I bought from Sweetwater - StarTech.com USB31AC1M USB-C to USB Type A Cable - 3 foot
Now my MC6Pro powers up and works great, but once again I ONLY use it for patch/program changes, not anything fancy (short press, long press, etc.)
huh?
so you say the MC6 pro actually is working with the Player when connected through a USB 'A' <-> USB 'C' cable (plugged into the port labelled 'DEVICE' on the MC6-pro?) "my MC6Pro powers up and works great" would imply that you actually have that connection in use?
that would be nice !
-
on all Profiler models it is totally clear which connector is host (='A' socket) and which is device (='B' socket)
An USB 'A' <-> USB 'C' cable explicitly codes the 'C' side to be the device side (note: it has to be a cable which supports datatransfer, and not only a charging cable) The Morningstar seems to recognize this correctly, as it starts acting as a device, but acts slowly as I understand from your reports?
Maybe the Morningstar has problems processing the MIDI data it is receiving *from* the Player, when acting as a device? For example: initially the 'Paintaudio' controllers had this problem too, and it was fixed by Paintaudio in their firmware.
-
-
tsachou: what do you mean? you cannot spread misinformation without backed claims.
the KPP works just fine with USB MIDI ... this has been demonstrated many times, and everybody can find proof of this on multiple reports on the web.
one thing which isn't/wasn't supported in the current firmware release is the selection of a received MIDI channel.. this has been implemented already now (currently in beta-firmware), and will be available in the next firmware.
if you encounter problems: please explain what isn't working for you, and we'll try to help find the problem in your specific setup.
but do not bleat around unbacked nonsense.