Augustus Looper -teething problems and OSC

[pinki]

I must echo something I read elsewhere here in this forum about the manual- there is a crucial piece of information missing (maybe it's there -please tell me where!). You have to set the maximum delay time to a figure greater than the loop time you will be using in bars and beats. I was TOTALLY lost before I read Scott Righteous' post here called "Basic Augustus Loop set up:http://www.kvraudio.com/forum/viewtopic ... us#4233316
(btw -why does AL not have the time in seconds update to the necessary buffer time when one sets the number of desired beats?)

I really really think the manual needs a section on how to do basic looping as explained in your reply os.


Anyhow lovin the plug!

Question- I want to use my Lemur to control Augustus- is there a simple way to get each element to reveal its OSC address within the plugin?

Thanks.

[os]

Changing the buffer size is a costly operation that can't be guaranteed to work without major audio stutters, so AL never does it automatically.

AL's controls/parameters don't have separate OSC paths. You use the '/setParameter' path followed by the param id, as explained in the manual.

[pinki]

So I'm using

setParameter(Pitch)

on a fader in Lemur but its not working. Lemur does not allow:

setParameter("Pitch")

and so I tried

setParameter(paramID_Pitch, 12.0 )

and not working either

[os]

That's Lua code - you're looking at the wrong part of the manual. Look in the section entitled "OSC Control". The OSC message you want is probably "/set".

[pinki]

Thanks os- I'm still not there though:

/set

I see this in the manual:
/set i:param f:value

but if I enter that in Lemur, as for example:
/set i:Pitch f:x
where x is my variable in Lemur, nothing happens and in fact Lemur does not accept that format. So I tried this:
/set/i:Pitch/f:x
but nothing.

Surely someone has tried using a Lemur with AL before. Please help!

[os]

i:param means an integer parameter id, e.g. 1, 2, 3, 4 etc.
f:value means a floating point value

so e.g.

/set 42 0.6

[pinki]

OK this is beyond me- do I have to find the Parameter ID by using getParameterID ?

Has anyone used a Lemur with AL?

If I put /set 42 0.6 as an address for the x value of a fader in Lemur it makes it into /set420.6 when I leave the text field.

[os]

If you can send me the Lemur user manual maybe I could figure it out for you.