I have managed to create something that takes a sample and can play it forwards or backwards, can loop forwards or backwards, and can change the speed.....

What I am wanting to do now is be able to record incoming audio and manipulate it this way. In other words, how do I create an SK-1 style sampler where I can hit a key and it will record the audio coming into the audio input, and then take that same little clip of audio and mess with it. As it is now I load samples in using soundfiler.

I guess I'm kinda trying to make that sample loopy scratchy time-stretch thing on Kaoss pads, and all I need now is to know how to grab little sampes of incoming audio.

Any ideas? Thanks.

That would be rather strange i guess. I've been recording a lot of impro sessions during which i write 5 simultaneous stereo files (using 5 [writesf~] objects) on different computers/usb drives, never had any trouble with it.

Yeah, I've recorded 45 minutes straight a few times using [writesf~], and my hard drive still works. Which is good, because I'm a lazy bastard when it comes to backing up.

Well, this is my 2nd hard drive replacement on my macbook (which I've only had since August of 2006) so I don't know. Maybe I'm letting it get too hot, or maybe I rattled it loose by moving it too much while it is powered on. Who knows?

You know, most people I know who've dealt with MacBook hard drive failures (which is quite a few as my school requires students to have MacBook Pros) have had them die within a year or two, so they may just not have a great lifespan.

hmm...

...I should go back my stuff up...

You know, most people I know who've dealt with MacBook hard drive failures (which is quite a few as my school requires students to have MacBook Pros) have had them die within a year or two, so they may just not have a great lifespan.

Of the two people i know that have macbooks bought about 2 years ago, their hard drives have failed and been replaced. I remember the iBooks had cracked logic boards a few years back and loads had to be recalled. I heard that Apple trying to source cheap labour and parts. Things like too much thermal paste on the cpu leading to overheating and causeing all sorts of problems.

Touch wood my first generation 17" powerbook is still trundling along nicely, albeit slowly!

any how i digress.....

OK.... so back to my original question. Unfortunately I had everything all figured out and everything was working exactly how I wanted, until my hard drive broke and I lost it. (I didn't lose everything, just the part about recording audio into my scratchy sampler)

Anyway, I figured it'd be easy to redo it again, but I can't get it. So how exactly do I get from writesf~ to loading the recorded file into a table? I know that's how I had it set up, and I'm totally stumped. I need to get from audio coming into writesf~ and then read it out of a table.

Yet another hard lesson learned: always back your stuff up!!!

P.S. - I have been looking at the help files (which is how I figured it out the first time) but I'm just stuck. Maybe once I figure something out, the knowlege I needed to do it flies out of my head because I don't think I need it anymore. I feel dumb.

UPDATE!!!!! Nevermind. Just figured it out again. And saved it. And backed it up. And emailed it to myself.

So you're recording the sample onto your harddrive with a writesf~ and then loading it to a table?

Wouldn't it be easier to record the sample directly to the array?

My (limited) understanding was that if I wanted to be able to start and stop recording on the fly and then loop the recorded sample, I'd have to use writesf~ but yeah, if it's possible to do it directly to an array (of a non-predetermined length) then that probably would be better.

The whole issue I think is that I'm not starting out with a specific length of time for the sample being recorded. I'm just pressing a key to start and then pressing another key to stop.

Any suggestions on doing it better/more efficiently?

ah yes, when you load the recorded sample onto the array it resizes the array to its size allowing you to record samples at arbitrary lengths. If it works it works. The only possible problem would be BLOCK IO while loading the array, but hat would only happen on low-end machines and with large sample sizes.

If you do find that you're getting a BLOCK IO stutters you can try my RAMFS suggestion.