Hi All,
I was wondering how people are dealing with avoiding quantisation on sine(or any) LUTs at very low frequencies (typically under 1hz). Is it better to switch to an algo or make 2 tables or can you interpolate and smooth the curves?
I mean you can get a nice effect with the stepping but its obviously not ideal.
/0
p.s. sorry 4 cross post http://www.nullpointer.co.uk http://www.dividebyzero.org ________________________________________________________ C:\AUTOEXEC.BAT C:\REM [Header] C:> C:>PATH=C:\PERL\BIN;C:\WINDOWS\COMMAND;\C:jdk1.2.2\bin ________________________________________________________
(all suffixes enabled)
-----Original Message----- From: Miller Puckette mpuckett@man104-1.ucsd.edu To: Norbert Math math@iem.kug.ac.at Cc: pd-list@iem.kug.ac.at pd-list@iem.kug.ac.at Date: 27 July 2001 22:07 Subject: Re: [PD] unique names for externals
This is going to be a never-ending problem...! suppose someone uses lib 1 and lib 2, and has a patch using "wack" from lib 2, and then the lib 1 author introduces a "wack" object. The only way I can think of to protect against this problem is to somehow declare to Pd that, in the context of a given patch, "wack" should be taken from lib 2. Hmm, then someone merges lib2 and lib 3, so the declaration then has to change... I have no idea how to deal with this in general..
cheers MIller
On Thu, Jul 19, 2001 at 05:51:50PM +0200, Norbert Math wrote:
hello hackers,
shall we introduce a mechanism that guarantees unique object names across the published pd libraries? the problem: for example, both zexy and gem have an external called "abs~". i guess you cannot tell which one gets loaded after you had loaded both libraries.
at the pure database, http://iem.kug.ac.at/pdb/ i made a list of all existing externals and pd objects - you can look there when making an external if its name is free. (and, while you are there, please check the entries of your objects - there is a good chance that some are outdated or even missing)
would it be good to have a kind of registration mechanism? eg. a possibility to registrate names (or fractions of names) on the database?
norbert
nullpointer hat gesagt: // nullpointer wrote:
I was wondering how people are dealing with avoiding quantisation on sine(or any) LUTs at very low frequencies (typically under 1hz). Is it better to switch to an algo or make 2 tables or can you interpolate and smooth the curves?
On a sine curve I wouldn't use a table lookup, but instead osc~ or cos~ directly. Modern CPUs can compute sin() so fast, you don't need to look up the values in tables the way old Csound still does...
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ / / __ \ ___\
/ / / ____/ / / / // ____// /\ \ ___\____ \
/_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\