[Filch]

Have you looked into ctrlr at all? The whole thing about v5 is being able to build panels quickly and easily, no coding necessary.

[Filch]

You’d have to build a panel yourself or get someone to.

The ones currently built or being worked on are here :
viewforum.php?f=61

[Filch]

Those are ctrlr v4 panels. Those will not work with the current version , ctrlr v5

[Filch]

I see. I assumed they were there before based on the Changelog link at the top of the page : "[DONE]: add background for groups"
I have no idea when that was written though. I thought that might have been current. ” title=”Smile” />

That’d be great to have though in a future update.

[Filch]

Any chance background images for Groups will return, and/or possibly adding background images for individual tabs?

[Filch]

"sawan":2lrb46o1 wrote:

is there any backward compatibility with older ctrlr panels?[/quote:2lrb46o1]

negatory

[Filch]

I thought about filing the bug, but I wanted to be sure it wasn’t something weird on my end only. I’ll submit one so it can be looked into.

[Filch]

Just tested this by adding one Loopbe midi port at a time and it starts to exhibit the behavior I described when I reach 18 total ports selectable.

[Filch]

Yah, the Panel Properties drop down.

But I notice there’s a problem at just activating the ports from the ctrlr Devices menu. When you activate the Blofeld port for use, it turns green and a checkbox appears next to it. I can then select it from the panel dropdown. But if I have more than 14 devices, when I specifically select Blofeld (blofeld has its own usb port) , it get’s a check mark, but it doesn’t turn green. At that same moment I select it, my Multiface port gets checkmarked and turns green. The panel dropdown will then show the Multiface, but not Blofeld.

It also works reverse. In the Devices menu, If I select Multiface, it turns green and gets a checkmark, but it also selects the Blofeld and gets a checkmark but not turn green.

So I know this happens when I have 19 midi devices to select from, I know it fixes itself if I drop down to fourteen or less (removing one of my various usb midi hubs). So I’m thinking this breaks at some point at 15 or higher. I don’t have single midi devices to plug in to add one at a time, but I can use a midi loopback app to add ports one at a time. I’ll try that and see if I can figure out at which point it breaks.

Do you have more than 14 devices selectable, are you having any issues when selecting?

**edit**
I figured I should specify that I’m using Windows 7 x64 sp1

[Filch]

I’ve come up on a new bug. If I have 14 or less midi devices, I can activate them all fine and they work normally. But when I have 19 devices available (adding a motu micro lite), I have problems when selecting some midi ports for activation.

For example, if I activate my Waldorf Blofeld driver, it selects that, but also my Multiface out. The blofeld stays grey, but the multiface is green. And when I go to the panel dropdown on the panel to select which output to use, the Blofeld doesn’t show up. It’s missing. If I deactivate either, they both deactivate.

I’ve left the micro lite plugged in and unplugged a motu 128, and the problem goes away. So it’s not the microlite that is causing the issue. What I know is the problem occurs at some point when my available midi devices are somewhere between 15 and up.

[Filch]

Topic probably should have been placed in Using Ctrlr instead of News and Releases.

There was a v4 editor/librarian for the Supernova done, but v4 is no longer supported as atom is diligently working on v5, which is good for everyone because v5 requires no programming experience to build a panel for your software synth.

So you have it right, download ctrlr, start building a panel for your supernova. If you have questions about something, do a search first, and if you don’t find your answer, ask away.

[Filch]

cleanup

[Filch]

Nice!

What’s next?

[Filch]

Doing great atom. Thanks for the update. Keep up the great work you’ve been doing. I’ve sent a small donation to support your efforts. ” title=”Smile” />
I’m looking forward to the next update!

Quick question about the LUA update. Will it by chance include the ability for one modulator to read the value from another modulator and send a bitstream message based on those combined value as specified by a formula?

[Filch]

I’m almost complete with this panel as far was what I’m able to put into it with the current state of ctrlr. Tabs are not quite working yet so my layout is bigger than is intended.

There’s a few parameters in here that are combinations of each other sent as one message. Because of this I have been unable to implement a proper solution for them yet.

For Example :

The Trigger Mode and Envelope mode are combined into a bitstring value and sent as one message in the following format :

0ttmmmmm

tt = Trigger Type

---

0 normal
1 single

mmmmm = Envelope Mode

---

0 ADSR
1 ADS1DS2R
2 One Shot
3 Loop S1S2
4 Loop All

So if I selected a Loop All Envelope and wanted it as a single trigger type. My bitstring would be 00100100 , or 36 in decimal. The problem here is that my buttons to select Trigger Type and the drop down box to select Envelope Mode are not aware of what each others values are or when its changed. I believe the only way to get it to work that way would be with some LUA code.

My only solution for this in the meantime is to have a drop down box with the Envelopes listed twice, like ADSR Normal and ADSR Single. But this won’t be a good solution for the arpeggiator which uses 3 variable values in the bitstream sent : step, glide, and accent values. That’s too many combinations to put into a drop down box. So the arpeggiator programmer is out for now.

[Filch]

Looking good, sir!

[Filch]

From what I understand, ctrlr does not currently support more than 2 images , so a 4 state button won’t work.

Just tested : Changing the value for uiImageButton On State = , and Button Off State = , to anything other than 1,0 , the image does not change as you describe. Interesting for me, if my on/off state is anything but 1,0 , it will not send out the correct value over midi. It sends 1 every time, on or off. Once I revert back to 1,0 it sends those values out correctly.

I’ve also tested this out on Mostrum’s WaveXT v1.99 panel , and the behavior is the same. Change the value to anything other than 0,1 , the image stops working and the values sent are not correct.

[Filch]

You need to make sure the Frame attributes are the same size as your button graphic

[Filch]

Nice. I will totally try that tonight. I liked what you did with the mod/pitch wheels on your Wave panel. And the updated knobs on 1.99 look really good.

I will probably be bothering Fozzie soon enough once I get the rest of the panel done. I’m starting to hit the more complex portions of the midi implementations now. Hopefully I can pick it up quick and get a mostly complete version out.

[Filch]

This is very exciting progress here. It makes me want to get back into coding again.

[Author]

Posts