[Filch]

They’re building their own control panels, or they’re being hard core on quality control of anything with the word Moog on it and only want approved items. So if someone makes a shitty panel and slaps Moog on it, someone finds it and thinks, "Man, this is not the quality I expect from Moog."

Protecting the brand, but I think it’s a little much.

[Filch]

Hahaha, fucking Moog… seriously, c’mon.

I’m going to start naming and labeling them MOHG then.

[Filch]

All I can say is, WoW. This is unbelievable. I’m in awe.

I can’t wait to get my hands on this just to glean some design and programming knowledge from this.

[Filch]

"msepsis":3bms78wp wrote:

I like Filch’s suggestion to make two options – place modulator where it is into the group, and place at 0,0 within the group. Different strokes for different folks. I still think place it where it is should be the default action when you add a modulator to a group.[/quote:3bms78wp]

Actually, just do place modulator in relation to it’s position of the group it’s being added to. And if someone speaks up and wants it another way, they can do that and have it changed later.

[Filch]

changelogs seem to be broken again

[Filch]

"msepsis":svpm9atz wrote:

"Filch":svpm9atz wrote:

.. Only problem is that for people who want to add stuff to a group that’s not already positioned in the group where they want it…[/quote:svpm9atz]

good point, but I tend to think that would be relatively moot provided they were able to move the position of the modulator once it’s in the group.. when promoting a modulator to a group I don’t think Joe user would expect the position of the modulator to move, he’d just expect it to be added to the group, where they currently are, then tweak position after if need be… just my two cents.[/quote:svpm9atz]

That is my thinking as well and I agree, that’s how I want it to work and think it should work.

[Filch]

Yes you can move it once it’s in the group, but not via arrow keys. At least it wasn’t working last time I tried it a month ago.

[Filch]

That’s how I would like it. Only problem is that for people who want to add stuff to a group that’s not already positioned in the group where they want it. Perhaps an option asked when sending to a group.

"Send to group/tab relative to panel position"
"send to group/tab relative to group/tab position"

[Filch]

It’s not just you, it’s a bug. You have to manually type in the coordinates or mouse it.

[Filch]

Here is what happens.

Each object on the panel has an X,Y location (plus size). Say your object is located at 100,200 on the panel. When you add it to a Tab or Object, it’s location will be 100,200 BUT it’s relative to the Tab or Object location, not the panel anymore.

If you expand that tab or group size past the range of where your object is supposed to be (its x,y location relative to the 0,0 point of the group or tab), you’ll see it.

It’s quit annoying, but workable once you figure out this is what it’s doing.

[Filch]

Sounds like maybe a parameter is getting a value incorrectly, or your getbyte value is for another parameter than what you set it for. When the setting for the panel modulator is updated, it is then outputting a value which is changing your XT value to something different than it was.

One way to start trying to figure this out is to perhaps parse your your midi dump into a list with the modulator name and the value it thinks it’s being sent, then cross reference that list with the current patch parameters on your XT. A PITA, but step forward in finding the bug.

[Filch]

Aye,

I’ll try to answer any questions along the way. I was a noob too not just a couple months ago, you learn quick.
I’ve taken a break from building/coding the last few weeks, but I’ll be back at it full steam shortly. Going to try and contribute on the JP8080 panel msepsis started.

[Filch]

I’d be more than happy to contribute when I get some time. It’s looking good already. I say keep it all in one panel and use tabs or groups to hide things if you want vocoder settings on it’s own "page".

[Filch]

Hrmm.. don’t know what to say about the linux stuff. I assumed the panels were transparent to the ctrlr "client", what works in one should work in the other. Unfortunately I don’t have a linux build to play around in.

Take a shot in the windows build and let me know how it goes.

[Filch]

+1 mr Sepsis , agreed here. There’s been countless times where I wished for this.

[Filch]

getting "attempt to call method setProperty is a nil value". What am I doing wrong here :

[code:2k5mtwef]
l = panel:getModulatorByName("LFO 1 Speed")
b = panel:getModulatorByName("LFO 1 Box")

if l ~= nil and b ~= nil then
lVal = l:getModulatorValue()

if lVal <= 1 then
text = a[0]
else
text = a[math.floor(lVal/2)]
end

b:setProperty(uiLabelText, text, false)
end
[/code:2k5mtwef]

[Filch]

I was thinking a uiLabel before, but I didn’t think I could use a table of different values, but as you clearly point out, setProperty would do this. Thanks Atom!

[Filch]

?

[Filch]

Whoa!!!! hahahah

[Filch]

Ah, Just realized. I don’t need the method on the LFO knob. My method on the Box itself is working, but I only see it repaint the text if it’s within the component field of the knob I’m turning. I found this out because I placed the box near my LFO knob, the LFO component window overlapped the BOX window a bit, and the overlapped part was getting redrawn.

So how do I make this box redraw the text without being inside the component that I’m adjusting?

I’ve attached a small panel that illustrates what is happening.

[Author]

Posts