Forum Replies Created
-
Posts
-
Thanks for your bugreport. Creating a panel for an instrument you don’t own yourself can be really tricky 🙂
I will look into the issues and will try to fix them – if I can find some time. Be patient.edit: I think I found what’s wrong with my panel. Unfortunately a lot. I know how to fix it, but don’t have the time to do it.
To be continued …Please download and try new version (or newer) 20180524 from soundmondo.martintarenskeen.nl
Let me know if this fixes the bug or if you find any other bugs
Thanks for reporting. I will look into it if I have the time. I really should visit and read this forum more often 🙂
Did you try escaping with a \ in front of the ‘ ?
Yes I did. Doesn’t work.
OK. Is it documented somnewhere which characters are or aren’t allowed? Then I can make my code work also in unforeseen situations.
Sometimes exiting and restarting Ctrlr helps to establish a working MIDI communication.
console(String(“Hello World”)) should solve the problem
OK, thanks. But why? And does this make it not-a-bug?
Seems a lot of typing just to say “Hello World”.Hi
I don’t own any MKS-50 or K3 but your panels did attract my attention because the graphics really LOOK great. Beautiful layout, choice of colors, buttons, and sliders! What software, outside Ctrlr, did you use to create the graphics? Did you design everything yourself or did you use existing collections of buttons and sliders?
Hi
I don’t own any MKS-50 or K3 but your panels did attract my attention because the graphics really LOOK great. Beautiful layout, choice of colors, buttons, and sliders! What software, outside Ctrlr, did you use to create the graphics? Did you design everything yourself or did you use existing collections of buttons and sliders?
I have experienced loss of my Lua code more than once.
In some occasions it happened after disabling Lua, this is (or hopefully was) a known bug that was reported somewhere in this forum before.In some occasions I have lost my work after I made a coding error that would crash Ctrlr. It’s very easy to make LUA typos and programming errors. I do that a lot 🙂
But loosing all my work should not be the result.It would be nice if Lua code could be saved and loaded separately from the panel xml file, in a separately editable text file. That would make it easier to fix bugs if a Panel crashes before you have a chance to fix it.
The key word is: LISTEN to them.
also have yammy dx27 … a worthless pice of crap … fm 4 op , no filter , not many parameters for sound tweaking
I don’t agree. DX27, identical to DX100 can make great Bass and Percussive attack sounds and Metallic sounds and Bells for example. No filter? So what. It’s an FM synth. Not many parameters for sound tweaking? 94 programmable parameters is not “not many”, if you know how to use them. But if you don’t like the sound, choose another synth.
About the LFO parameter change:
I think it has something to do with FB01’s way to handle the LFO in a multi/configuration vs. voiceparameters in a single voice.
Configuration parameterchange values are 7-bits (one byte), Voice parameterchange values are 8-bits (2 bytes with 4-bits used in each).
It’s easier to write a Ctrlr panel for the configuration parameters than for the voice parameters. The FB01 voiceparameter sysex will need some custom LUA coding to be handled.
BTW: I have started creating a FB01 panel myself, but hardly have any time to work on it.
This thread is drifting away from my original question, which still isn’t answered:
why does
console("Hello World")fail and generate all these error messages since Ctrlr version 5.5.2 ?I frequently use the console() function to insert code in my LUA code for testing and debugging purposes. For example to track the value of certain variables when doing things in my panel. The console window has to be open to see anything. Or, on my Linux laptop, sometimes I start Ctrlr from aterminal window and I can see the messages in the terminal window, or redirect them to a logfile from there.
If you want all kinds of strings and values to show up in a dialog window that pops up from a panel there are other methods that you need. There are several examples of that in the Ctrlr DEMO distribution.
I think the layout is clear download->ctrlr/panel and a big Download-Ctrlr link
Strange. The ctrlr/panel menu is working again. Thanks.
What do you mean? What have you tried?
1. Start ctrlr
2. From dropdown menu go to: Panel -> LUA console
3. Click on the bottom part of the Console
4. typeconsole("Hello world")
5. The text “Hello world” should appear on the upper part of the Console.If this works, you can try using console(“Any text bla bla”) in LUA code you use for your Panels.
I have reverted to Ctrlr 5.4.29 after having too much trouble with 5.5.2.
OK, thanks. The ctrlr.org/panels link works. But still the question remains: where has this link gone on the ctrlr.org opening home page? It used to be below the “Downloads” where you could then choose between the Ctrlr download page for executables or the page with Panels to download.
I have been away from this forum and website for quite a while, so maybe I missed something.
If I click on Downloads, it directly sends me only to http://ctrlr.org/nightly/ which gives me a list of downloadable Ctrlr versions.
What happened to the Panels pages? Where can I download the Panels?
an old thread but if anyone is still into it, I found this, might help?
I already know most of the SysEx secrets of the FB01 and an FB01 ctrlr panel is on my TODO list. I know how to do it, but don’t have much time to do it.
And yes, the FB01 is a strange unit where SysEx implementation is concerned. Very different from DX21 and TX81Z. But also very powerful. And I am not talking about those 8 waveforms that are not as important as some people think. I have written SysEx editors for both FB01 and DX21/TX81Z in the 90’s (YSEDITOR for ATARI ST) so I know what I am talking about.
