UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!

[Sampleconstruct]

4 fresh Falcons - an arp/bass sequencer meets granulated e-bow phrases/drones meets lush vocal pad meets dopplerized hand cymbals:

https://soundcloud.com/sampleconstruct/ ... falcon-air

[otristan]

@RobKastler

Custom mapping with the script is not mandatory and only required if you want to do
more fancy stuff than the prebound ones

I would advise you to first try the preset inside this zip file
http://we.tl/K7s6z92toG

See if this works with a basic preset already.

Thanks,

[wagtunes]

Well, I am totally addicted to this synth which has become my all time favorite. Kudos to the developers. It takes a lot to wow me these days.

I want to start getting into scripting but don't know where to begin as it's something I've never done before. Is there a tutorial somewhere? Is there an example script that I can look at so I can see how they're designed? Just something to get me off the ground running. I'll do the rest. I'm a former computer programmer so I think I can handle it. Just need to know where to start in learning.

Thanks.

[EvilDragon]

http://www.uvi.net/uviscript/


Uses Lua, so you might as well go ahead and have a book/class on Lua.

[wagtunes]

http://www.uvi.net/uviscript/


Uses Lua, so you might as well go ahead and have a book/class on Lua.

Thanks. I took a look at one of the stock scripts that came with the VST and it kind of looks like A combination of FORTRAN, BASIC AND C++. At least it isn't RPG II.

Might take me a while to actually learn this thing. It doesn't appear to be very modular. If there are sub routines in this thing I'm hard pressed to find them. Looks more like spaghetti code which is very messy.

Oh well, something new to keep me busy.

[EvilDragon]

If by sub-routines you mean functions, yeah, Lua has that.

[wagtunes]

If by sub-routines you mean functions, yeah, Lua has that.

Used interchangeably but sub routines, for the most part, are very long sections of code that perform a number of tasks that are then inserted into the main module to keep the code clean and easy to read whereas functions are usually mathematical formulas of some kind that are traditionally much shorter in length. Also, functions usually do not have some kind of call statement but are just referenced by the function name itself where parameters are passed to it.

For Example:

CALL SUBROUTINE (GETSTUFF X,Y,Z)
FUNCTION DOMATH(X,Y,Z)

or just

CALL SUBROUTINE (GETSTUFF X,Y,Z)
DOMATH (X,Y,Z)

depending on the language.

They are technically different though some people lump them altogether.

Obviously, there are always exceptions as all languages are different but every language I've ever worked on (mostly various versions of BASIC) clearly differentiate between the two.

From the code I've looked at so far, there does appear to be functions of some kind, though I don't understand what they do as of yet, but there doesn't appear to be anything remotely resembling a subroutine, which of course would then require a separate module that actually contains the subroutine, though there are some languages where you can embed the subroutine in the main code as long as you have a header above it.

I prefer the separate module approach because that way if you have to make a change and you have 100 programs using that sub routine, you only make the change once and then simply recompile the 100 programs instead of having to change the code in 100 programs and then recompile.

Of course then there is the simplicity factor. LUA scripts, for the purposes of what we're doing here, may be so simple that subroutines just don't make sense. Of course if that's the case, then spaghetti code is something that pretty much can't be avoided, which is why I don't normally like to program in things like this. Too messy for me.

[EvilDragon]

Ah, you mean like includes in C. Yeah, Lua can do that ("reqire" keyword).

http://www.lua.org/manual/5.2/manual.html#6.3


But I think for the most part you won't need this in Falcon. Only if you want to create a bigger sample library you might want to have some modularity (or if you plan on having a series of products that share a lot of the code)... but just for simple UI stuff you don't really need this.

[wagtunes]

Ah, you mean like includes in C. Yeah, Lua can do that ("reqire" keyword).

http://www.lua.org/manual/5.2/manual.html#6.3


But I think for the most part you won't need this in Falcon. Only if you want to create a bigger sample library you might want to have some modularity (or if you plan on having a series of products that share a lot of the code)... but just for simple UI stuff you don't really need this.

Which is what I'm seeing, which is why this looks like spaghetti code. LOL.

I'll read through the reference manual to learn what all the math stuffs do and then I'll kind of have a handle on it. Figuring out how it handles logic (what stuff has to come first, last, etc) is going to be the hard part as if you do things out of order you tend to just FSU.

[EvilDragon]

I think for the most part (if not completely) it follows the way C/C++ orders operators, since Lua is actually written in C...

But, it's all on the Lua homepage. http://www.lua.org/pil/3.2.html

[whyterabbyt]

Ah, you mean like includes in C

No, like in he has no proper education in CS or any modern programming language, and is adhering to arbitrary distinctions he picked up from badly-designed languages in the 70s.

[whyterabbyt]

They are technically different though some people lump them altogether.

No. Technically (within a compiler or interpreter) they are the same thing, though some people who dont actually understand the technicality may make an arbitrary distinction between them.

And modern languages do not use 'call statements'. Because functions dont need unnecessary syntactic sugar to work.

[wagtunes]

Ah, you mean like includes in C

No, like in he has no proper education in CS or any modern programming language, and is adhering to arbitrary distinctions he picked up from badly-designed languages in the 70s.

Know what? It's all we had back then so forgive me for being old.

[whyterabbyt]

Ah, you mean like includes in C

No, like in he has no proper education in CS or any modern programming language, and is adhering to arbitrary distinctions he picked up from badly-designed languages in the 70s.

Know what? It's all we had back then so forgive me for being old.

Im well aware of what we had back then, thanks.

[streifentier]

They are technically different though some people lump them altogether.

No. Technically (within a compiler or interpreter) they are the same thing, though some people who dont actually understand the technicality may make an arbitrary distinction between them.

And modern languages do not use 'call statements'. Because functions dont need unnecessary syntactic sugar to work.

Well, I think that whyterabbyt is (apart from probably not making the greatest effort to put it into kind words) quite right. Generally there´s no limit as to what code you can put into a "function", so whatever you might want to put into a "subroutine" can be handled by functions. No italian noodles needed.