Forum Replies Created
KymaConnect shows in its EXT MIDI popup menus CoreMidi MIDI interfaces and devices that are connected to, and recognized by your Mac. If you are not seeing your devices, for example a USB controller, then the first thing to check is whether macOS Audio MIDI Setup is showing the missing device(s). If not then that is the place to start your troubleshooting. If it does show up in Audio MIDI Setup, and is not “grayed out”, then we will have to dig in to see why it is not shown by KymaConnect.
Kyma’s DSP Status, and the Paca(rana)’s panel, show MIDI devices connected to the Paca(rana)’s USB or FireWire interfaces, provided those devices use standard drives that the Paca(rana) supports. Those devices are local to the Paca(rana) and not available to the Mac. Likewise MIDI devices connected to the Mac are not directly available to the Paca(rana). Kyma’s DSP Status window shows only these local, recognized MIDI devices.
KymaConnect uses MIDI devices connected to the Mac. The MIDI from these devices is set to the Paca(rana) over the Mac-to-Paca(rana) network connection using “MIDI-Over-OSC”. MIDI from the Paca(rana) is likewise return to the Mac in the same fashion. OSC messages use the Paca(rana)’s Ethernet network connection. KymaConnect only uses the network connection. It does not use FireWire.
Dante, Symbolic Sound’s Kyma control protocol, and OSC all use a standard IP network. So they can all peacefully coexist within normal network considerations. In my experience Kyma 7+, Dante, and KymaConnect all work well when sharing an Ethernet network.
Kyma 7+ eliminated Kyma’s need to have a FireWire connection between the Mac and the Paca(rana) and replaced it with a network connection. KymaConnect, as mentioned, has always used the network connection. The Paca(rana) only needs a single Ethernet cable connection; Just make sure to use the “Expansion B” port.
KymaConnect 2.0.0 has been release. Please see KymaConnect 2 is now available for details. The version released is the same as the last beta (BETA 9) but of course does not expire like the beta does on August 1. You should be able to install the production release over the last beta. Please post to KymaConnect 2 BETA Support if you run into any issues.
Beta testing continues. I will post new releases as they become available here. The KymaConnect 2 beta download in the Community Library is inactive and will be reactivated when the next beta becomes available.
Yes, sadly the Morph’s MPE mode is not compatible with Kyma without a fiddly work around that currently requires you to have another MPE control that Kyma supports. This is largely because the Morph has only a partial MPE implementation and seems to have the philosophy that the sound source can be manually adjusted to conform to the Morph’s settings for things like polyphony and bend range. Also those important settings can only be changed by running the Sensel app.
No changes to MPE. The only difference between BETA 9 and BETA 8 is in the expiration date.
I’m curious how you were able to get the Sensel Morph working at all with Kyma. My own testing indicates that the Morph does not respond to the expected MPE commands that Kyma assumes in order to find an MPE controller, and enter MPE mode. This is discussed briefly in this Q&A https://kyma.symbolicsound.com/qa/5540/how-do-i-mpe?show=5540#q5540 and this one: https://kyma.symbolicsound.com/qa/4431/sensel-morph-mpe-with-kyma?show=4431#q4431
The only way that I have been able to get the Morph to work in MPE mode with Kyma is to use another MPE controller that Kyma does recognize to force Kyma into MPE mode for the currently loaded Sound and then play the Morph.
Do you recall the process you used before to get the Morph working?
BETA 9 is now available from the Kyma Community Library: KymaConnect 2 BETA. It replaces the previous BETA 8 which expires June 1, 2021.
This is a Release Candidate and reflects KymaConnect 2’s expected initial production release. There are no changes from the BETA 8 release so operation should be identical. If you notice any changes, encounter bugs or problems, or have suggestions and general comments, please let us know in the Community Forum Kyma Connect 2 support thread.
The BETA 9 release has an expiration of August 1, 2021.
BETA 8, now available from the Kyma Community Library: KymaConnect 2 BETA, replaces the previous BETA 7 which expires May 1, 2021. The BETA 8 release has an expiration of June 1, 2021.
There are no other changes in this release so operation should be identical to BETA 7. If you notice any changes, encounter bugs or problems, or have suggestions and general comments, please let us know in the Community Forum Kyma Connect 2 support thread.
BETA 7 is available from the Kyma Community Library: KymaConnect 2 BETA. This replaces BETA 6, stops working on February 1, 2021. BETA 7 expires on May 1, 2021.
This is a minor update with a few small bug fixes. Operation should be nearly identical to BETA 6.
As usual, please report any issues, possible bugs, suggestions, or general comments in the Community Forum Kyma Connect 2 support thread.
BETA 6 is available from the Kyma Community Library: KymaConnect 2 BETA. This replaces BETA 5, which will be cease working on December 1, 2020. BETA 6 expires on February 1, 2021.
This is a significant release because it supports macOS 11 (Big Sur) and the executable is now a “Universal Binary” that will run natively on either Intel or Apple Silicon processors.
Aside from a minor improvement to the GUI on macOS 11, the operation of this release should be identical to the previous BETA 5. The only difference is the use of the latest Apple tool chain, and the inclusion of Apple Silicon support in the Universal Binary. Behavior on macOS 10.14 (Mojave) and macOS 10.15 (Catalina) should be the same as it was for the previous release. If you think you are seeing different behaviors, even small differences, please report them in the Kyma 7 Community Forum thread.
If KymaConnect is not seeing MIDI activity there is more than likely none. Best to verify though with MIDI Monitor.
Does the control have a power switch so you can turn it off and leave it plugged into USB? If so try switching it off before restarting you Mac, and switch it off before letting your Mac go into sleep mode. Give the Mac time to wake up, or start up, before switching it on.
As I mentioned I have experienced this type of USB MIDI issue a relatively recent model from a top brand. I have attributed the problem to the USB hub but it might do it even if I plugged it directly in the Mac. Turning its power switch off, then back on always brings MIDI back to life, and I never have the problem if I remember to switch it off before sleeping or shutting down the Mac.
Sounding more and more like a driver issue.
I do have the Akai and Akai Port 3 in two External inputs. Not sure what Akai Port 3 is, but figured I’d connect it and find out.
That is not what I meant by multiple entries. I was interested whether you see a complete duplicate set of ports for the Akai in the port list. Usually when CoreMIDI does that you also see duplication in AudioMIDI Setup, with the duplicates grayed out.
Not sure if this is new behavior with update or not. I just added an Akai MPK49 MIDI kbd controller, which is bus powered. After launching Kyma, KymaConnect doesn’t recognize MIDI transmission from it, although it does recognize that it is connected. After unplugging/replugging USB, MIDI transmission works just fine.
When you say that KymaConnect does not recognize MIDI transmission do you mean that you do not see MIDI activity in Kyma’s DSP status window, or that KymaConnect’s activity LEDs are not showing MIDI activity?
One thing to try is to have KymaConnect stopped when you first plug it in. See if there are two entries in the MIDI port list for the MPK49.
I have seen this identical behavior in other applications, like Logic, with other class-compliant, USB-powered controllers. The controller is recognized by the software but there is no MIDI reception until it is either turned off and then back on, or unplugged and re-plugged in. I suspect this is related to a problem in macOS/CoreMidi.
Also noticed that it only seems to work when connected to the right-hand side USB port on 2016 MBP, not the left-hand side port.
Try plugging it into the left-hand port with KymaConnect not running and then inspect the available ports KymaConnect shows. See if the MPK49 is showing. Record the full name that KymaConnect is showing, if it shows up. Repeat the same experiment with the right-hand port and look for a difference between the port names.
CoreMIDI considers the same device connected in two different USB paths to be different devices. Historically KymaConnect also treated them as different devices, which meant that changing USB ports would cause a configuration to no longer work. BETA 4 added code to help this situation but there are situations which it cannot handle. I discuss this in more detail in the BETA 4 release comments in this forum message: https://kyma.symbolicsound.com/forums/topic/kymaconnect-2-0-beta/#post-1897
The last paragraph may be what you are experiencing with your left/right USB ports.
BETA 5 is available from the Kyma Community Library: KymaConnect 2 BETA. All KymaConnect 2 BETA users must update immediately; Previous BETA versions, including BETA 4, no are no longer valid. Please discard previous BETA installers.
BETA 5 is available from the Kyma Community Library: KymaConnect 2 BETA. All KymaConnect 2 BETA users must update immediately; Previous BETA versions, including BETA 4, no are no longer valid.
The macOS 10.16 (Big Sur) release is rapidly nearing. We are testing KymaConnect 2 on macOS 10.16 but additional user testing is very helpful.
The interesting thing about the error message of the operating system was that it was like a virus warning where you could tell Apple right away that it was malware.
Now, if a KymaConnect user mistakenly declares the installer to be malicious during installation, does this perhaps have a negative effect on other KymaConnect installations of other users? I hope that this is not so bad.
I do too! I don’t believe that is the case but have no way of proving it without risking making matters worse.