[Possemo]

I did never manage to get these flags working correctly in all cases. In particular, Lua scripts are always triggered in most cases. Also, on instances there is a problem on startup. It will trigger a load of modulators on startup sending a big mess to midi-out. Only way for me: use toggle variabal as dnaldoog suggested. I use it like this:

if doNotSend then return end

This is short and painless.. more or less.

[Possemo]

These are nibbleized values. As MIDI cannot send higher values than 127 big numbers are broken down in nibbles (a fragment of a Byte).

In a listbox you would do that like this:
1=16383
2=0
3=1
4=2
5=4

And the sysex message is as follows:
F0 18 0F 00 55 01 02 05 01 LS MS F7

LS are less significant bits and MS are more significant bits

[Possemo]

I guess you are on MacOs. In this case you should use the AU-Plugin. To my experience the sliders should move a bit smoother. Ableton is able to use both vsti and au.

[Possemo]

I wouldn’t bother to cut down the panel in order to being able to upload it here. Just use google drive, ms one drive or something similar. I think google drive is very nice, you get 15gb of free space. Google won’t delete your data after while like other free cloud services.

[Possemo]

@dnaldoog: These are instances done with v5.3.201 – so no problems with Ctrlr versions here.

@prple_1: I haven’t seen your post. You should have sent me an email maybe I could have helped you. Now it’s probably too late and you have lost interest.

@jovius: This is the same panel as prple talks about. The vsti does not work equally well on all DAW’s and you have to set it up correctly. Have you read this?: http://roet32.wixsite.com/ctrlr/tutorials

[Possemo]

No idea why this happens. I would try another DAW, e.g. Reaper. Reaper does work nicely with Ctrlr and it is free (with a nag screen at startup). Another advantage of Reaper: you can load 32-Bit and 64-Bit plugins so you can generate instances for both.

[Possemo]

Pictures do not show. Can you post a .bpanelz file? Menu File -> Export -> Export compressed binary + ressources.

I once had an idea making a panel for my TX81Z which would move the operators when changing alogrithm – placing them in the panel to show the selected algorithm. It would be some work but feasible. Well on the XFM2 which allows connecting the 6 ops freely that would be quite challenging…

[Possemo]

I used global vars in one of my panels. You can set them like this:

panel:setProperty("panelGlobalVariables",m1..":"..m2..":"..m3..":"..m4..":"..m5..":"..m6..":"..m7..":"..m8..":"..m9..":"..m10..":"..m11..":"..m12..":"..m13..":"..m14..":"..m15..":"..m16..":"..m17..":"..m18..":"..m19..":"..m20..":"..m21..":"..m22..":"..m23..":"..m24..":"..m25..":"..m26..":"..m27..":"..m28..":"..m29..":"..m30, false)

Here I did set 30 vars – named m1 to m30.

The XFM2 looks very interesting. I first wanted to ask you what you are meaning by “bitmapped parameters” but then I read about this fully featured 64-voice 6op FM-Synth. In the MIDI implementation chart I see as much as 454 parameters! Instead of fixed algorithms you can build your algo yourself with this bitmapped parameter… great!

Maybe other people will be interested in this astonishing project: build yourself an uber-dx7 for less than $100.
https://www.futur3soundz.com/xfm2

And it sounds damn good:
https://www.youtube.com/watch?v=fJyIRA1ev-A

Edit: this is an old post – obsolete by now. I did’t realize that you must not include links in a post.

• This reply was modified 3 years, 11 months ago by dasfaker.
• This reply was modified 3 years, 11 months ago by Possemo.

[Possemo]

How does unstabiltiy manifests with 5.3.201? In general you should be able to go back to 5.3.201.

Ctrlr should be able to handle several modulators having the same name, but there may arise problems if they are updated by Lua code. I dont know as I clean them up in my panels (a good idea anyway). The modulator-list is quite helpful for this, Menu: Panel->Modulator list.

Editing the xml-file is tricky, I would avoid it unless there is no other way.

When you are updatin the ui, could it be that the button gets a value beyond its range? A button expects value 0 or 1. If you need the button to send other values you should set them like this:
OFF=32
ON=64
But to update the button you still have to use 0 and 1.

Buttons are another thing in Ctrlr that is wonky. You can make Ctrlr work flawlessly but you have to work around bugs…

[Possemo]

I would use the recommended stable version v5.3.201 …could save you some headaches.

btw. the XFM2 looks like one great project. Building yourself an enhanced DX7 which sounds great (listened to youtube) for just under 100$. But with over 450 parameters it won’t be the easiest editor to make… I wish you all the luck.

[Possemo]

I did use global variables in one of my panels. You can set them like this:

panel:setProperty("panelGlobalVariables",m1..":"..m2..":"..m3..":"..m4..":"..m5..":"..m6..":"..m7..":"..m8..":"..m9..":"..m10..":"..m11..":"..m12..":"..m13..":"..m14..":"..m15..":"..m16..":"..m17..":"..m18..":"..m19..":"..m20..":"..m21..":"..m22..":"..m23..":"..m24..":"..m25..":"..m26..":"..m27..":"..m28..":"..m29..":"..m30, false)

m1 to m30 are variables, m1 is the first one, e.g. k1… etc.

[Possemo]

Thanks for your answer. Yes I already went the way with powershell. I still get the problem that when I include a path in “your_wav_filename” it won’t do anything – it seems that it passes wrong values, maybe for the backslash (\).

Nice that it does work for MacOs too, thanks.

Just to tell what I’m trying to do:
First I thought that goodweathers panels, which cannot send their data to the synth (because tha synth isn’t able to save/restore patches) were somewhat “free of sense” but in fact it can be helpful to keep a patch-sheet within a DAW track. On a vintage Minimoog it would also be very interesting to hear how a patch does/should sound. There were several revisions of the vintage Minimoog and these over 40 years old tail draggers can sound very different. ATM I am spending my little free time to restore my Minimoog to factory specs. I think it is getting close being an acceptable reference for how a patch should sound.

It will try to record a soundsnippet for each of the Minimoog Model D Patchbook. It would be the nicest if I could integrate the sounds into the panel (via ressources) and make a procedure that saves the .wav to disk to play it back and then delete it.

No idea if this will work, I will see. But before I should finish the panel for the Korg 05r/w… so this will take a long time.

[Possemo]

I just never have time to spare for this panel. But as it is already about 90% done I am confindent that I will finish it this year. For now the library will need to be loaded each time you start the panel otherwise it will crash. It is able to load files from other editors – .pcg files (Korg X3) and .05r files.

I wanted to attach the unfinished panel to this post but it seems that it does not accept even a tiny 1.1 MB file anymore.

Here from google drive:
https://drive.google.com/file/d/1ouZPakR-XcJdlDCQldg7luGG4LF4JYs3/view?usp=sharing

And some patch banks to try out:
https://drive.google.com/file/d/1oCyM4fJvgaEoYfkRk7TZnHU2zQRQoAkf/view?usp=sharing

[Possemo]

Maybe this guy has an ancient MacOs and/or he is using an old build of Ctrlr. os.time() does work on actual MacOs’es with the actual Ctrlr Mac-build. As an alternative you could use math.randomseed(Time.getMillisecondCounterHiRes())
In theory the hires counter should give a better seed but my experience is that it just gives slightly different results. Sometimes better, sometimes worse than my other method:
math.randomseed(os.time()*os.clock())
It seems that a big number makes a better seed.

[Possemo]

Is your Juno2 set to midi channel 1? Maybe you have to enable sysex on the synth I don’t know the Alpha Junos.

[Possemo]

cool, I wanted to suggest that your panel seems to be mature enough for putting into the panels section. The panel progresses at fast pace, you got my respect!

[Possemo]

you would make two messages in multi mode:

CC,ByteValue,MSB7bitValue,106,-1
CC,ByteValue,LSB7bitValue,107,-1

[Possemo]

John Shin wrote:

Now you can ignore my first question, here is my new first question with sub-questions:
1. what do I do with these..?
a) Midi channels (I see 5 of them and I set it as 1 for all)
b) Plugin check boxes: do I tick BOTH of them or none..?
C) OSC Server settings: do I enable it or no? (it is currently 7770 and protocol default.
d) ROUTING section: which ones do I tick and which ones do I ingore? (currently I ticked “IN Device -> OUT Device & right side of it “change MIDI Channel” ticked)

2. also another question, I AM totally not to judge nor compare it to any other applications, but since I am so new to this,
what are the differences between Ctrlr panels editor AND a) Soundtower prophet 08 editor and SYNTHET (which you need to purchase)?
are functionalities the same?

Tryin to answer these questions first.

a.) midichannels have to be set to the same on both the synth and ctrlr. If you want to know what midichannels are good for just google it.

b.) in standalone and in Cubase as plugin: uncheck them all
c.) osc is not needed, disable it
d.) do not tick any of them. If you do so it can produce midi loop feedback with lots of strange behavior.

2.) I have no idea as I don’t know any of thes editors and I don’t own a prophet 08.

Just set midi in and out in Ctrlr – disable the controller. As on Mac many apps can use the same midi port in parallel just run Ctrlr-standalone and Cubase in parallel. Connect your controller in Cubase not in Ctrlr. If you use the plugin within Cubase you basically set up Ctrlr the same way. Just be aware that Cubase cannot connect to a midiport which is already used by the Ctrlr-plugin. So you can have only one track with the Ctrlr plugin enabling the midiconnection.

• This reply was modified 4 years, 8 months ago by Possemo.
• This reply was modified 4 years, 8 months ago by Possemo.
• This reply was modified 4 years, 8 months ago by Possemo.

[Possemo]

So you already installed Ctrlr and loaded the panal into it and connected midi out? Ok, for full functionality you need to connect midi in too (from midi out of prophet). Furthermore you need to set up the prophet correctly. Carl explained it:

The most important is your midi connections : first check your midi connections in ctrlr (midi input and output, sometimes it doesn’t match with naming of devices.. check your computer midi configuration too).

Then click on “Get” button under GLOBAL area of POWER08 panel. if you see “?” in “receive” and “send” boxes, then you have to check your global parameters directly on your synth : –> Global –> + or – to navigate –> and verify that these parameters are correctly setup :

– MParam Send:NRPN
– M Param Rec: All
– MIDI Control : On
– MIDI SysEx: On

Then you can hit “Get” again and you will see the update in “receive” and “send” boxes.

Hope this helps!

Try with standalone first, plugin can be tricky at times.

• This reply was modified 4 years, 8 months ago by Possemo.

[Possemo]

Ah I see, this free EG is a nice feature. I have never done such a thing but I guess it should be possible with a uiCustomComponent. That will definitely need advanced scripting skills. Attached a demo panel with a mouse draggable envelope. There you can see how you handle mouse movements/events. I have no idea how you could read out what pixels are on/off. I’d probably do it separated – fill a table with values while the mouse moves and draw points in the customcomponent separately.

Attachments:

You must be logged in to view attached files.

[Author]

Posts