groove~ buggy weirdness
Hey everyone, I’ve been having some problems with groove~ and I wanted to
find out if I’ve just been doing things wrong for a while or if there is
some problem with the object that no one talks about.
Very frequently when using groove~ to play from a buffer, it will just not
respond to signals that I send it. This usually happens after I play from
the buffer once without having loop turned on. I thought that this might
have to do with groove thinking that it’s a literal tape loop, so that if I
send it a positive signal of 1 to go forward. It would need a signal of -1
to go back to the beginning of the "tape." Does that make sense? I tried
that and it worked, but only sometimes. All of this wouldnt really be a big
deal –it was minor enough to probably be user error– until I discovered
that while turning the dac~ on and off didnt help, adding a new MSP object
while the dac~ was on temporarily fixed the problem, but only temporarily.
Does anyone know what this means? Is there some sort of ram issue going on?
Am I missing some major function of the groove~ object?
I only know that if the loop is off you can’t play samples backward,
but everything else should work. i mean, every value > 0 should make
it play, no need of a negative value to go back.
hope this helps.
The loop is off and I’m playing samples backward. I checked this out on my
other machine and basically the exact same thing happend so I’m inclined to
think that It’s something I’m doing wrong. But I am still experiencing the
> Am I missing some major function of the groove~ object?
i would say so….
the manual says:
int or float In left inlet: Sets the sample playback position in
milliseconds. 0 sets the
playback position to the beginning.
before (re)starting your groove, you have to tell it from where to
restart – it it’s from the beginning a simple [t f 0] should do the
have a look at the help file
Kasper T. Toeplitz
noise, composition, bass, computer