Replies: 2 comments 2 replies
-
Which version of Ctrlr are you using? |
Beta Was this translation helpful? Give feedback.
-
I don't think the crash data would make much sense to most people, but I was going to say 5.3.201 is the best version for linux and windows. Looks like you've discovered that. What is the USB to MIDI device? If it's one of those cheap Chinese ones, then throw it away. Can you connect MIDI DIN directly through an audio interface or something like that? This program can receive MIDI data no problem. Maybe check to see if it works using this? I use Debian 11.0 with Ctrlr 5.3.201 and panels I load seem to work, although I don't use linux for audio things extensively. Finally, can you dual boot into Windows and check MIDI connectivity using the same hardware? |
Beta Was this translation helpful? Give feedback.
-
Hi all,
many thanks for ctrlr, I previously successfully created a panel to edit the patches for a Roland GP-8 Guitar multi effects processor, working like a charm!
Today I wanted to start on a panel to edit a Line6 POD XT Live (a guitar amp modeller). It supports midi over USB, which is supported on Linux. Ctrlr detects the midi device correctly (correctly named POD XT Live), but it doesn't seem to send or detect any midi data. Using midisnoop I see the midi control data when I turn any of the knobs on the device, so the Linux driver is working as expected. But on the midi monitor of Ctrlr I don't see any data when I turn that same knob. Sending a program change also doesn't give the desired effect on the POD XT Live. I checked the channel (and also tried omni mode), but no results. How can I debug this issue? What is the difference between the way midisnoop and Ctrlr read midi data? Any hints what I should look for?
Beta Was this translation helpful? Give feedback.
All reactions