June 4, 2012 at 10:36 am #616
I’ve been trying to use ctrlr on Linux for the last days.
First I tried the binary. (BTW I’m an archlinux user, so I built a package via AUR)
This seemed to work fine, with the only problem being that no MIDI devices are recognised. ” title=”Wink” />
As a few other linux users also had this problem: Did you find a solution?
Noticing that the linux builds are rather old, I tried to compile ctrlr from source.
I got the code from SVN as described in this thread[/url:14ram9ep] posted a year ago.
I found the "Build_linux.sh" script but don’t quite get how to use it.
Could you describe the "official" procedure the get the source compiled on/for linux?
I consider myself an experienced linux user with (slightly above) scriptkiddie-like coding skills. ” title=”Wink” />
Greets, RomanJune 4, 2012 at 12:46 pm #4386
Well that old thread is still valid. Try to get the Introjucer binary running and do as the thread says, adjust your paths inside Introjucer, and it should generate a valid Makefile for Ctrlr.June 5, 2012 at 5:53 pm #4387
I’ll try that, thanks!June 6, 2012 at 3:44 pm #4388
Well, compiling worked at last (minor adjustments necessary).
Still with rev1039 the MIDI Device Problem stays the same; no devices are recognised. Do you have any hints for that?June 6, 2012 at 4:04 pm #4389
Well i can’t really say anything cause i have no test platform for linux devices, there is some discussion on the JUCE forums http://www.rawmaterialsoftware.com/view … f=5&t=8143 about alsa, maybe we need to wait for a fix from JJUCE. I’m also considering using RtMIDI library for MIDI device handling but i need to think about that (if it’s a good idea) it supports linux too.June 18, 2012 at 2:30 pm #4390
Sorry for my late reply!
I had a brief look on RtMidi and it seems quite superior to the "standard solution", so if it’s feasible, it has my vote! ” title=”Wink” />
Also let me know if I can help you by testing or anything else. I quite a few Linux machines lying around anyway, on which a plan to use ctrlr.
EDIT: BTW: have you considered using jack for midi on linux?June 18, 2012 at 2:47 pm #4391
RTMIDI has JACK support for MIDI so that would work, i use linux everyday at work and at home but i never used it for audio stuff, i never used JACK only ALSA. Does JACK use it’s own hardware interface for MIDI or is it just a layer that uses ALSA ?June 18, 2012 at 3:43 pm #4392
Also i wasn’t able to get any of my MIDI devices to work on linux, i haven’t tried the ESI m8u XL that might work.June 19, 2012 at 7:11 pm #4393
Quick update I tried linux yesterday with my esi m8u xl connected to the vm I’m running linux mint. I noticed that the project setting for alsa was disabled in introjucer and that’s the reason for not seeing any devices. There is also an option for jack support in introjucer but I haven’t tried that. Try to update the sources from the svn and rebuilf. Ctrlr should see alsa devices, that worked for me.June 25, 2012 at 9:09 pm #4394
Strangely it still doesn’t work for me. With the new version (thx anyway ” title=”Wink” /> ) there is no more "MIDI Device Settings" button and Ctrlr still does not show up in qjackctl (neither as jack-, nor as alsa-midi device).
I won’t give up yet, though. ” title=”Wink” />June 25, 2012 at 9:16 pm #4395
The new ctrlr builds don’t have the MIDI Device settings icon, you select the device in the panel properties (Right click on panel or lick a red-eye icon on the panel toolbar)June 25, 2012 at 9:59 pm #4396
Damn, that was fast!
I does seem to work now.
Thx for your time!
- The forum ‘Linux’ is closed to new topics and replies.