Will the older legacy panels ever be ported?

[oliver-ruehl]

Hi,

I'm sponsoring this project and want to support the devlopment.
Mostly I'm working with the AKAI Miniak, but I'm not sure if it will ever work in the future.
I've tried the newest version with the old "MINIAKmicron.bpanelz" and the plugin is crashing in
Bitwig (Linux Debian)

Can you give us some look into the future?

Thanks very much for your hard work
Oliver

[damiensellier]

Hi Oliver, that's great news! Welcome aboard. CTRLR is really a great software.
But just to let you know, Roman Kubiak who is responsible for CTRLR has been away from the project for a long time. We are a bunch of active users on the forum and the github trying to fix bugs here and there and help other people building panels for their favorite MIDI instruments. IMHO there won't be any further developpement of CTRLR from the CTRLR Master but probably some updates on other forks. We are currently working on the compatibility of VST3 panels to be able to run Ctrlr panels on most of the 2023 DAWs. Currently it's working on Windows VST2 and standalone Exe. For mac it runs on intel macOS on Standalone App, VST2, VST3 without the possibilty to export VST3 panels properly, AU is working great too. I think there's a Linux port available as well.

What version of Ctrlr are you using on WIN10? And can you please tell us more about the way it crashes? Does it load up in bitwig? Or is it just crashing on certain operations? Did you try opening the panel in the standalone Exe?

And about your development involvement, are you fluent with C++ and the JUCE framework? CTRLR is all about it.

Welcome along Oliver

Damien

[oliver-ruehl]

Hi thanks for the nice welcome :)

I made a mistake in my post, I run Linux Debian.

The error I'm getting is this one:

/home/elektrik/neue-vst/Ctrlr/Ctrlr.so

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 2 plug-in /home/elektrik/neue-vst/Ctrlr/Ctrlr.so: libbfd-2.34-system.so: cannot open shared object file: No such file or directory
-------------------------------------------------------------------

/home/elektrik/neue-vst/Ctrlr/Ctrlr.vst3

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Not a plug-in file
-------------------------------------------------------------------

I'm using the 5.5.9 version of ctrlr.
I have no C++ knowledge.
Some Linux skills, python, BASIC, I was able to compile some things, but that is about it :)

Kind regards
Oliver

[oliver-ruehl]

I checked the synaptic packages if I was missing a library (libbfd-2.34-system.so is in binutils which I have installed) , so it seems I'm OK.
Maybe I should try compiling it myself.

[damiensellier]

I replied to your other post on the CTRLR discussion. Tobias released a working Linux version: https://github.com/keinstein/ctrlr
Yeah exactly, you should try compiling it on your own and check if it's working. Forget the current Ctrlr master branch, it has known bug on all platform. Is the standalone application running anyway?

[oliver-ruehl]

Is the standalone application running anyway?
No i get
./Ctrlr: error while loading shared libraries: libbfd-2.34-system.so: cannot open shared object file: No such file or directory

[damiensellier]

Oh alright, so it's just the Linux version not working at all.

You should compile your own softwares if you can from https://github.com/keinstein/ctrlr It seems that it's working from now on.

RomanKubiak/ctrlr#400

Finally, I managed to compile a version of Ctrlr that

works with Lua 5.1
doesn't crash on startup
replaces lua usb support using the system prvided libusb (which should avoid many problems)
documents which libraries must be installed inorder to build the program

TODO:

Conditional compilation of libraries: Some libraries like lua can be provided by the linux distrubution but may be not part of the Windows infrastructure.
ensure static linkage of the libraries

[rekado]

FWIW, ctrlr will be available in GNU Guix in a few days (see https://issues.guix.gnu.org/62304). This means it can be installed on any GNU/Linux distribution.