Transposition real time.
Hi guys! i’m trying to make effects to process my voice, and i want to changes the transpose in real time, but i don’t know wich object do that without latency.. i tried with gizmo but it has a little bit of latency. Hope you can help me!
All the best!
Besides [gizmo~] I believe there is only one other option: [tapin]/[tapout], for realtime pitch transpose.
I always found gizmo to be a bit ‘grungy’ too, especially at extremes. Anyway, if you search the forum for either "elastic" or "tapout" plus "pitch", "transpose" etc you should find your way; and look here too:
ps I was going to suggest my own wonderful granulator, but as yet, it’s not realtime, only buffered pitch manipulation.
i presume you mean independent time/pitch stretching/shifting here?
the groove~/gizmo~ combo works very well, but yes, latency incurred because of the fft. such is the reality of physics.
you need a (mainly) granular solution if you want "no" ("less") latency.
it can be done with clever patching, an excellent example of which has been floating around for years, accessible here:
i expect max6 will improve matters here, too.
there are also commercial options such as "elastic~" etc externals based on zplane, but it is not all that great tbh.
sorry, missed brenden’s post.
There is an important bug in elastic~ when you record in buffer~ from live (not from a file): it doesn’t work. I wrote to them and they told me that they were going to fix it but they haven’t done yet.
N00b_meister, I would like seeing tour granulator.
Apologizes for my bad english. Best regards!
Totally wonderful, it is. Wow. I love it. Could you send it to me? I´d love having it.
Congrats and best regards.
Of course, I did suscribe when I saw it. Thank you very much again.
Thanks! amazing stuff… really.
I will post a granular pitchshifter external soon (with fairly low latency, depending on the grainsize)
@pid, you said "latency incurred because of the fft. such is the reality of physics." I recently realised that this latency is not necesarry… you can prevent this latency by building groove and gizmo into 1 external and then processing a lot of frames everytime you jump to a new position. So you trade in latency for a cpu spike :-) Unfortunately this workaround doesn’t work for streaming situations.
timo that is cool. i tend to be interested in the streaming situations though!
what i have done in past is put groove~ and gizmo~ pfft~ into the same abstraction, turn it into a poly~ and upsample it to reduce latency. works pretty well with a butterworth lowpass on output. i never need drastic shifting / stretching, so i am usually reasonably happy.
would be interested to ‘see’ your spikes solution and your ‘granular pitchshifter external’ though!
sweet object, could have done with this a couple of weeks ago ha.
Forums > MaxMSP