KVR Audio

AdmiralQuality · Post by **AdmiralQuality** » Sun May 14, 2006 9:18 pm

I just noticed. Amoebe's knobs use 300 degree knob travel, just like in real life!

(Most VSTs use the 270 degree default from VSTGUI)

Oh wait... you've still got 270 degree mouse control.

Call this after you create your controls...

Code: Select all

cYourAnimKnob->setRangeAngle(- k2PI * 300.0f / 360.0f);
cYourAnimKnob->setStartAngle(k2PI * 240 / 360.0f);  // (doublecheck this one, but thats where you set the start angle)

...and the motion will better match the mouse.

(Don't feel too bad if you missed these. I only stumbled across them when I was already half way into writing my own.

)

pj geerlings · Post by **pj geerlings** » Sun May 14, 2006 10:08 pm

AdmiralQuality wrote:I just noticed. Amoebe's knobs use 300 degree knob travel, just like in real life!

(Most VSTs use the 270 degree default from VSTGUI)

Oh wait... you've still got 270 degree mouse control. Call this after you create your controls...
Code: Select all
cYourAnimKnob->setRangeAngle(- k2PI * 300.0f / 360.0f);
cYourAnimKnob->setStartAngle(k2PI * 240 / 360.0f);  // (doublecheck this one, but thats where you set the start angle)
...and the motion will better match the mouse.

(Don't feel too bad if you missed these. I only stumbled across them when I was already half way into writing my own. )

Thanks for the find and potential fix - I am really unsure about making them counter-clockwise knobs - aren't they clockwise knobs?

please let me know!

thanks again,
pj

AdmiralQuality · Post by **AdmiralQuality** » Sun May 14, 2006 10:16 pm

Nothing to do with counterclockwise. (There a func for that too! With the typically misleading name of ->setInverseBitmap() )

That's just the way the numbers work out. Your default range is already -270 degrees. See...

from CKnob::CKnob in vstcontrols.cpp...

Code: Select all


setStartAngle ((float)(5.f * kPI / 4.f));
setRangeAngle ((float)(-3.f * kPI / 2.f));

It's all upside down and backwards, if you ask me. But it's arbitrary so I can't really complain. Whoever wrote VSTGUI is smoking some stronger shit than I am though.

pj geerlings · Post by **pj geerlings** » Sun May 14, 2006 10:21 pm

AdmiralQuality wrote:Nothing to do with counterclockwise. (There a func for that too! With the typically misleading name of ->setInverseBitmap() )

That's just the way the numbers work out. Your default range is already -270 degrees. See...

from CKnob::CKnob in vstcontrols.cpp...
Code: Select all
setStartAngle ((float)(5.f * kPI / 4.f));
setRangeAngle ((float)(-3.f * kPI / 2.f));
It's all upside down and backwards, if you ask me. But it's arbitrary so I can't really complain. Whoever wrote VSTGUI is smoking some stronger shit than I am though.

Yes, I tried without the "-" sign and it was wacky - thanks again!!

A new version ( 0.9.2 ) is done ...

Right-click here/Save Target As ...

regards,
pj

egbert · Post by **egbert** » Mon May 15, 2006 2:08 am

Kirk: Here's the new model phaser - check it out!

[Spock examines interface, makes a test firing or two]

Spock: Why Captain ... I can't believe my ears!
Kirk: I can't believe your ears either Mr Spock.

(Boom Boom)

egbert · Post by **egbert** » Mon May 15, 2006 2:22 am

Hi PJ - I am getting some crackling when I adjust GUI parameters on NxtPhase with the latest Beta - I haven't noticed this before but it may have been there.

AdmiralQuality · Post by **AdmiralQuality** » Mon May 15, 2006 2:23 am

Awesome PJ! Maybe we can start a trend to get 300 degree knobs in all VSTs!

[Edit: Oh and WTG Amoebe too! Why did you choose 300 degrees by the way? Did you reference a real knob?

Great work!

Edit2: I just realized your sig starts with a Star Fleet insignia for the "A"! Har!
]

Morgaxx · Post by **Morgaxx** » Mon May 15, 2006 2:31 am

egbert wrote:Kirk: Here's the new model phaser - check it out!

[Spock examines interface, makes a test firing or two]

Spock: Why Captain ... I can't believe my ears!
Kirk: I can't believe your ears either Mr Spock.

(Boom Boom)

Classic...

Nice effect.

shamann · Post by **shamann** » Mon May 15, 2006 2:57 am

I've come across odd behaviour in the latest version. If I delete the input from the phaser, I get a big old blast of white noise. Strangely only happens in Audiomulch, tried in eXT and Bidule but nothing happened. Maybe it's a problem with Mulch, but I've never had this happen before.

pj geerlings · Post by **pj geerlings** » Mon May 15, 2006 5:17 am

egbert wrote:Hi PJ - I am getting some crackling when I adjust GUI parameters on NxtPhase with the latest Beta - I haven't noticed this before but it may have been there.

None of the parameters have zipper-noise elimination at this time - it is still beta - and I bet there will be a few changes before we get to 1.0.0

peace,
pj

pj geerlings · Post by **pj geerlings** » Mon May 15, 2006 5:20 am

AdmiralQuality wrote:Awesome PJ! Maybe we can start a trend to get 300 degree knobs in all VSTs!

[Edit: Oh and WTG Amoebe too! Why did you choose 300 degrees by the way? Did you reference a real knob?

Great work!

Edit2: I just realized your sig starts with a Star Fleet insignia for the "A"! Har!
]

It all started when I wanted a larger number of steps in a knob control - insteat of 63, I wanted 101 ( 0% to 100% ) and the result was the current knob stepping and sweep.

pj geerlings · Post by **pj geerlings** » Mon May 15, 2006 5:23 am

shamann wrote:I've come across odd behaviour in the latest version. If I delete the input from the phaser, I get a big old blast of white noise. Strangely only happens in Audiomulch, tried in eXT and Bidule but nothing happened. Maybe it's a problem with Mulch, but I've never had this happen before.

It might be a larger buffer size in Audiomulch - not really sure - right now there are a number of areas that could be improved. It is still a work in progress.

Looks like I better start a "NxtPhase ToDo" list

peace,
pj

DotNoir · Post by **DotNoir** » Mon May 15, 2006 6:53 am

Wow, for some reason I've missed the GUI. That's beautiful! Great work amoebe and pj for the plug. Really love your work, both of you that is.

amoebe · Post by **amoebe** » Mon May 15, 2006 9:47 am

It all started when I wanted a larger number of steps in a knob control - insteat of 63, I wanted 101 ( 0% to 100% ) and the result was the current knob stepping and sweep.

It all started when I decided to improve my scripting files to accept user input. Before that the angles and # frames were hardcoded. Then I thought it a waste to only use 270 degrees where almost 360 were possible.

I didn't know the software needed to be adapted for it, though. I thought the animation would handle that.

AdmiralQuality · Post by **AdmiralQuality** » Mon May 15, 2006 1:24 pm

amoebe wrote:
It all started when I wanted a larger number of steps in a knob control - insteat of 63, I wanted 101 ( 0% to 100% ) and the result was the current knob stepping and sweep.
It all started when I decided to improve my scripting files to accept user input. Before that the angles and # frames were hardcoded. Then I thought it a waste to only use 270 degrees where almost 360 were possible.

I didn't know the software needed to be adapted for it, though. I thought the animation would handle that.

In circular mouse mode the VSTGUI code defaults to 270 degrees (and most GUIs use it). Its not very well documented that there's a function for changing the "range angle". Like I told PJ, I just stumbled across it myself the other day when I was working on coding my own. I've been VSTGUIing for 7 months without knowing it was there. All my plugs will have 300 degree knobs in the future!

(In linear mouse mode it doesn't matter of course. The movement doesn't match the angle to the mouse pointer in any way.)

And yes, the animation defines the limits of where you SEE it go, but you'll notice in the previous version that it starts to get ahead of the mouse's angle towards the ends as the code assumes it stops at 270 degrees and your animation is 300 (which is what they SHOULD be as that's what most every real world pot I've tested does!)

(This should be in the dev board. Oh well.)

Anyway, simple matter to tweak now that we know there's a function for it.

So keep making 300 degree knobs, and show those two lines of code to any developers using your knobs with VSTGUI. Again, works fine without it, but it's nicer to have the knob point at the mouse exactly. Also it's that much more room to move, providing a slightly finer resolution of control. You're right, they could go almost all the way around (actually, for Poly-Ana, I'm working on ones that DO go all the way around. Fun! Detents too! And a circular-relative mode that doesn't jump when you first click on it, only after you start a drag. That's how I stumbled on the existing rangeangle and startangle functions, was about to add my own when I realized they were already in there.)

Awesome stuff guys. I spent an hour last night playing clav through it. I'm gonna start a reggae band now...

NxtPhase - with a classic GUI from amoebe