<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Harry Van Haaren wrote:
<blockquote
cite="mid:r2p58ef89e41004261241g8e3bc6a6ue4d3db5daae518fd@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type"
content="text/html; charset=ISO-8859-1">
Here's my impression of a Granulizer:<br>
<br>
Chops a piece of audio up into many little "granules" (segments),
ususally<br>
each granule is smaller than 20ms in duration, and then reorganizes
these granules to<br>
form new sounds. There is a method of synthesis based around this
approach.<br>
</blockquote>
In practice grains can be up to 100ms. <br>
Some of the parameters of granulation:<br>
- grain length (1 -100ms, but this )<br>
- grain envelope (the envelope of each single grain, e.g. triangle,
trapezoid, gaussian etc.)<br>
- grain density (can be measured or described in different ways but
it's the number of grains played in a certain amount of time, the more
the grains the 'denser' the sound)<br>
etc.<br>
<br>
There are many granular tools out there for linux. I made a
'minimalistic' one with Pd if anyone were interesterd<br>
<br>
Best,<br>
Lorenzo<br>
<br>
<blockquote
cite="mid:r2p58ef89e41004261241g8e3bc6a6ue4d3db5daae518fd@mail.gmail.com"
type="cite"><br>
-Harry<br>
<br>
<br>
<div>2010/4/26 Louigi Verona <span><<a moz-do-not-send="true"
href="mailto:louigi.verona@gmail.com">louigi.verona@gmail.com</a>></span><br>
<blockquote>Jorn! Thanks, very informative answer.<br>
<br>
What can you say about stuff like this:<br>
<br>
1. vocoder<br>
2. grnulizer<br>
3. slicer (when a file is sliced into pieces)<br>
4. beat matching<br>
<br>
L.V.<br>
<br>
<div>
<div>2010/4/26 Jörn Nettingsmeier <span><<a
moz-do-not-send="true" href="mailto:nettings@folkwang-hochschule.de">nettings@folkwang-hochschule.de</a>></span><br>
</div>
<blockquote>
<div>
<div>On 04/26/2010 08:47 AM, Louigi Verona wrote:
<div>
<div><br>
> Hey guys!<br>
><br>
> I was wondering about the following.<br>
> On Windows we have lots and lots of plugins and synthesizers and
effect<br>
> racks. On Linux the selection is much less variable.<br>
><br>
> However, am I correct in understanding that the variety of the
Windows<br>
> synths and plugins merely means that people take several core
modules and<br>
> just rearrange them into different GUIs?<br>
> Am I correct in understanding that there are only several major
algorithms<br>
> for things like filters, delays, reverbs and choruses?<br>
<br>
</div>
</div>
</div>
</div>
<div>
<div>in my view, the situation is mixed. there is a lot of utter
bullshit<br>
going on, eqs and "mastering" compressors seem to have the greatest<br>
voodoo factor. then some people sell you simple convolvers as<br>
oh-so-great emulators of vintage stuff... i think it's justified to say<br>
that these basic building blocks are widely understood, with little room<br>
for ground-breaking improvements.<br>
<br>
it's either in great user interfaces or cutting-edge (and patented)<br>
technology that proprietary stuff kicks our collective asses (which is<br>
fine in my book).<br>
<br>
there are many truly revolutionary algorithms and interface designs that<br>
have no free software equivalent, nor will they for the forseeable<br>
future. stuff like ableton live or the waves reverbs come to mind, or<br>
(gasp!) melodyne. or advanced restauration tools like really good<br>
denoises and declickers. then there's adaptive convolvers that can<br>
tackle non-linear stuff (like the "liquid" gear marketed by focusrite) -<br>
no ready-to-use free equivalents exist for this. whether you need it or<br>
not is another question. as it stands now, we can't emulate an UREI, the<br>
closed source folks can. but sampo s. is hot on their tracks :)<br>
<br>
the audio fundamentals (controlling spectrum, delay, frequency response,<br>
and space), i.e. the basic things you mentioned that you need to get a<br>
mix done, is all there, in varying degrees of usability and slickness,<br>
and i have never looked back.<br>
<br>
then again, i'm not tied into a workflow that needs maximum efficiency.<br>
stuff like protools does have its uses - it's hard to envision an<br>
environment where a seasoned engineer could be faster and more<br>
productive. but often, all that you get for your money is a fake brushed<br>
aluminum widget with huge, wasteful and incorrectly modelled VU meters<br>
and fake rack ears... caveat emptor.<br>
<br>
but in all fairness, open source is covering ground in this area, too.
:-D<br>
<br>
best,<br>
<br>
jörn<br>
<br>
<br>
<br>
_______________________________________________<br>
Linux-audio-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Linux-audio-dev@lists.linuxaudio.org">Linux-audio-dev@lists.linuxaudio.org</a><br>
<a moz-do-not-send="true"
href="http://lists.linuxaudio.org/listinfo/linux-audio-dev">http://lists.linuxaudio.org/listinfo/linux-audio-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br>
_______________________________________________<br>
Linux-audio-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:Linux-audio-dev@lists.linuxaudio.org">Linux-audio-dev@lists.linuxaudio.org</a><br>
<a moz-do-not-send="true"
href="http://lists.linuxaudio.org/listinfo/linux-audio-dev">http://lists.linuxaudio.org/listinfo/linux-audio-dev</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Linux-audio-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Linux-audio-dev@lists.linuxaudio.org">Linux-audio-dev@lists.linuxaudio.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxaudio.org/listinfo/linux-audio-dev">http://lists.linuxaudio.org/listinfo/linux-audio-dev</a>
</pre>
</blockquote>
</body>
</html>