coffeencigs

i dont know if anyone of you ever used jit.qt.movie (i know its jitter)

it has the "palindrome" function meaning.. you set a looppoints and the video plays from loopstart to end and then from loop end to start in reverse...

is this possible with a groove~ or any other max object for sound playback?

i cant find anything in the helps.. but maybe there is a trick

i dont know if anyone of you ever used jit.qt.movie (i know its  jitter)

is this possible with a groove~ or any  other max object for sound playback?

palindrome-looping

Alternate between sending a positive and negative signals to groove~, switching sign when the right outlet hits one or zero.

Hello if you find a thread titled- 'more more on clickless looping (sorry)' . Open my patch & it has this function. you'll need to add in a few more bits to clear up the clicks though. But it's all in that thread. I'm away from my max machine for a few days so can't update at the mo'. It's easy enough to implement and I'm sure someone has more sleek way to do it than I but it'll get yopu started.

im using a select object and in the left inlet goes the current position of the sample (in ms), in the right inlet the value of the loopend position (in ms)

so what i thought was, everytime when the current position equals the loopend position, select should bang, and then send the -1 msg to the grooves~'s sig~ object..

but it doesnt work, and i get the feeling that it is because the float with the current postion is running too fast for the select to recognize...

when i set the playback speed to 0.3 it works perfectly...

im using a select object and in the left inlet goes the current position of the sample (in ms), in the right inlet the value of the loopend position (in ms) 

but it doesnt work, and i get the feeling that it is because the float with the current postion is running too fast for the select to recognize...
when i set the playback speed to 0.3 it works perfectly...

you might have to loose a bit of precision for this to work..

yes, it's probably too fast.
you might have to loose a bit of precision for this to work..

Not sure why you re-made the thread, but if you modify whatever patch you're making to be controlled at audio-rate, ie by using wave~, index~ or maybe play~ instead of groove~ for playback, you won't run into these max-timing issues.

Using a triangle wave with a range of 0. to 1. to drive wave~ is a much simpler and more accurate way of doing what you want, in my opinion anyway.

I'm not sure what others think of this, but I always feel that when working with audio, use signals to control parameters that relate to timing/accuracy whenever possible. Don't compromise and lose precision unless you really really have to!

I'm not sure what others think of this, but I always feel that when working with audio, use signals to control parameters that relate to timing/accuracy whenever possible.  Don't compromise and lose precision unless you really really have to!  

I've put in a way of changing the loop length that was missing from my other post. Is this not the kind of thing you're after? It's not groove~ based, but it will work, arguably better than messing with select and edge~ combinations.

I've put in a way of changing the loop length that was missing from my other post.  Is this not the kind of thing you're after?  It's not groove~ based, but it will work, arguably better than messing with select and edge~ combinations.

timlloyd wrote on Tue, 08 September 2009 18:42

it will work, arguably better than messing with select and edge~ combinations

timlloyd wrote on Tue, 08 September 2009 18:42it will work, arguably better than messing with select and edge~ combinations

ooooops, total time output on info needs to be plugged into the left inlet of [f ] not the right, otherwise when you load a new file the loop length and playback frequency isn't updated.

palindrome looping?