Elasticindex~ as a play~ replacement.
Does anyone here own Elasticindex~? I am tempted to buy it, but I want to use it to replace an instance of play~ in my patch. AFAIK, the difference between play and index is that play interpolates between millisecond values, while index takes pure sample-based information. How much work is involved in replacing play~ with index~/elasticindex~? Is it as simple as putting some mstosamp objects in the line, or is there more to it? I'd expect that mstosamp would cause some glitchy issues.
Also, does elasticindex~ suffer the same problem as play~ does when referencing long (greater than 3-4 minutes at 48k/24b) audio files? Play~ often sounds like sample rate reduction after a point (I actually use hr.play to get around that).
Well I used the regular eleastic~ external and was very happy
with its sound quality. It requires you to load the sound in to
a buffer. Eventually I will probably get elasticindex~ as well.
I own and use it. It is really good, very useful, but unfortunately does not sound completely transparent at normal speed/pitch with it's elastic algorithm on (it can be switched off to become a normal index` essentially)
Transients sound a little blurred, and there is a slight "tremolo" covering the sound. I emailed the elastic~ team about it a few weeks ago, because I know they intended it to be transparent at normal speed/pitch. Not heard back yet regarding a possible cause (if it is my setup that is the problem or a bug in my external, or even just a part of the algorithm etc..)
I do recommend it though, it's freezing/incredibly slow playback at normal pitch granular-ish capabilities are very interesting to use and sound very smooth.
My workaround at the moment is to use it in conjunction with index~, both linked to the same buffer~, and just switch into elasticindex~ when I want something other than normal playback.
I have to rush off to work, but I'll post a .wav demonstrating the sound quality issue I was talking about later this evening.
I buyed elastic~, and i'm not so happy with its sound quality. When you put the pitch is going down (or accelerate) it's ok, but when you put the pitch up, it's still sounds rather metallic for a "patented algorythm" that's supposed to be used in expensive pro-audio soft like cubase. (hear the example sound attached)
I find the gabor/ftm maxmsp package much more powerful on several points: "freezing" effets (see patch bellow) are must more controlable than with elastic~. For slowing down or pitching up mono-pitched sounds, like voice or instrument sounds, gabor's pitch-shift(see patch), will sometimes sounds really better than elastic~ (hear the example sound attached), Plus it have a formant parameter that is great. And it's totally free.
But i'm still wondering is there are some better sounding pitch shift somewhere.. I remember few years ago a dj playing with the speed on rock'nroll standards (Virtual dj or a soft like that), i was impressed by quality... far better that elastic~ i think.
I also note that i questioned the elastic team about their differents packages, and they answered me that elasticx~&elasticindex~ sound was less good than elastic~ sound.
what they said... sounds like something easily done in max. it's no serato or eventide thats for sure... I wish I knew what the magic of those nice shifters was
> serato or eventide
hmm.. just listening to the serato examples it looks 4 time better than elastic~ but... it's 10 times more expensive ! And even not avalaible as vst, only protool. same for eventide i think.
yeah. I'm just holding them up as standards to judge things by. Serato isn't real time at all. in the same spirit as "omx is great but they are no LA-2A"
Yes, Serato Pitch and Time is purely a non-realtime process. The discussion of elastic~ and elasticx~/elasticindex~ sound quality is very informative, but I really was wondering how hard it would be to convert a patch that currently uses play~ (rather different from index~) over to using elasticindex~ instead.
I've never really used play~ so I'm not too sure about that, but as far as I've found elasticindex~ operates in exactly the same way as index~, so you could modify the patch to use index~ and see how tricky it is. Then if you get elasticindex~ it will just slot right in.
My first thought is it would be pretty straightforward, as play~ uses a signal position in milliseconds the same way index~ uses a signal position in samples. The only thing might be that if you're converting milliseconds to samples you might (not sure) end up with the sample index containing occasional floats, in which case you would have to use trunc~.
Going back to the sound quality thing, I really can't complain about elasticindex~. I've only used it for dramatic pitch/time changes, mainly slowing down and freezing at normal pitch. I really like how it sounds for this, its so easy to use, and doesn't require me spending ages making my own granular processor or puzzling over the gabor/fmat objects. If you want the grain position variation quirkiness that could easily be done as well.
I've been using it in a phrase sampler patch, with phasor*loop length as a playback signal. Then just use sah~ to freeze, and you can scrub through a buffer at any speed really smoothly. For a grain position thing, I could just make a little rand~ or crazy lfo signal and modulate the frozen sample value with that. I'm gonna get off the internet and try it out!
-edit- it could even be this simple depending on your patch:
timlloyd wrote on Thu, 06 August 2009 00:47 its so easy to use, and doesn't require me spending ages making my own granular processor or puzzling over the gabor/fmat objects. If you want the grain position variation quirkiness that could easily be done as well.
You're right that elastic is more simple to use than gabor.
But gabor is using "overlap" methods, so any patch using msp objects or elastic will never sounds the same than the gabor example patch i put above, until you put tons of complicated stuff in a poly~.
Thats true, I only meant it could approximate it, but I tried it yesterday and unfortunately it does not sound good. I need to learn more about this granular stuff!
Something that puzzles me when I look at the gabor/ftm stuff is all the data connections, If it was in a patch made for live use, would it be as fast/responsive as something controlled at audio rate, more like the granular toolkit objects from nathan wolek?
I'm getting more and more interested in making a granular patch now for using on live audio and looped phrases. Will have to look more into the gabor and GT stuff.
> would it be as fast/responsive as something controlled at
> audio rate
I don't see why it wouldn't. The only think to know maybe, because of the special way the gabor object are sending their data to each other, i had some clicks with vector size less than 256 sometimes, so it could be a 2,5 ms additional latency if you expected a 128 vector size.(at 44100Hz)
> I'm getting more and more interested in making a granular
> patch now for using on live audio and looped phrases.
Maybe you could also have a look at cataRT from Diemo Schwarz, the guy that made ftm, it's a big granular engine, that analyse and organize "pellets" of your sound to show them as an xy cloud in a lcd (lots of parameters for the representation of the "pellets", color, pitch, periodicity, loudness,etc..) and then play them from the cloud. Also, you specify how many beats are in your sound, if you want to cut it in rythmic pieces. I discovered this yesterday, it's a bit rough to understand, but there is a doc in pdf.
Also, it's really easier to patch using the "ftm message box". And faster to compute... see picture.
Hi ,
To Alexandre:
Would you have a 4.6 version of the Gabor test patches ??
thanks a lot
phil
Found them on their site.
They sound great!!
thanks for the lead
phil
Wow, I was completely blown away by the cataRT engine! What a fantastic piece of work, opens up all kinds of possibilities.
MAN!!
That ftm bundle is just crazy. Sounds amazing. lot's of possibilities.
thanks again alexandre
phil
The only problem with the stuff from the guys at ircam, is that they don't really manage to communicate well on the work they make. Even when i was a member of the ircam forum, it was not easy to just understand what all theses fantastic objects and patches were doing, and how they work. I'm surprised every time i speak about ftm here, in this forum, that almost nobody really seem to know this great stuff. Look at the number of topics here about this expensive elastic~ object compared to the number of topics about free ftm/gabor. It might be as important to describe really clearly the possibilities of a package/patch, when making it, with example sounds, and maybe with a youtube video, (look at the presentation video from elastic~), than to make it. If not, lot's of people will never hear about it.
> Would you have a 4.6 version of the Gabor test patches ??
I don't have, but they are just the gabor examples patches from ircam, i just added a [preset] in one and a [biquad] in the other.
I totally agree.
IRCAM makes fantastic stuff but it is not very well communicated to interested user. Mostly in the scientific paper style.
Online demos, tutorials and YouTube videos would be fantastic !!
/thomas
(Ircam forum member and owner of the elastic~ objects)