Hi Matt,

Can anyone indicate to me what the main differences/advantages are to using xrecord~, loop~, susloop~ (?), xgroove~ etc over the plain old tabwrite~, tabplay~.

i can only speak for the xsample objects because these are the ones i use in most cases. xrecord~ has some additions which might be handy, e.g. mixing-in, signal-triggered recording. xgroove~ is somewhat different to tabplay~ since the playing speed is controlled by a signal, and there are some more features like different interpolation modes, selectable units etc. (the cvs version also has *experimental* cross-fading loop fade zones) Have a look at the help files that come with the xsample package.

I use tabplay~ for looping audio samples, linked to a metro object.
Is this not the ideal way??

It works quite well if the loop is long enough. For very short (granular) loops the time resolution of the bang messages may not be good enough.

greetings, Thomas

susloop~ is mainly useful if you want to loop between two arbitrary points after playing from the beginning of the sample. For example, you could use it to loop the sustained part that follows the attack of an instrumental sample. It gives you sample-accurate looping, while using metro or other control objects can only give block-accurate looping.

Ben

On Friday 28 March 2003 4:34 am, matthew jones wrote:

Can anyone indicate to me what the main differences/advantages are to using xrecord~, loop~, susloop~ (?), xgroove~ etc over the plain old tabwrite~, tabplay~.

I use tabplay~ for looping audio samples, linked to a metro object. Is this not the ideal way??

any hints very welcome!

Matt

---

PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list