[m.tarenskeen]

Ah I see … I was mixing up two different projects! I had just built Dexed from GIT sources before I answered your question about Ctrlr. Forget everything I wrote.

In fact I have the same question. I have not succeeded building the latest Ctrlr version (6.x) on Linux yet. And the pre-built development version doesn’t work. The version I am using is Ctrlr 5.4.16, downloaded from the Ctrkr website pre-built for Linux.

[m.tarenskeen]

Why not publish/export as a Ctrlr panel (*.bpanelz), why only an .exe version? Then it should work on Windows, OSX, and Linux. Wine not needed.

[m.tarenskeen]

After cloning or downloading the sources from GitHub, carefully read and follow the instructions in README.md
For Fedora this worked for me last time I tried

git clone https://github.com/RomanKubiak/ctrlr.git
cd dexed
git submodule update –init –recursive
./scripts/get-juce.sh
./scripts/projuce-lin.sh
./scripts/build-lin.sh

[m.tarenskeen]

If you are interested in the graph side of things, my JD-990 and PLG-150-AN contain a lot of ‘graphics’ objects!

Nice. Impressive graphics. I might borrow a trick or two from you 🙂

• This reply was modified 3 years, 11 months ago by m.tarenskeen.

[m.tarenskeen]

I just released an updated version, with a brand new GUI design (many thanks to: Uriah
theuriah.bandcamp.com), and some small changes and/or bugfixes.

The Panel works not only for the PSS480, but also for the PSS-580 and PSS-680. And there is a special version available for the PSS-780.
You can find the latest version of my Ctrlr panels on ctrlr.martintarenskeen.nl

• This reply was modified 4 years, 6 months ago by m.tarenskeen.

[m.tarenskeen]

Thanks Possemo,

That should help.
I will try your suggestions.

[m.tarenskeen]

Check your LUA code for lines that use console()
In code for my panels I replaced many instances of

console("this is a message")

to

console(String("this is a message"))

It fixed some problems on some versions of Ctrlr for me. I don’t know if it will fix your Patch save problem, but it might fix the error message. As far as I know my suggestion doesn’t hurt even if it doesn’t make sense.

[m.tarenskeen]

I’m using both 5.3.201 and 5.4.16 on Linux Fedora succesfully.

I want panels that I create myself to run on both. Some LUA code that I use on 5.3.201 will not work on 5.4.16. Then I try to find a workaround that works for both. If 5.4.16 is crashing on your system it’s most likely having a problem with the panel you are using.

Ctrlr 6.x is not running for me on Linux (yet)

[m.tarenskeen]

I think exporting (restricted) instances are a Windows thing, not working on Linux?

[m.tarenskeen]

I have seen that there is version 5.3.201 available for Linux (same stable version as for Windows I suppose).
I’d like to install on a Virtual Box VM.
Do you have any experience on that and can you recommend me a Linux version (image to download)?
Thx in advance!

Also Ctrlr-5.4.16 is available for Linux and working.

I use Linux Fedora. Ubuntu is a very popular distro too and slightly more user-friendly some people say. The nice thing about Linux is that it is free, so nothing is stopping you from downloading images from different distros, try them inside Virtual Box, and see which one you like best.

[m.tarenskeen]

How to build Ctrlr version 6.x.y on Linux myself?
The old build instruction don’t seem to work anymore?

Latest available Linux binary (6.0.1) crashes. (Using Fedora 29 here)

error while loading shared libraries: libbfd-2.28-system.so: cannot open shared object file: No such file or directory

[m.tarenskeen]

patchelf –replace-needed libbfd-2.28-system.so libbfd-2.31.1-17.fc29.so Ctrlr

Thanks for the tip, but unfortunately it didn’t work for me (crash)

MT

[m.tarenskeen]

Having problems with the Linux version (see previous message, hope this can/will be fixed) I am now trying the new Windows version.

It seems many of the buttons in my Panels now have a fresh new look. Square and rectangular buttons now have a rounded look. Looks really nice for some panels, not so nice for others. IMO what used to be smaller rectangular buttons look better in the new style. What used to be large square buttons look kind of ugly now. Personal taste, I guess, it also depends on the colors I choose. But is this rounded-button-look configurable or is it forced by JUCE?

[m.tarenskeen]

I am trying Ctrlr-x86_64-6.0.1.sh on Linux Fedora 29.
If I try to start the standalone Ctrlr binary (have not tried the Ctrlr.so Linux VST yet) I am getting this error:

./Ctrlr: error while loading shared libraries: libbfd-2.28-system.so: cannot open shared object file: No such file or directory

Previous Ctrlr versions are still working normally.

$ ls /usr/lib64/ | grep libbfd
libbfd-2.31.1-17.fc29.so
libbfd.a
libbfd.so

• This reply was modified 5 years, 2 months ago by m.tarenskeen.

[m.tarenskeen]

About the console error: This is a really annoying error. Or maybe a really annoying imcompatibility issue (which is not quite the same, but equally annoying)

In the Panels I created I try to keep things compatible with different Ctrlr versions.

The problems are usually somewhere in the Lua code:

console("This is a message")

works fine on older versions but makes the latest version crash.

Instead I now use

console(String("This is a message"))

Which seems to work on all Ctrlr versions I have tried.

Another source of incompatibility are bit operations. In my code I use pure Lua replacements of bit operations that used to require the bit module that is not available in all versions of Ctrlr.

I think developers of Ctrlr panels should try to test and debug their panels on different more or less recent versions of Ctrlr. With a little workaround often it is possible to make Panels compatible with different versions of Ctrlr. Ctrlr is a powerful but buggy tool – I’m afraid we will have to live with that.

MT

[m.tarenskeen]

Possemo wrote:

the .bpanelz file includes all ressources such as images etc. You can make a .bpanelz file by using the export feature of Ctrlr.

Note: When I export as a bpanelz file from Linux and include a custom ttf font, if I load this panel on a Windows machine this font is not used but reset to one of the default system fonts.
The font is included but not used: to activate it I have to open panel-edit mode and select the font for the elements that I had in mind. Only then the panel will have the looks that I had in mind. Example: my Yamaha Reface DX and Korg DS-8 and 707 panels (lcddot.ttf font used for voicename display)

Same story if I develop and export on a Windows machine and then load the panelz file on a Linux machine. Because more people use Windows I usually export on a Windows machine before making my panels public.

Don’t have any experience with OSX behaviour, so can’t tell how a Mac behaves.

[m.tarenskeen]

Thanks, good to know this workaround. Still, it’s an annoying bug that’s probably not difficult to fix.

The real problem is that Ctrlr is a complex softwareproject that for most part is developed and maintained by one single developer. We can’t thank him enough for that! But it would be good if he could get some help from other developers to find and fix bugs, maintain compatibility with everchanging libraries (JUCE, Lua, C++) and/or improve things and add new features.

[m.tarenskeen]

Possemo wrote:

To m.tarenskeen: yea this is true, sleep is not a substitute for timers. There are many cases where you absolutely need a timer. Mainly because Ctrlr is single-threaded and therefore does not always do what you want when using Lua scripts.

I have some questions about that os.execute stuff.
I develop my panels mainly on a Linux system. Once in a while I start an old Windows laptop just to check compatibility issues. I don’t own an Apple computer.
I guess (for example) os.execute(sleep(100)) executes a command that has to be available on the host operating system.
Question one: shouldn’t it be os.execute("sleep(10)") (with quotes)?
Question two: is the command working on Linux, Windows, and, OSX and working with the same syntax? My aim is to create panels that work on all these three OS’s

[m.tarenskeen]

Possemo wrote:

Ah. for once I was faster than dasfaker.. ?

I would prefer os.execute(sleep(value in milliseconds)) instead of a timer. sleep works fine – just be aware that the MIDI Monitor of Ctrlr will display wrong values. It looks like sleep has no effect but in fact when you look at it with MIDIOX you can see that it does work flawlessly.

Thanks, I didn’t know that. I can use that in one of my homemade panels. For me the timer construction is difficult to grasp. Using os.execute(sleep()) is easier to understand. But I can imagine situations where sleep can not be used. For example when used in situations where a track is playing in a DAW simultaneously. Timing will be ruined then, or maybe the system will crash?

[m.tarenskeen]

I have been trying to fix all these bugs on my Reface YC panel. Hopefully my latest version works better, but there is always a chance that new bugs are introduced while trying to fix others.
Could you try Reface YC panelz version 20180607 from http://soundmondo.martintarenskeen.nl and report back if it’s any better now?

[Author]

Posts