Forum Replies Created
-
AuthorPosts
-
My new panel is now finished. Buzzzy!
There some minor enhancement i need to do in my lua script but it work very well.
Thanks very much dnaldoog πThanks very much. You make my day π
My Buzzzy! panel is almost finished. I’ll publish it soon.Bruno
I’ve made this script which is called when the “engine uiCombo” modulator value change:
EDIT: corrected some error in the script.-- -- Called when a modulator value changes -- @mod http://ctrlr.org/api/class_ctrlr_modulator.html -- @value new numeric value of the modulator -- selectWavesForEngines = function(--[[ CtrlrModulator --]] mod, --[[ number --]] value, --[[ number --]] source) local engine = panel:getModulatorByName("osc_engine"):getValue() local waves_pulse = panel:getModulatorByName("osc_pulse") local waves_fm = panel:getModulatorByName("osc_fm") local waves_wave = panel:getModulatorByName("osc_wave") local waves_noise = panel:getModulatorByName("osc_noise") if engine == 0 then waves_pulse:getComponent():setVisible(true) waves_fm:getComponent():setVisible(false) waves_wave:getComponent():setVisible(false) waves_noise:getComponent():setVisible(false) elseif engine == 1 then waves_pulse:getComponent():setVisible(false) waves_fm:getComponent():setVisible(true) waves_wave:getComponent():setVisible(false) waves_noise:getComponent():setVisible(false) elseif engine == 2 then waves_pulse:getComponent():setVisible(false) waves_fm:getComponent():setVisible(false) waves_wave:getComponent():setVisible(true) waves_noise:getComponent():setVisible(false) elseif engine == 3 then waves_pulse:getComponent():setVisible(false) waves_fm:getComponent():setVisible(false) waves_wave:getComponent():setVisible(false) waves_noise:getComponent():setVisible(true) end end
But i can not find anything about layers. Just “Component Layer ID”.
Do i need to make a script that run when the panel load finish with setVisible(false) on waves_fm, waves_wave and waves_noise uiCombo?Thanks. Your help is greatly appreciated π
- This reply was modified 4 years, 6 months ago by arcangeli.
February 17, 2019 at 10:49 am in reply to: Need some help to add patch load/save for the Triode panel #96766Thanks π
I’ll try to do the lua Table without saving next week.
Saving as binary file seem to be more simpler than converting to csv.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
You need to modify the Ctrlr binary with patchelf:
patchelf –replace-needed libbfd-2.28-system.so libbfd-2.31.1-17.fc29.so Ctrlr
That work for me on Debian testing.October 20, 2016 at 9:10 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70152Open build.sh with a text editor (i’m using vim but i think that there is a simpler one already installed like leafpad)
Remove these 5 lines:
if [ $CPUS -ge 4 ]; then
let JOBS=’CPUS / 2′
else
let JOBS=2
fi
Replace them by:
JOBS=1It control the number of file that are compiled at the same time which need more memory that available on the rpi.
Quit all unused applications (do not use the rpi).
launch ./build.sh -f another time and cross finger π
You may need to install more “dev” package but i can’t say for sure beacause i do not use raspbian (archlinux on the rpi).
I’ll try to help you more if needed. You can contact me directly if you need faster response at bruno AT arcangeli DOT org
Remember to unzip Boost/boost.zip.
October 20, 2016 at 8:40 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70150You need to install libiberty-dev with “sudo apt-get install libiberty-dev”
October 20, 2016 at 8:19 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70148cp /path/to/your/libbfd.a libbfd-$(uname -m).a
cp /path/to/your/libiberty.a libiberty-$(uname -m).a
uname is your friend as the rpi3 has some distribution in aarch64 and some other in armv7l (yes the rpi3 can do 32 OR 64 bit).October 18, 2016 at 2:54 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70143I’ve made some error. I’ve removed my old source tree. There was somethng weird inside.
No it compile perfectly. Work weel.
Sorry.Good work Atom. Thanks.
October 16, 2016 at 3:34 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70140Compile well until:
οΏΌ../../../../Source/Misc/lobject.c: In function βluaO_tostringβ:
../../../../Source/Misc/lobject.c:376:58: error: macro “lua_integer2str” passed 3 arguments, but takes just 2
len = lua_integer2str(buff, sizeof(buff), ivalue(obj));
^
../../../../Source/Misc/lobject.c:376:11: error: βlua_integer2strβ undeclared (first use in this function)
len = lua_integer2str(buff, sizeof(buff), ivalue(obj));
^
../../../../Source/Misc/lobject.c:376:11: note: each undeclared identifier is reported only once for each function it appears in
../../../../Source/Misc/lobject.c:378:59: error: macro “lua_number2str” passed 3 arguments, but takes just 2
len = lua_number2str(buff, sizeof(buff), fltvalue(obj));
^
../../../../Source/Misc/lobject.c:378:11: error: βlua_number2strβ undeclared (first use in this function)
len = lua_number2str(buff, sizeof(buff), fltvalue(obj));
^
Makefile:852 : la recette pour la cible « build/intermediate/Release_Nightly/lobject_d8b8cdb1.o » a échouée
make: *** [build/intermediate/Release_Nightly/lobject_d8b8cdb1.o] Erreur 1
CTRLR[linux]: build failedWith lua 5.3 on ubuntu 16.04 aarch64
October 15, 2016 at 9:04 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70137There’s nothing particular to do for compiling it on ARM.
I’ve tried on Rasbain with succes.
I mostly use ArchLinux on rpi2 and ctrlr version is tagged 3d8651d991d377f7b167806c39c47a3121fe9536 on git.
Go inside Builds/Generated/Linux/Standalone.
Copy your OS version of libbfd.a to libbfd-armv7l.a. Do the same with your libiberty.a.
./build.sh -f
You may need to install some “-dev” package like binutils-dev and libiberty-dev and some other (can’t remember as i’m offen compile myself some app).Now, i’m trying with my Nvidia Jetson-TX1 (AARCH64) running ubuntu. Work perfectly.
September 26, 2016 at 10:27 am in reply to: [solved] Toggle button that change uiPanelBackgroundColour1 in lua #70100The first problem was under my eyes but can’t see it. Replaced panel:getPanelEditor():setPropertyInt by panel:getPanelEditor():setPropertyString.
Now that part work well πSeptember 24, 2016 at 12:53 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70094I’ve conceived my novation circuit panel with the 800×480 resolution in mind.
That’s work perfectly.
There are many screen (mainly hdmi+usb). I’ve got the official screen with dsi interface. As thus i can use the rpi with 2 screens πSeptember 22, 2016 at 8:40 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70088Great, it work perfectly on x86_64 and armv7h (raspberry pi 2) with Arch Linux.
It’s really awesome.
Now i can finish my Novation Circuit panel and share it πSeptember 19, 2016 at 10:03 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70079Ok, thanks. I’ll try this soon π
September 18, 2016 at 9:09 am in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #700575.3 compile ok.
But does not work.
Ctrlr start, i can open a panel. But nothing more. Nothing work inside the window (the menu work). Things are frozen.
I’ve made a panel for my Novation Circuit that work very well on x86 (archlinux) but i don’t want to use this computer for this.
It is a shame…September 17, 2016 at 12:14 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70053That now work.
It need ctrlr 5.3 with lua 5.1 and gcc 4.8…Awesome! Thanks very much.
My problem with Ctrlr is the lack of time to learn it as there is no doc…Great!
Apparently, Ctrlr lack only a good documentation πI’ll now recreate my panel from start. With better naming convention.
The problem (relative position) come from my window manager (awesome) which is a Tiling one. If i manage my window like with “standard” WM, it’s ok.
Changing the owner parameter for each element is a long task… And not very user friendly π
Thanks for your help dasfaker.
-
AuthorPosts