Forum Replies Created
OK. I’ll support if I can!
When I get my arpeggiator working I’m going to release the first beta panel.
I’m afraid you could get into troubles, specially if you want to sync LUA events with the host.
And I can only agree with dasfaker.
Don’t think Ctrlr is made for syncing from what I read on the forum.
My blinking LED according to tempo for example is just for the look of a panel but the underlying tempo mod is well sending a correct CC to change tempo on the synth.
You can code an arp but only to send notes to a synth and hear the sound but not to use it as part of a song using several synths. I was planning to do the same for a simple sequencer but only with the goal to play some notes, absolutely not for accuracy and sync. For that we have DAWs and sequencers 😉
I have exactly the same thoughts and feeling as you, Tedjuh.
That’s why I didn’t insist when I didn’t get further push from Atom to help him.
I’m also accepting Ctrlr as is and that’s why I stick to 5.3.201.
Now, I’m very happy to help other people and as I said I continue expanding the Step by Step guide when I’m in the mood.
Give you some challenge then start working on it and by searching on the Ctrlr forum, in Juce classes and other general doc you will always learn something and progress.
Now I finished a panel for the Prologue (quite big work) on request of someone else and I’m giving me some fun and challenge by coding a wave editor. Challenging and fun 🙂
About the arp, if you need a blinking LED according to tempo, I just did that for another synth and to be honest, it is very cool. So, just let me know.
OK. Lot’s of posts…
My friend found the issue (some authorization in Program Files).
He has been putting the panels in the standard Program Files / VstPlugins folder and this seems to have created some issues (probably some access issues).
Putting all panels VST somewhere else solved the issue.
Good to know for all of us!
About supporting Ctrlr dev, my proposal is still valid 😉
Thx to all!
Still on version 1909 here. So I won’t be of much help here. Thing is that I found out the hard way that I had to install older c++ redistributables to get some vst’s from well-known manufacturers to work. Had to tinker in the registry. Had to put vst dll’s in certain windows folders before studio one or fruity loops would even recognize them, and so on. And sometimes there’s no way to tell where the problem lies. Is it windows, the vst.. missing packages?
My friend has FL.
He got the issue when completely re-installing his PC. Thus Win 10 2004, FL Studio, and Ctrlr.
I just asked him and he was in 2004 before the re-install.
So, the issue he is getting is when re-installing Ctrlr on Win 10 2004, and FL.
Any idea on which C++ libraries would be missing or other stuff needed?
Would really help 🙂
I took a lot of time to dig into Ctrlr; I made a free panel for the Pro 2 which includes not only an editor but a full librarian, I wrote a step by step guide that helped newcomers understand what Ctrlr is (in fact I continued extending it with tons of stuff, Lua programming…), I’m also contributing to the forum (not like others also selling panels)…
I have been asked by people to develop some panels for synths I don’t have and they said it was normal that I ask for a little contribution. As you all know, making nice panels is not done in 1hr but rather 100-150 hours even if you can re-use some of the logic between the panels.
I also think that it is normal to provide updates with new features for free.
So, I feel quite OK in my shoes 😉
That being said, I proposed Atom to support with simple tasks like writing explanations on the meaning of the properties, etc… (we have links but no popups with explanations). Didn’t get a positive answer on that but I’m still OK to do that.
About Ctrlr as such, I’m OK to start studying the source code, to learn it, correct bugs… but only if starting from 5.3.201. I would also need explanations on how to build and assemble the whole package (didn’t find explanations on that; anyone?). I don’t know C++ or C# (I know well some C) but I have learned several languages (Lua being the last one) and it is no problem on that side thus.
Just some basic info and I can support from there at my pace (this is still a hobby for me).
Quite many gurus in this thread 🙂 Love you guys!
Working here on Win10 2004 and Reaper v6.13.
Good to know!
So, I don’t think it is a Ctrlr vs Windows 10 2004 issue but something else…
Did you do anything special or just left your 5.3.201 version there between your Windows upgrades?
Thx for replying!
Standalone is working fine.
Happening when doing a drag and drop of the plugin to a new track.
Other plugins are working fine.
Here is the message
Attachments:You must be logged in to view attached files.July 29, 2020 at 2:17 pm in reply to: Radio button in a modulator group needs a default setting #119327
That’s why it is best to use a variable name like sName (s for string) instead of n even if Lua do not make the difference.
About the Called on mouse down vs Called when changed:
– with uiImageButton, indeed, the OnClick is only fired when you click on the label. I’m using that to display some value or help text without changing the actual value
– but I’m going further by redirecting my OnChange method to the OnClick one because I also want to display the value and help text when the user changes the value
-- -- Called when a modulator value changes -- @mod http://ctrlr.org/api/class_ctrlr_modulator.html -- @value new numeric value of the modulator -- OnOff_OnChange = function(--[[ CtrlrModulator --]] mod, --[[ number --]] value, --[[ number --]] source) -- No action while loading a program or if the panel is in bootstrap or program states if not isPanelReady() then return end OnOff_OnClick(mod:getComponent()) end
Best of both worlds 😉
I am new to CTRLR but I found out that it works with Momo’s D-05 editor on my Mac. Standalone and as AU in logic x, but no snapshots and still I can’t find out how to save and load anything.
Bulk dump didn’t work with the Thunderbolt interface but with the usb ( probably 1.0)midi cables. Well I just moved a few parameters and saved it in the D50 what more to ask for-/- lol
Hi, it is the responsibility of the panel developer to secure a well functioning panel.
I don’t know if Load/Save are foreseen in Momo’s editors. did you ask him?
In a more general way, snapshots have been implemented quite a long time ago in Ctrlr and I’m not sure if this functionality has been completed or not.
And don’t forget to also adjust Expression to evaluate when calculating the modulator value from the midi message value to the opposite 😉
what is the progress for your DP4 editor?
Finally, I just got a DP4 🙂
In parallel, I made and released a panel for the Behringer Odyssey. In that one, there is also a multi effect with different types of parameters for each of the 3 parameters by effect.
I found an easy way to handle all parameters and their different types, limits, min/max…
I’m also interested in that one 😉
I put it on my to-learn and try list but didn’t get a chance to do it by now 🙂
The “source” parameter is working fine.
To prevent Lua functions to be fired you indeed need to set a boolean, add a test at the beginning of all your “OnChange” methods, launch a timer to reset the boolean after all methods have gone through the test.
I’m using this for loading data in all modulators from a file.
Before starting the load, I set bLoadingProgram=true. In each OnChange methods i’m testing if bLoadingProgram == true and doing a direct return in that case.
All methods will be triggered due to the load of each parameters.
I also start a timer at load. Set it to enough time to have all your methods processed but not too much.
When stopping the timer, reset the boolean to false so your methods are executed nicely on manual turn of a button.
Standalone is good for testing.
Use 5.3.201 on PC, 5.3.198 on Mac.
Well… this is really strange… Ctrlr is bidirectional by default…
There is nothing to do.
Can you give a screenshot of your Midi settings?
You try with Ctrlr standalone, right?
Ok good! Can you post a screenshot of the midi monitor with both input and output sysex messages in?
Are there really the same?
It should work.
Did you use uiSlider or uiImageSlider?
Please try this panel.
FYI, I tested with uiSlider and it didn’t work. With uiImageSlider it works.
Let me know if it works with this test panel.
Attachments:You must be logged in to view attached files.
There is no need to use Lua coding to have bidirectional behavior for single parameters exchange (of course, well needed for requesting and receiving dumps).
– what are trying to achieve with f0 3e 22 11 10 00 00 34 xx f7?
– stay in Ctrlr panel development mode (no need to export anything to test this)
– you said your Midi input and output settings are ok in Ctrlr
– start the Ctrlr midi monitor and activate input and output monitoring
– if you send the sysex from the panel, do you see it appearing in the monitor output?
– if you send the sysex from the synth, do you see it appearing in the monitor input?
Please provide more info if you want to get helped (which synth, which parameter…)
Welcome to Ctrlr!
if needed, you may get some info in my Step by Step guide https://ctrlr.org/forums/topic/ctrlr-step-by-step-guide/
There is a limitation to 64 parameters to be exported so it might be your issue. One way to reduce is to strictly enable export when necessary.
However, you will still reach 64 pretty fast.
So, the other way is to add a ctrlr.overrides file that you place in the same folder where is installed the plugin Ctrlr.dll. Rename it to the same name of the plugin and extension overrides (in my case is “Ctrlr-VST-x64.overrides”), and set the changes listed below, otherwise you could only see 64 parameters (and none of them are related to the synth engine).
<?xml version="1.0" encoding="UTF-8"?> <ctrlrOverrides ctrlrMaxExportedVstParameters="5000" ctrlrShutdownDelay="256" ctrlrUseEditorWrapper="1" ctrlrLuaDisabled="0" ctrlrLogToFile="0" />
For your bidirectional sysex issue, it should work without any script or so.
I’m testing this with my Novation controller. when not working, check some basics:
– Start synth then panel
– check Midi Input and Midi Output settings in panel
– if sending from panel to synth is working, then your sysex is correct
I saw that this panel has not been replaced in 5.3.201 and the int64ToInt function is still not working.
What is this function supposed to do?
If we know that then we can re-code it ourselves.
Is the issue coming from the int64ToInt function or from the data it gets as argument?