OK: this is intended to work indeed. We will investigate this.
Posts by kpahuitsing
-
-
how did you test this? what software version did you use on your PROFILER, and what model is your PROFILER?
-
it might not be needed to convert to DIN MIDI, as the PLAYER acts as a USB MIDI host directly (so a compatible footcontroller can be connected directly to the PLAYER with a USB cable)
-
just select your preferred audio i/o device in the DAW
-
first step: just try to open any MIDI-capable application on your Windows PC, and see if the PROFILER can be selected as MIDI input or MIDI output.
-
Not feature that I plan to use at the moment.
that's fine, but : does it work?
-
does USB MIDI work?
-
Terrapin : did you actually try the latest beta, and still having connection problems? (and besides that: did you check the usual hardware-related suspects like decent cabling, decent hub etc. ? )
-
maybe your particular Windows install doesn't cope well with the addition of USB MIDI to the device? (virus scanner?)
you could try to manually remove the device in the device manager of Windows, and replug it.
-
OK, glad to hear
(note: if you wish, it should be able to upgrade again now)
-
please try with a different (older) version of kaos.bin first.
-
please try to update the unit with OS 7.3.2 first, as a interim platform. This version can be found in the download section under 'older software versions'.
From OS7.3.2, it should be possible to jump directly to any newer version (OS8, OS9, or OS10)
-
please be sure to have the 'kaos.bin' file in the root-folder of your USB drive
-
from the picture it looks like it's OK on the PROFILER's side ( the option 'auto' would not be available when the unit didn't have SPDIF slave capability; and the screen indicates the correct samplerate when changed externally)
so : it looks like there is no actual audio signal carried over the cable coming out of your audio I/F : maybe you could plug that I/F's output cable into another SPDIF slave to cross-check?
-
what is the AWG spec of the cable you're using?
please consult the main PROFILER manual which has a paragraph about cabling (in particular: see note about AWG rating)
-
I did some digging and I think it may be related to the lack of dedicated driver. Looks from what I can find that the windows Spotify app doesn’t support ASIO and as such can’t use the profiler as a sound card. Chrome or firefox or whatever can so this would be why the web works. I hope there are plans to provide a proper driver for windows folks
huh?
windows Spotify does not support ASIO, and therefore the PROFILER doesn't work at the moment ?? that isn't correct.
-
with the RM and Profiler connection being sensitive to what USB cable and adapters are used, and given that many new computers (Mac's) no longer have USB-A outputs but rely on USB-C, so an adapter is necessary, it would be great if Kemper could list the USB cables and hubs/adapters that it recommends. Much like was done with POE injectors.
It is hard to objectively determine what a "decent/high quality USB cable and adapter" would be from most advertisements.
unfortunately there is no real way of telling that from advertisements.
but on the bright side: it seems that the very vast majority of the cables/adaptors out there seem to be OK... there is really only a very small number of users reporting problems (and we even don't know for sure this is due to the cabling)
so our advice is: if you have connection problems with a Stage model and >OS9, but not with <OS9.. please try another USB connection cable if possible
it's a good idea for Kemper to make a list of verified and tested cables however, so we will take this into consideration.
-
you said you increased your I/O buffer size already: what value is is set to when this happens?
-
please try to use decent/high quality USB cables / adaptors.
The updated USB communication is running at a higher speed than before, that is why the quality of the physical USB connection (cable/adaptor/hub) itself has become more critical than before.
-
My computer should be more than fast enough for this task. As I stated above the problem went away after a reboot of both the computer and the Profiler.
OK.. glad to hear it seems to be solved for you then.