[dasfaker]

Happy Holidays!!

[dasfaker]

Well, here is an example with two modulators that update each other. In revision 765 it works as expected, but in 780 it doesn’t.

[dasfaker]

I’m getting a stack overflow message in code that previously worked. When I need two modulators that share the same cc to be updated when I move one of them, I put this code in both modulators, so when I move modulator "A" updates modulator "B";

[quote:7kqozryq]f1 = panel:getModulatorByName("Filter 1 Cutoff")
if f1 ~= nil then
if f1:getModulatorValue() ~= newValue then
f1:setModulatorValue (newValue, false, false, true)
end
end[/quote:7kqozryq]

It shouldn’t give a stack overflow message, because modulator "B" only updates when it has a different value, so once it’s updated and they share the same value it should stop updating "A", but it appears that it is ignoring the line [i:7kqozryq]if f1:getModulatorValue() ~= newValue then[/i:7kqozryq]

[dasfaker]

Any formula that has a global variable. For example, F0 00 20 33 01 00 6f k0 55 xx F7. In this formula, when moving a physical knob, xx displays xx value + k0 value. If you move the modulator knob on the panel it works fine. It’s only when the modulator receives midi

[dasfaker]

"dasfaker":20n0sbof wrote:

· Sliders with sysex formula and global variables, when they are controlled from a physical knob, behave strange. If I turn the knob to 0, the modulator in the panel only go to position 64 (middle). When the physical knob goes to the middle, the modulator goes to 127. It’s like the modulator starts at +64 (coincidentally, the global variable of those modulators is 64; I have to test it with other value).
[/quote:20n0sbof]

I can reaffirm this bug. The value the modulator displays is it’s own value + global variable

[dasfaker]

Of course!!! I had forgotten those functions. Thx for your fast reply, msepsis!!

Atom: I supposed the colours meaning, but there are some methods in black that work, may be the docs weren’t updated

[dasfaker]

I’ll wait the new revision, if problems persist I’ll send you an example

[dasfaker]

Hi doshult.

I appreciate you take the time to test the panel, I’m not offended at all.

In the first place, the panel if for OS 4.5. I have it installed in my Snow (beta version) and works perfect. I haven’t tested the panel with an older version, so I don’t know if it will work. What I know is that in very old versions (may be before v3) some parameters aren’t governed by the same sysex string or cc as in newer versions, and some of them are Unison, Reverb and Arp parameters that I remember (what is causing that old patches not always load right).

ASAP I’ll upload a new version of the panel (today I think) that should work fine with all modulators, but always in os 4.5, and the Virus in single mode.

[dasfaker]

Hi Atom

I’m having several troubles with this revision. The strange thing is that those troubles aren’t happening always.

· If I enter in edit mode, not always I am able to select modulators to edit. I click on any modulator but the modulator doesn’t get selected and can’t see the modulator properties.

· Half of the times I close the panel, Ctrlr crashes.

· Half of the times I open the panel, the method called when the panel has finished loading is not working (method executed with no errors, tested). In fact, many times I click the icon Run method in a safe LUA state in this method Ctrlr crash.

· Sliders with sysex formula and global variables, when they are controlled from a physical knob, behave strange. If I turn the knob to 0, the modulator in the panel only go to position 64 (middle). When the physical knob goes to the middle, the modulator goes to 127. It’s like the modulator starts at +64 (coincidentally, the global variable of those modulators is 64; I have to test it with other value).

· The font used in the method’s editor sometimes change to Arial. When this happens, the position of the cursor is not the real position of the cursor, so it’s almost impossible to edit text.

Any tip on whta’s going on?
Thx.

[dasfaker]

Don’t worry, rev 765 is still rock solid.

[dasfaker]

I didn’t want to give the impression that VirusControl works bad. In fact, in my computer works fine, and do all the adds says. But it’s like any other vst, with the problems of vsts (latency specially). Access should make a VirusControl without audio to let you choose the way to go.

I’m very grateful about your words, mainly because I have little experience programming and about sysex (seems that your Waldorf panel is way more complicated in this area). Anyway, if I can help you (or anyone) with anything please ask. And excuse my English ” title=”Confused” />

[dasfaker]

There is a problem with modulators that send sysex.

All of them send F0 00 F7 instead of the message assigned to each one. Selecting None and later Sysex as Midi Message Type solves the problem, but after saving and opening the panel this happens again.

This is related to an old bug that send this F0 00 F7 if you have a sysex formula that ends with f7 and not F7, even if you have a CC or another Midi Message Type.

Also the global variables are not working for me. I have a uiCombo that select a global variable but the global variable is always the first value of the uiCombo.

[dasfaker]

The virus works in two ways. With VirusControl, the access panel, it works like a vst thru usb. In this mode, the normal midi ports are disabled and all clock stuff is done by VirusControl. This is were a lot of people are having troubles with syncro and latency.

The other way to use the Virus is like a normal midi synth, with the classical midi ports. In this case you can’t use VirusControl, so there is no editor for the Virus if you want to use in this way.

Another problem with VirusControl is that not all the parameters have automation, the only way to access them is thru sysex, and again this must be done without VirusControl. With VirusControl you can’t change programs or banks with program change messages, so you can’t automate this. Having the Snow only four parts, this is a must.

Even more, I use Ableton and it doesn’t accept sysex messages even with Max4Live, so Ctrlr was the only solution to those problems. If you want to use the Virus live, without latency and with good syncro, you can’t use VirusControl. The only thing I will miss from VC are the multiple usb outs.

[dasfaker]

My fault. I did it before you told me tree times, but somehow I forgot to save the panel before reopen it

[dasfaker]

Fantastic, I’ll try this afternoon.

On a quick test, it seems that the script selected in "Called when the panel has finished loading" is not working any more on my panel.

[dasfaker]

Thank you. In fact I work in a related job, and I have been using Photoshop since version 3, many years ago.

I wish I was as prolific as you making panels, I have several synths here awaiting…

[dasfaker]

Yes, the example above was a real example;

"F0 00 20 33 01 00 71 00 [/color:1c5tanak]0a xx F7" is a message from the Virus. The number in red is the midi channel.

"F0 00 20 33 01 00 71 k0 [/color:1c5tanak]0a xx F7" is the formula of a knob with a global variable. No matter what value has the variable, the above message never moves a knob.

[dasfaker]

Cool, thank you.

[dasfaker]

Thx. I’ve used Photoshop for the design and Knobman for the knobs and sliders

[dasfaker]

The delete button gives a login error, but uploading worked fine. Thx

[Author]

Posts