Danjel van Tijn

I am hoping to find a simple sampler patch/object with the following qualities:

Single voice
ADSR
sustain loop
simple interface

can-someone-recommend-a-sampler-object

oh and one last feature: playable with midi notes

oh and one last feature:  playable with midi notes


I could but I am trying to save time. I am playing with the samplor~ object found in maxobjects.com.

This is such a basic and essential functional block that it seems unproductive to have to re-invent the wheel.

Each of the apparently "simple" bits of the object you're searching for - to me, anyway - includes a series of decisions that I'm happy I can make for myself. It's not a bug - it's a *feature.*

I made some seamless loops in SoundForge(i.e. no clicking while looping) but when I play them using the Groove~ object I hear clicking at the end of each loopy cycle.

I am thinking that this problem may be due to the fact the loop length is set in groove~ using (ms) instead of samples.

What would be a good way to deal with this?

if you have a sound file that is a seemless loop, then use the replace

message to get it into a buffer (so the buffer resizes to the file

length) and use groove~ with no arguments (other than the buffer name)

and do not use the loop min, loop max inputs :: groove~ will by

> I made some seamless loops in SoundForgec(i.e. no clicking while looping) but when I play them using the Groove~ object I hear clicking at the end of each loopy cycle.

> I am thinking that this problem may be due to the fact the loop length is set in groove~ using (ms) instead of samples.

> What would be a good way to deal with this?

if you have a sound file that is a seemless loop, then use the replace
message to get it into a buffer (so the buffer resizes to the file
length) and use groove~ with no arguments (other than the buffer name)
and do not use the loop min, loop max inputs :: groove~ will by
default loop the whole buffer.

2008/12/1 Danjel van Tijn :
>
> I made some seamless loops in SoundForgec(i.e. no clicking while looping) but when I play them using the Groove~ object I hear clicking at the end of each loopy cycle.
>
> I am thinking that this problem may be due to the fact the loop length is set in groove~ using (ms) instead of samples.
>
> What would be a good way to deal with this?
>
>
>
>
>


You will need to send the 'loop 1' message to the object to make it actually "loop".

One can also send 'loopinterp' message to interpolate at the loop points which can be useful.

Quote: samuel.freeman wrote on Mon, 01 December 2008 13:57

----------------------------------------------------

> if you have a sound file that is a seemless loop, then use the replace

> message to get it into a buffer (so the buffer resizes to the file

> length) and use groove~ with no arguments (other than the buffer name)

> and do not use the loop min, loop max inputs :: groove~ will by

> > I made some seamless loops in SoundForgec(i.e. no clicking while looping) but when I play them using the Groove~ object I hear clicking at the end of each loopy cycle.

> > I am thinking that this problem may be due to the fact the loop length is set in groove~ using (ms) instead of samples.

> > What would be a good way to deal with this?

You will need to send the 'loop 1' message to the object to make it actually "loop". 

Quote: samuel.freeman wrote on Mon, 01 December 2008 13:57
----------------------------------------------------
> if you have a sound file that is a seemless loop, then use the replace
> message to get it into a buffer (so the buffer resizes to the file
> length) and use groove~ with no arguments (other than the buffer name)
> and do not use the loop min, loop max inputs :: groove~ will by
> default loop the whole buffer.
>
> 2008/12/1 Danjel van Tijn :
> >
> > I made some seamless loops in SoundForgec(i.e. no clicking while looping) but when I play them using the Groove~ object I hear clicking at the end of each loopy cycle.
> >
> > I am thinking that this problem may be due to the fact the loop length is set in groove~ using (ms) instead of samples.
> >
> > What would be a good way to deal with this?
> >
> >
> >
> >
> >
>
----------------------------------------------------


You could also replace groove~ with the grooveduck abstraction; normally a good way of eliminating clicking at loop points.

> It is probably more that you set them as integers, instead of more 

nope definitely set them as floats but there were many decimal places and I am not sure how much the groove~ object actually rounds floats.

> It is probably more that you set them as integers, instead of more 
> precise floats...

nope definitely set them as floats but there were many decimal places and I am not sure how much the groove~ object actually rounds floats.


> One can also send 'loopinterp' message to interpolate at the >loop points which can be useful.

I experimented with turning loopinterp on/off with several samples but I heard no change at all. I actually wondered if there was a bug or something (tried it from the help example)

I will try grooveduck and I will also try looping the whole file without setting loop points.

Can someone recommend a sampler object?