Well, I did check the examples and all, but couldn't quite get its potential, or what "variable speed" stands for deep in practice and everything, sorry.
Seems ineteresting though, and that I can make some good use of it.
cheers alex
Message: 1 Date: Thu, 9 Aug 2012 11:20:49 +0100 From: Julian Brooks jbeezez@gmail.com Subject: Re: [PD] ipoke~_v.3_test1 for Pd To: Pierre Massat pimassat@gmail.com Cc: PD List pd-list@iem.at Message-ID: < CAGemBFTg3vK6ez69nTRigVkDUUzHqqXPce21hNxeKGT+Jyx64Q@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1"
Hi Pierre,
Well I would say check the test patches first off and come back if you require more info...
Katja's description on the forum is here: http://puredata.hurleur.com/viewtopic.php?pid=32209#p32209
Cheers,
Julian
Hi Alex,
I suppose the 'bigger picture' is that we have accomplished the 1st step in attempting to plug a perceived lack in current Pd which is a [tabwrite4~] object. [ipoke~] for MaxMSP came up a few times on the list recently and someone mentioned 'could we get the source off him?' So I asked P.A. if we could port it over to Pd and figure out his approach to the interpolating buffer writer problem/lack.
This a small crew of us have done (Katja mainly). We're now in the middle of inserting antialiasing and cubic interpolation (Matt, Katja and Chuck) with P.A. and Alex pitching in and porting it back into Max as a v.4.
Me, I like to use it in looping stuff with on-the-fly pitchshifting (for example). Other usages includes physical modelling and doppler type stuff plus whatever we can think of?
We're not saying it's a game changer but we are confident that it can plug a small hole and hopefully it is well designed and built.
Hope that helps and cheers for checking it out.
Regards,
Julian
Awesome, in fact I'm particularly interested in doing pitch shift on the fly as well, how do you do that?
And what about these limitations of [tabread4~]? I'm getting the idea it's all a matter of better quality in the recording of the audio, is it right or is there any other feature?
And moreover, what is "variable speed" about anyway? I can only make some assumptions, but it'd be good to have a better input on this.
Thanks for working on this and sharing it out.
Cheers
2012/8/9 Julian Brooks jbeezez@gmail.com
Hi Alex,
I suppose the 'bigger picture' is that we have accomplished the 1st step in attempting to plug a perceived lack in current Pd which is a [tabwrite4~] object. [ipoke~] for MaxMSP came up a few times on the list recently and someone mentioned 'could we get the source off him?' So I asked P.A. if we could port it over to Pd and figure out his approach to the interpolating buffer writer problem/lack.
This a small crew of us have done (Katja mainly). We're now in the middle of inserting antialiasing and cubic interpolation (Matt, Katja and Chuck) with P.A. and Alex pitching in and porting it back into Max as a v.4.
Me, I like to use it in looping stuff with on-the-fly pitchshifting (for example). Other usages includes physical modelling and doppler type stuff plus whatever we can think of?
We're not saying it's a game changer but we are confident that it can plug a small hole and hopefully it is well designed and built.
Hope that helps and cheers for checking it out.
Regards,
Julian
On Thu, Aug 9, 2012 at 3:03 PM, Alexandre Torres Porres porres@gmail.com wrote:
Awesome, in fact I'm particularly interested in doing pitch shift on the fly as well, how do you do that?
And what about these limitations of [tabread4~]? I'm getting the idea it's all a matter of better quality in the recording of the audio, is it right or is there any other feature?
And moreover, what is "variable speed" about anyway? I can only make some assumptions, but it'd be good to have a better input on this.
Thanks for working on this and sharing it out.
Cheers
Alex et al.,
[tabread4~] reads from a table of numbers based on the index you give it. If you give it a fractional index (e.g. "3.427"), it will interpolate between the values in the two surrounding points (in the example, between the values stored at indices 3 and 4). It does so by drawing a curve that fits the values at the four surrounding indices, and outputs the value of that curve at your fractional index. In some way, it is trying to fill in between samples, and give you a value of what the sample "would have been" at that factional index.
So, you can read through a table faster or slower than the original sample rate, and [tabread4~] will give you higher quality by filling in the gaps (this is one of the things meant by "variable speed").
[ipoke~] does this in reverse -- it's a table writer, so the left inlet you give the signal you want to write, and right inlet you give the indices in the table you want to write. If you write into the table fast (e.g. imagine the indices you give it are [0, 4.5, 9, 13.5, 18, 22.5, 27 ...]), it will interpolate over the gaps and give you a lower sound. So far it does linear interpolation, but in the works is cubic interpolation like in [tabread4~].
It can be used for many things like pitch and doppler shifts, and other more experimental things in a way that can be difficult to get with a table reader like [tabread4~]. You can change the speed you go through the table with a [phasor~] for complicated pitch shifts, and you can write backwards into a table as well. [ipoke~] will also let you overdub -- that is, mix the signal you want to write into the table with what is already there. This gives you some flexibility.
I'm not sure what you mean by "pitch shift on the fly" -- can you elaborate?
Best,
Matt
-
Alexandre Torres Porres -
Julian Brooks -
Matt Barber