On 21.12.15 03:48 , Bjorn Roche wrote:
> Generally speaking, a program like ProTools (the "host app") will open a
> plugin, and ask for a list of parameters. The plugin will respond with
> something like "These are my parameters and they have the following
> basic properties (id, display name, min,
On 06/09/15 06:59, Ross Bencina wrote:
Personally, I think AudioSampleBuffer is (a) trying to do too much
(there should be two objects: a Buffer and a BufferRef); and (b) it's
abstraction overkill for the plug-in use-case.
Speaking of the plug-in use-case. One thing that I really dislike about
On 12.04.15 02:26 , robert bristow-johnson wrote:
> i was wondering about that (20,000 sounded awful large). i thought they
> might have meant *all* of the system and utility code that was called to
> do it.
I guess the number 20,000 is also a way to impress one's boss, the
marketing department
On 10/16/2014 09:22 AM, Peter S wrote:
entropy = 0
state = b(1)
for i = 2 to N
if state != b(i) then
entropy = entropy + 1
end if
state = b(i)
end for
But that's not additive is it? For a sequence of length one the
algorithm always yields entropy = 0. But for a sequence of
On 13.01.14 09:46, Frank Sheeran wrote:
> At this point, the #1 goal is to evaluate the language itself. Is a
> functional, textual, programming language the best way to design a
> patch? Better than Csound, better than visual environments like Buzz
> or Cycling '74's Max? Can I write a patch in
On 29.11.13 09:35, Tim Goetze wrote:
> Harmonics in electric guitar signals tend to roll off quite fast
> though. There's usually not much high-frequency spectral content to
> worry about, relaxing this requirement greatly in practice.
BTW, for those who can read some German, this book
https://h
On 28.11.13 19:30, Nigel Redmon wrote:
> 2) There isn't a specific minimum requirement, so this isn't really an issue.
> That is, the more cpu you have, the more and better you can oversample, but
> you do what you need and what you can get away with. (You could go nuts and
> think that, well, t
On 04.10.13 11:45, David Reaves wrote:
> I have two books which I have found to be indispensable, "Digital Audio
> Signal Processing" by Udo Zölzer, and "DAFX: Digital Audio Effects" edited by
> Zölzer, with numerous authors.
>
> They're my 'go-to' books when I need background and ideas on the s
On 01.05.13 22:35, Sampo Syreeni wrote:
> So, how do you go about systematically and portably implementing what
> you would expect from your logical operations, using standard C
> operations, without knowing the basic width of your types? (Logical, not
> arithmetic) right shifts of signed quanti
On 19.06.12 19:32, Al Clark wrote:
> Is there a good book(s) that specifically addresses programming audio on
> Windows and or Apple OS X?
>
> I am looking for something better the various Visual Studio documents.
>
> From my perspective, I care about XP and newer, and soon Apple OS X
It's not a
On 26.02.12 16:46, Theo Verelst wrote:
Of course most all computer languages have serious limitations, too:
none allow explicit parallel programming concepts, "native" associative
behaviour, and even simple mathematical reasoning takes a heavy LISP
program to begin with (Like Maxima), and a lot o
On 1/11/12 9:39 , Didier Dambrin wrote:
> How is wikipedia a bad idea? Only because it has mistakes? Sure, but
> it's still a lot more reliable than any other source on the net. All
> encyclopedias can have mistake & any information has to be verified anyway.
> What else would replace it? Certainl
On 2/8/11 15:39 , Miles Egan wrote:
I'd suggest you seriously consider rolling your own. It's not *that*
hard to build a simple audio graph system and you won't be tied to a
alien system with design priorities likely quite different than your
own. Interfacing with a big, complex, multi-platform a
13 matches
Mail list logo
