[music-dsp] my own projects

[Joshua Scholar]

The program is sitting in a zip file at
http://www.nightstudies.net/SoundWorkbench/
If you point the text in SoundWorkBenchIni.txt at the plugin directory for
winamp 2 or winamp 5 then it can play
wave files.

I haven't extricated the source from some other projects, but I'm planning
on making the source available too.

I'm all upset that its throwing an exception on shut down in some place that
the debugger can't debug, but the debug version doesn't have that problem
and BoundsChecker can't find any problem either.


Josh
----- Original Message ----- 
From: "Aristotel Digenis" <digenis at digenis.co.uk>
To: "music-dsp" <music-dsp at ceait.calarts.edu>
Sent: Wednesday, February 16, 2005 4:33 PM
Subject: Re: [music-dsp] my own projects


> Screenshots would indeed be great. 8-)
>
> Aristotel
>
> Brian Willoughby wrote:
>
> >[  Hey you'all, I threw together a wave visualization program a week
ago...
> >[  It's very pretty - I plot the peak to peak at 16 times the resolution
of the
> >[  screen, with the brightness cumulative and the channels overlaid
(right in
> >[  red and left in green), with and there's a brightness control knob.
Anyway
> >[  the results look like an ocilliscope - it's surprisingly revealing to
plot
> >[  the waveform at a higher resolution than the pixel width.
> >
> >Sounds like an interesting visualization technique.
> >
> >The Mac OS X graphics model, based on PDF, allows for fractional pixel
> >coordinates.  If you set the step to .0625 (1/16th) pixel and draw line
> >segments connecting each audio sample at that stepping, the graphics
display
> >system with automatically anti-alias the resulting waveform.  This is
also
> >rather beautiful, but rather straightforward in that it looks almost
exactly
> >like a future monitor with more pixel resolution might appear (although
> >softer).
> >
> >Your algorithm is a little unique.  Is there any height information in
your
> >plotting?  You describe combining 16 samples into one pixel width using
> >brightness, but is your display one pixel tall or do you assign vertical
> >position to the PCM value?  Screen shots might help.
> >
> >I think the difference between the AppKit visualization and yours is that
the
> >anti-aliasing would hint at the relative positions of the 16 samples,
while
> >your algorithm aligns 16 samples directly on top of each other and then
the
> >next 16 samples are stacked, and so on...
> >
> >Brian
> >--
> >dupswapdrop -- the music-dsp mailing list and website:
> >subscription info, FAQ, source code archive, list archive, book reviews,
dsp links
> >http://shoko.calarts.edu/musicdsp
> >http://ceait.calarts.edu/mailman/listinfo/music-dsp
> >
> >
> >
> >
>
> --
> dupswapdrop -- the music-dsp mailing list and website:
> subscription info, FAQ, source code archive, list archive, book reviews,
dsp links
> http://shoko.calarts.edu/musicdsp
> http://ceait.calarts.edu/mailman/listinfo/music-dsp