Techlab Log
Adam Lederer

Project: Audio Timestretching
Approach: TBA (will be transient-based)

Technologies used:
JUCE (http://www.rawmaterialsoftware.com/juce/)
Linux
Windows
Microsoft Visual C++ Express Beta 3
gcc
Transient detection
FFT

Log:

9/26/2005
Created Log, Considered options and methodology for audio timestretching algorithms

9/27/2005
Worked more with JUCE toolkit (already deciphered, in earlier times), seeing if
I can figure out how to get it to run correctly on Linux (the demo program)

9/29/2005
Continued to try to get JUCE working - solved some problems, contacted developer

10/3/2005
Still struggling with JUCE, also waiting for Sys people to get the system up 
and running sound-wise

Oct 6: Working with JUCE - Jule's Utility Class Extensions - C++ API for 
 sound.
   Also needs Xinerama for multiple monitors. 

Oct. 13 - absent

Oct. 17 - found Melodyne, time stretching package, I think this is the site?
  Proposal still seems to be just logs?

Oct. 18 - Time stretching - can we achieve better response/quality than something
like Transkriber, like when you drop the tempo by 50%, the quality suffers.
  We'll try CSound for audio editing features?  We have CSound on this image.

Oct. 27 - using JUCE, download TimeStretch - the executable file.
 This loads up a JUCE window in Linux - this is a Windows program he's making runnable in Linux.

Nov. 1 - Working on his research paper draft for 1st quarter.

Nov. 3 - Proposal The development of a Transient-based Audio Timestretching algorithm

also see prototypes

Dec. 15 Current Status Update
	When possible, I am working my way through the JUCE tutorial, but I'm 
	catching up with the lab requirements (bibliography, etc. etc.).  The 
	tutorial isn't really very good, so I have a lot of experimentation to 
	do to get my head around it, and I'm having to do a lot of debugging to 
	get it working on Linux (disabling certain features, etc.), but so far 
	JUCE is looking like it was a better and better choice.  Still 
	searching around to see if the audio functions are tutorialized anywhere
	- if not, I will just look at the documentation myself.