**Hi guys! **

This is my first serious object created with Pd. I'm taking a puredata class at my University and my professor asked us to make a looper object to play soundfiles and toy around with them. So I've dropboxed my first beta version here:

AudioLooper~ :
https://www.dropbox.com/sh/l9npip5k70y3sbj/AAB4vSIuCfiXnUOGBdax0PdCa?dl=0

I have to give the homework in on monday the 03rd of November, but I'll be getting feedback from my professor and we'll keep working on it for the semester.
If you'd like to pitch in suggestions or modifications, i'm super open to that. I'd like to optimize the object and share it with everyone.

Here's a screenshot of my -help.pd for a quick overview.
Screen shot 2014-11-01 at 2.31.30 PM.png

I have a feeling it may be using a little too much cpu (averaging 19% of my '09 macbook pro), but it does have a lot of features, maybe that explains...

There are a lot of useless number boxes if you open AudioLooper~, but they helped me understand what I was doing, So I left them there for now.

AudioLooper~'s Dependancies: [sfruit/if]
Made with Pd Vanilla 0.45-4(32bit) on OSX

Don.

And just one more thing: how did you change your patch cords into arrows? I have never seen that before

Nice work !

Some [if]s could be replaced by [moses] or [sel]. When you use externals, use namespaces : [sfruit/if] eg, so as to let know to which lib belongs the external.

When a patch gets this hard to read (i've made far worse ), it's time to use [s], [r], [t b b b], etc.

All the gui objects (toggle, atoms, sliders, etc) are eating cpu, even if you don't show them. Try to remove them.

I would use only one inlet and use [route] inside to dispatch messages, so i could just send [play<, [stop<, [loop 1<, etc.
From my experience, remembering the role of each inlet is hard when the object has more than 3 or 4 inlets, unless for self-explanatory objects ([colorRGB], [translateXYZ])

@gsagostinho , it smells like you just did right-click/save the link/ open with pd? The patch is hosted on Dropbox, you have to go there, then download the file

@gsagostinho https://svn.code.sf.net/p/pure-data/svn/trunk/scripts/guiplugins/simple_examples/cordarrows-plugin.tcl

you're looking for this file.

@dwan Thanks on the input. I'll be deleting useless stuff to see how much cpu I can save. I hadn't thought about [s] and [r] for simple stuff like bangs and toggles, i'll try to use it more to simplify the look of the patch. have you encountered any undesirable effect/bug while testing?

Thanks!

@dwan not at all, I did download two proper .pd files. Apparently, the problem is being caused by a conflict with the sfruit library, and my guess is it's a 64bit compatibility problem.

@Don It's working flawlessly and doesn't take much cpu (less than 5% on my old core2duo 1.6ghz).
Playback speed should (imho) take effect immediately, not each time the playback restarts, but i think this is a consequence of your choice to work with [line~].

@gsagostinho The error log you posted shows clearly that you opened something like an html page with pd, even if you think you've downloaded a .pd file. You may have saved an html page as a pd file...

@dwan Hi Dwan, you are completely right! The funny thing is that I did the same thing when downloading [sfruit/if] from sourceforge, so it gave me the absolutely same error, and that's why I thought it was a compatibility problem. Since all these downloaded files were .pd, it never crossed my mind I might be dealing with an html page instead. Silly me

Thanks for pointing it out and take care,
Gilberto