- This topic has 25 replies, 5 voices, and was last updated 3 years, 4 months ago by
.
-
Posts
-
The KymaConnect 2.0 BETA is available for immediate download from the Kyma Community Library: KymaConnect 2 BETA. The BETA is open to all KymaConnect 1.0 licensees. (your existing KymaConnect 1.0 license key will license the BETA).
This is a major new version. Improvements include:
- macOS 10.15 “Catalina” support.
- 64-bit operation.
- Four additional external MIDI device slots, bringing the total number to eight.
- Enhanced MIDI routing, including selectable routing between external MIDI devices on a device by device basis.
- Additional MIDI command filtering options.
- A new virtual MIDI port, Haken2Kyma, for dedicated use with the Haken Audio’s Haken Editor.
- Support for IPv6 direct-to-Pacarana connections, and IPv6 local networks. This will reduce initial connection time in some situations.
KymaConnect 2 requires macOS 10.14 (Mojave) or macOS 10.15. It is designed to work with Kyma 7+’s new Ethernet connection method; KymaConnect 2 and Kyma 7+ can share the same Ethernet connection. This is the preferred configuration.
Before you install any version please review How do I verify that the KymaConnect installer is authentic?
This post is used to announce new versions and to communicate changes to BETA procedures. Subscribe to stay informed when a new BETA releases becomes available. If you have a problem like “why is the download not available” please post it here.
Bug reports, technical support questions, comments about KymaConnect 2, and suggestions should be posted to Tips & Techniques topic: KymaConnect 2 BETA Support. Please do not contact Delora Software support with BETA-related issues.
Keep in mind that all Kyma 7 Community forums are readable by the general public. Do not post personal information or upload sensitive screen grabs or files like license keys.
==================================================================
Version History2020-04-22 version 2.0.0 (200.1) BETA 1
Just to verify… It will NOT function in High Sierra? Im asking cause Mojave takes away some functions from my video apps.
Here is the direct link to the Kyma Community Library: KymaConnect 2 BETA. I will correct the original post but right now the forum editor is being a bit difficult. Sorry for the inconvenience.
Doug
KymaConnect 2 was developed specifically for macOS. The implementation deeply leverages macOS’s native facilities and Apple’s development tools. Porting to a different OS, like Widows 10, would require extensive redesign and a ground-up rewrite. We have no current plans to support additional OSes.
BETA 2 is now available from the Kyma Community Library: KymaConnect 2 BETA. This release corrects a bug that was preventing proper operation of MIDI Time Code and some other MIDI System Common messages.
BETA 3 is available from the Kyma Community Library: KymaConnect 2 BETA. This release corrects a bug that was preventing connections if the Mac’s Ethernet port was set with either IP4 or IPv6 disabled.
I like the cleaner interface, the Capybara stuff was always a bit distracting, and the new graphics are an improvement. I also like that it works on Catalina. Working is much better than not working!
If I have any other issues I will let you know.
You are welcome! I appreciate the opportunity to Beta test, and figure you should get some feedback. I do notice that the DSP Status window doesn’t show the Linnstrument I am using, it says Silent Device both for Input and Output. This is on 7.34f0, the latest version (as of June 4). I panicked a bit, but somehow I can still control my Sound with the instrument, despite it not showing up. Very strange.
Is the Linnstrument connected to the Pacarana’s USB Port? If so then you should pass on your observations to Symbolic Sound. If it is connected to your Mac and assigned to one of KymaConnect’s External MIDI, then it should not show up in DSP status. That is reserved for showing the USB or FireWire MIDI device it is currently using.
I was using it directly connected, and just switched back to using it through KymaConnect. I *thought* I remembered it showing up in that drop down before, but perhaps I am mistaken. Since it works, I am not to fussed about the situation.
Each BETA release has an expiration date. For example the most recent release, BETA 3 (build 200.3), is scheduled to expire on August 1, 2020. Should you be concerned that the KymaConnect 2 BETA will stop working then?
Each time we release a new BETA build we extend the expiration date, typically a month or more. Should it ever happen that we do not have a product improvement reason to release a new BETA version before the expiration we will release a new BETA just to extend the expiration date. This will continue until we are ready to conclude the BETA period.
So expect a new BETA version sometime before August 1, 2020. I will announce it here in the forum when it is available from the Community Library.
BETA 4 is available from the Kyma Community Library: KymaConnect 2 BETA. There are a number of UI changes, including better reporting of MIDI devices that are no longer connected, powered off, or otherwise unavailable. Please read the release notes that you can find in the “KymaConnect 2” folder your Mac’s “Applications” folder for more details.
We are now actively testing on the macOS 10.16 (Big Sur) BETA. If anyone is testing their workflows on the macOS 10.16 public beta please give KymaConnect a good work out and report your findings.
A bit more details on the biggest change in this release: handling missing MIDI devices. Previously when a MIDI device assigned to one of the EXT MIDI slots was not available the slot assignment, and the MIDI device pop up, would display <Unavailable>. Sometimes though it would show a multi-digit number.
Now what you should see is the actual name of the MIDI device with “(unavailable)” added. Sometimes though it will show “<Port Unavailable> (a_number)”. Why not the name always?
CoreMIDI does not retain a history of device names. Each device has a unique identifier number which applications are supposed to use to remember device assignments. The number that you sometimes previously saw in the popup is the device’s unique identifier.
KymaConnect 2 now retains a short record of previously known device names paired with device unique identifiers. It uses this record to display the much more friendly name when the device is unavailable.
If you have assigned devices in the past that are not available when you run BETA 4 then you will see “<Port Unavailable> (a_number)” for that device until you connect it. After that you should see the actual name even if you disconnect or turn the device off.
The display name is also used on KymaConnect’s status screen while KymaConnect’s agent is running. Slots with ports that are unavailable show an amber/orange colored status LED. KymaConnect works OK when a device is missing but will show “yellow” for the overall run status.
One thing to be aware of is that some USB MIDI devices change their unique identifier when connected to a different USB hub, or even sometimes a different USB port. This is why AudioMidi Setup seems to collect multiple copies of a USB MIDI device, all but one copy displayed as “greyed out”. KymaConnect 2 depends on the unique identifier so as far as it is concerned these are different devices. Consequently if you have such a device and change how it connects to your Mac KymaConnect may still show the device as noty connected even if it is. Just select the device in the popup menu and KymaConnect will use the “new” device, and will forget the old copy.
- You must be logged in to reply to this topic.