Forum Replies Created
-
Posts
-
Knut, there is one more thing that I would like you to verify in your network configuration. Open up System Preferences: Network, select the network port you use to connect to the Pacarana, and then click on the “Advanced…” button. Select the TCP/IP table and check how “Configure IPv6” is set. If it does not say “Automatically” or “Link-local only” let me know, and retry #3 after you have set it to either of those two values.
Based on your test it looks like PacaDHCP is still necessary. You should try to use the configuration from step #2 and see if it works as expected. The connection seems to be working fine based on your screenshot. I believe that the bottom status LED showing yellow is incorrect, probably a bug. I will try to reproduce it. Try disabling Ext1 and see if that causes the bottom status LED to show green.
Thanks for the offer Knut!
The difficulty with using a multi-Pacarana Wormhole, and a Pacarana-to-Mac direct connection, is due to a network routing limitation. This was not specific to KymaConnect. I would expect KymaConnect 2 to work in the same set up that KymaConnect 1 worked. So, at least in theory, you should be able to upgrade from KymaConnect 1 to the most recent KymaConnect 2 BETA (Beta 3). Leave the cabling the same, and keep “PacaDHCP” enabled. However, there may be an opportunity to use KymaConnect 2 to without the PacaDHCP work-around. This should also be tested, which could be accomplished by just disabling PacaDHCP.
Here is my suggestion:
1. Uninstall KymaConnect 1. Hopefully you still have the latest installer (1.0.2) in case you need, or want, to revert to using KymaConnect 1. If you do not then contact me at our support email.
2. Download and install the latest KymaConnect 2 Beta. Leave the rest of your set up the same, including keep PacaDHCP running. Try to use this set up and report back here.
3. If step #2 is successful then try disabling PacaDHCP. Also change the Mac’s Ethernet port IP4 setting from the manual value to DHCP. Reboot the Mac mini and power cycle the Pacarana. Run KymaConnect 2 and see if it is able to connect. If it does then that means that PacaDHCP is no longer necessary with KymaConnect 2.
I want to summarize the results of the previous posts between Scott and myself regarding the issue that was preventing a successful connection. This was due to a bug that I was able to reproduce. The bug was triggered when the Mac’s Ethernet port was set up with IPv6 disabled. This is not something that most users would encounter because the only way to do that on macOS 10.14+ is by executing commands from Terminal. So this was a good find and Scott’s help bringing this to my attention is greatly appreciated.
I have uploaded a new version of the KymaConnect 2 BETA, BETA 3 (build 200.3) to Kyma 7 Community Library. This release addresses the above bug and other related issues.
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 took it as intended. Nested quoting is not a feature of this forum, at least that I have been able to discover. So I am not sure what else you could have done. I tried using italics once and I got an HTML mess. Thanks though for letting me know.
I need to digest your latest info, but in the mean time:
Set the Mac’s Ethernet port, IPv6 to “Link-local only”. Be sure and click “Apply” after you exit to the main Network preference pane, before you close the Network preference pane.
Power off the Pacarana (if powered) and connect the Pacarana’s Expansion B port to the Mac’s Ethernet adaptor. Now, perform the follow steps:
- Stop KymaConnect if it is running.
- Turn the Mac’s Wi-Fi off.
- Power up the Pacarana; wait a minute.
- Run KymaConnect; wait a minute. Did it connect?
- Leave the Pacarana powered up, and KymaConnect running. Take a screen shot of KymaConnect’s status screen.
- Stop KymaConnect.
- Take a screen shot of KymaConnect while it is showing the “General” tab
- Take a screen shot of KymaConnect while it is showing the “Pacarana” tab
- Take a screen shot of the main Network preference pane while the Ethernet port is selected, and the Paca is still connected and powered.
- Email the screen shots to our main support email address.
One other question, you stated this about your Ethernet port settings:
DHCP, Self assigned, IPv6 Off.
How did you turn IPv6 off?
Correct, directly connecting USB controller to *either Pacarana USB port does not show the device or register receipt of MIDI data.
OK, that is something you need to pursue with Symbolic Sound. KymaConnect has no influence over the Pacarana’s USB MIDI system.
Running a dedicated wifi network direct from Pacarana to connect iPad/Kyma Control *does work as it should, so Ethernet port on Pacarana works.
What version of macOS are you running?
Some thing to check/try:
- Does Kyma 7+ work as expected when you direct connect the Mac and Paca via Ethernet?
- Is the Mac’s Ethernet port set to DHCP, or are you using a fixed IP address? Also, from macOS’s Network preference pane select “Advanced”, then the TCP/IP tab, and report how IPv6 is set up.
- What IP address does the Mac show when the Ethernet cable is plugged into the Paca, and the Paca is powered. What IP address does the Paca report?
- Try connecting with the Mac’s Wi-Fi turned off. If it shows the same yellow/offline pattern as before let it keep trying for at least a minute.
- Can the Mac connect to the same Wi-Fi network that you set up for the Paca and iPad? If so connect the Mac to the Wi-Fi without any Ethernet connection to the Paca. Run Kyma 7+ and verify that it works with that configuration.
- If #5 succeeds try running KymaConnect while Kyma 7+ is running.
- If the Wi-Fi access point you are using to create the Paca’s Wi-Fi network has multiple ports (like a switch or hub) try connecting the Mac to it.
Finally, I want to confirm that you are not using a FireWire connection between the Mac and Paca, and that KymaConnect never shows red for its status LED at the bottom.
KymaConnect recognizes my QuNexus, but I only get the yellow connection quality. My Pacarana keeps switching between yellow connection and (offline). I’m using the 7+ w/tbolt>Ethernet>Exp Port B connection.
Your Mac and Paca are not properly communicating. The yellow LED indicates that a connection is made but KymaConnect is not receiving the expected response from the Pacarana. You mention the QuNexus, but that should not be a part of this problem. Did you bring that up because you get a successful connection when the QuNexus is not connected to your Mac?
Is your Mac connected to your studio network using Wi-Fi? And just to confirm, the connection between the Mac and Expansion B is a direct connection, and there are no other Ethernet connections to other Pacarana Ethernet ports?
What is your macOS’s firewall set to? Any other network security utilities running?
Related? I am also having a problem with direct USB connection of MIDI devices not being recognized by the Pacarana. Perhaps that part isn’t working as intended?
Are you saying that that when you plug in a USB controller to one of your Paca’s USB ports that Kyma’s DSP status does not show that USB device as a possible MIDI device? Please explain
Thanks for the reports. I was able to replicate the problem and locate the bug. A new version is now available from the Kyma Community Library: KymaConnect 2 BETA that hopefully corrects your problem.
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.
Yes, MTC is supposed to work. I’ll see if I can replicate the problem with Logic Pro and report back. Did you by any chance check Kyma’s DSP’s log window to see what the Paca is receiving while ProTool’s transport is active?
Stephen said: On the Mac I used Audio Midi Setup to have the keyboard transmit on 16 midi channels, set Kyma’s default channel back to 1, but that seemed to break both the iPad and the keyboard, so for now I’m just leaving the default channel on 2 (setting the iPad to channel 2 as well).
I think you may misunderstand what the Audio Midi Setup’s Device Property screen is actually doing. All of those settings are just informational properties that software, like a DAW may or may not use to decide how to treat the MIDI device. The settings you provide do not actual change how the device behaves. So when you selected all 16 transmit channels all you did was tell “interested applications” that the Alesis can transmit on all 16 channels. The Alesis though is still only transmitting on channel 2. In my experience very few applications use the property information.
If the Alesis does not have a way to change its MIDI transmit channel to something other than 2, and you would like to use MIDI channel 1, then you should try to use KymaConnect’s channel mapping facilities. You access that feature from the KymaConnect preference pane’s Routing Tab. Each Source-Destination pair can have its own channel map. You could set up the Alesis-to-Pacarana route to have channel 2 mapped to channel 1. That way whatever the Alesis sends on MIDI channel 2 is automatically change to channel 1. Have a look at that section in the KymaConnect user guide, pages 22 – 24.
What type of MIDI messages do you see when you have Kyma’s MIDI Logging window open? Are you seeing note on/off messages on MIDI channel 1? What channel does the V49 send on?
[if you need some help interpreting the MIDI log post a screen shot of its content]
Kyma Sounds by default expect MIDI note events on channel 1, unless the Sound is currently operating in MPE or Continuum mode.
