Re: [PD] Sigmund~ parameters
Hi Miller, Here's a more detailed example. I've found that this problem is particularly obvious with minpower. The sound file I'm playing through sigmund has peaks varying mostly between 60 and 80, with occasional peaks around 90 (according to sigmund's env output). To my understanding the help file suggest that a value of minpower around 50 should detect pretty much all the notes, and a value around 90 would detect almost none. But in practice I find that there's almost no difference. I have to use values of minpower around 100 and 130, with 130 having the effect of effectively making sigmund output no notes at all. Is it a normal behaviour? Is there something I don't get in the way sigmund's work? I feel the growth parameter have this same issue, it feels to me that it's working quite differently in practice than what you would expect from reading the help file. Thanks for this wonderful object! Benoît Fortier Le jeudi 13 mars 2014 0h37, Miller Puckette m...@ucsd.edu a écrit : I presume you found the (very short) mention in the subppatch of the help wnidow (pd setting-parameters). Basically, if the measured signal power is less than minpower (expressed in dB) then the reported instantaneous potch is zero and no new notes will be reports (and this can give rise to repeated notes if the input power drifts below this value and then rises again.) growth is a threshold whereby sigmund~ may report repeated notes at teh same pitch, even if that pitch s continuously present in the signal, just because of a fall and subsequent rise in the measured power. This all needs a picture :) M On Wed, Mar 12, 2014 at 04:10:23PM -0700, Benoît Fortier wrote: Ok folks, never mind, I did some more testing with sigmund~ and I do now see that minpower and growth seems to be working. It works in a way I'm not quite sure to understand so I find it hard to use those parameters in a meaningful, predictable way, but I guess that's because of my limited understanding of what's going on exactly under the hood. Benoît Fortier Le mercredi 12 mars 2014 16h50, Benoît Fortier benoitfort...@yahoo.ca a écrit : Thanks for your reply. Yes I did some testing with fiddle and Helmholtz, If I need to I'll get to that in an other question. My question wasn't clear enough sorry about that. I would like first to clarify some aspect of the sigmund notes mode which seems very straight forward in the help file, namely growth and minpower parameter, but which in practice I find it doesn't quite work as expected. As anyone ever managed to get significantly different output by changing those two parameters? Are they working at all, and if so can anyone explain for the record how they actually work? Or maybe I'm missing something obvious? I'll ask a clearer question regarding other specific strategies for refining pitch tracking result soon, thank you for your help. Benoît Fortier 581 995-5622 Le mercredi 12 mars 2014 16h02, Alexandros Drymonitis adr...@gmail.com a écrit : Haven't tried [sigmund~], but [fiddle~] and [helmholtz~] (the latter by Katja Vetter) and I found [both fine but [helmholtz~] a bit better for my taste. I think it's a bit more responsive. What if you combine this with [env~] for example and this way you get pitch and amplitude... On Wed, Mar 12, 2014 at 9:42 PM, Benoît Fortier benoitfort...@yahoo.ca wrote: Dear list, I've been working on a patch for quite a few months now which involves pitch tracking. I've explored many possible solutions, considering the pros and cons of every approach, made different tests, etc. I've also done a lot of reading (help files, forums, etc), but I couldn't find satisfying answers to all my questions. I am now in front of 4 or 5 different approach, each of which requires to do a certain number of compromise at different level. My feeling is that I am now at the point where I could possibly eliminate some of those compromise with your help. I have a lot of questions, but I'll start with one regarding Sigmund's notes parameters. I've done a lot of tests, changing one parameter at a time. I found that only the stable time and vibrato parameters seems to be affecting the output the way it should. The other parameters - growth and minpower - doesn't seem to be working the way it's described in the help file. Am I the only person who noticed that? When I looked in the list archives, I found someone else mentioning this issue but nobody replied (and i lost the link to the thread). I'm using my patch to track the pitch of a violin. What I'm trying to do is to convert the pitch of the violon into the most accurate note on message possible (with midi note and velocity). I need this patch to be as responsive as possible but also with as few insignificant output as possible. Thanks for your help! Benoît Fortier 581 995-5622
[PD] Sigmund~ parameters
Dear list, I've been working on a patch for quite a few months now which involves pitch tracking. I've explored many possible solutions, considering the pros and cons of every approach, made different tests, etc. I've also done a lot of reading (help files, forums, etc), but I couldn't find satisfying answers to all my questions. I am now in front of 4 or 5 different approach, each of which requires to do a certain number of compromise at different level. My feeling is that I am now at the point where I could possibly eliminate some of those compromise with your help. I have a lot of questions, but I'll start with one regarding Sigmund's notes parameters. I've done a lot of tests, changing one parameter at a time. I found that only the stable time and vibrato parameters seems to be affecting the output the way it should. The other parameters - growth and minpower - doesn't seem to be working the way it's described in the help file. Am I the only person who noticed that? When I looked in the list archives, I found someone else mentioning this issue but nobody replied (and i lost the link to the thread). I'm using my patch to track the pitch of a violin. What I'm trying to do is to convert the pitch of the violon into the most accurate note on message possible (with midi note and velocity). I need this patch to be as responsive as possible but also with as few insignificant output as possible. Thanks for your help! Benoît Fortier 581 995-5622___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Sigmund~ parameters
Thanks for your reply. Yes I did some testing with fiddle and Helmholtz, If I need to I'll get to that in an other question. My question wasn't clear enough sorry about that. I would like first to clarify some aspect of the sigmund notes mode which seems very straight forward in the help file, namely growth and minpower parameter, but which in practice I find it doesn't quite work as expected. As anyone ever managed to get significantly different output by changing those two parameters? Are they working at all, and if so can anyone explain for the record how they actually work? Or maybe I'm missing something obvious? I'll ask a clearer question regarding other specific strategies for refining pitch tracking result soon, thank you for your help. Benoît Fortier 581 995-5622 Le mercredi 12 mars 2014 16h02, Alexandros Drymonitis adr...@gmail.com a écrit : Haven't tried [sigmund~], but [fiddle~] and [helmholtz~] (the latter by Katja Vetter) and I found [both fine but [helmholtz~] a bit better for my taste. I think it's a bit more responsive. What if you combine this with [env~] for example and this way you get pitch and amplitude... On Wed, Mar 12, 2014 at 9:42 PM, Benoît Fortier benoitfort...@yahoo.ca wrote: Dear list, I've been working on a patch for quite a few months now which involves pitch tracking. I've explored many possible solutions, considering the pros and cons of every approach, made different tests, etc. I've also done a lot of reading (help files, forums, etc), but I couldn't find satisfying answers to all my questions. I am now in front of 4 or 5 different approach, each of which requires to do a certain number of compromise at different level. My feeling is that I am now at the point where I could possibly eliminate some of those compromise with your help. I have a lot of questions, but I'll start with one regarding Sigmund's notes parameters. I've done a lot of tests, changing one parameter at a time. I found that only the stable time and vibrato parameters seems to be affecting the output the way it should. The other parameters - growth and minpower - doesn't seem to be working the way it's described in the help file. Am I the only person who noticed that? When I looked in the list archives, I found someone else mentioning this issue but nobody replied (and i lost the link to the thread). I'm using my patch to track the pitch of a violin. What I'm trying to do is to convert the pitch of the violon into the most accurate note on message possible (with midi note and velocity). I need this patch to be as responsive as possible but also with as few insignificant output as possible. Thanks for your help! Benoît Fortier 581 995-5622 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Sigmund~ parameters
Ok folks, never mind, I did some more testing with sigmund~ and I do now see that minpower and growth seems to be working. It works in a way I'm not quite sure to understand so I find it hard to use those parameters in a meaningful, predictable way, but I guess that's because of my limited understanding of what's going on exactly under the hood. Benoît Fortier Le mercredi 12 mars 2014 16h50, Benoît Fortier benoitfort...@yahoo.ca a écrit : Thanks for your reply. Yes I did some testing with fiddle and Helmholtz, If I need to I'll get to that in an other question. My question wasn't clear enough sorry about that. I would like first to clarify some aspect of the sigmund notes mode which seems very straight forward in the help file, namely growth and minpower parameter, but which in practice I find it doesn't quite work as expected. As anyone ever managed to get significantly different output by changing those two parameters? Are they working at all, and if so can anyone explain for the record how they actually work? Or maybe I'm missing something obvious? I'll ask a clearer question regarding other specific strategies for refining pitch tracking result soon, thank you for your help. Benoît Fortier 581 995-5622 Le mercredi 12 mars 2014 16h02, Alexandros Drymonitis adr...@gmail.com a écrit : Haven't tried [sigmund~], but [fiddle~] and [helmholtz~] (the latter by Katja Vetter) and I found [both fine but [helmholtz~] a bit better for my taste. I think it's a bit more responsive. What if you combine this with [env~] for example and this way you get pitch and amplitude... On Wed, Mar 12, 2014 at 9:42 PM, Benoît Fortier benoitfort...@yahoo.ca wrote: Dear list, I've been working on a patch for quite a few months now which involves pitch tracking. I've explored many possible solutions, considering the pros and cons of every approach, made different tests, etc. I've also done a lot of reading (help files, forums, etc), but I couldn't find satisfying answers to all my questions. I am now in front of 4 or 5 different approach, each of which requires to do a certain number of compromise at different level. My feeling is that I am now at the point where I could possibly eliminate some of those compromise with your help. I have a lot of questions, but I'll start with one regarding Sigmund's notes parameters. I've done a lot of tests, changing one parameter at a time. I found that only the stable time and vibrato parameters seems to be affecting the output the way it should. The other parameters - growth and minpower - doesn't seem to be working the way it's described in the help file. Am I the only person who noticed that? When I looked in the list archives, I found someone else mentioning this issue but nobody replied (and i lost the link to the thread). I'm using my patch to track the pitch of a violin. What I'm trying to do is to convert the pitch of the violon into the most accurate note on message possible (with midi note and velocity). I need this patch to be as responsive as possible but also with as few insignificant output as possible. Thanks for your help! Benoît Fortier 581 995-5622 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : Re : store and manipulate multiple lists
I'm still not familiar with data structure and pointers in pd, but I think I'll use your suggestion as a starting point. Thanks! BEnoît De : Frank Barknecht f...@footils.org À : pd-list@iem.at Envoyé le : samedi 17 mars 2012 11h49 Objet : Re: [PD] Re : store and manipulate multiple lists Hi, On Thu, Mar 15, 2012 at 11:39:51AM +, Andy Farnell wrote: Yes of course. Once you can sort items of any type you can sort aggregate items, structs, sublists or whatever on one of their elements. Its a little messy in Pd. The best way might be to use pointers and try to do the classic Kernighan and Richie head swap thing but I have no idea how to exchange pointers in Pd. Sorting lists of numbers by their first element is pretty easy to do with Pd's data structures/pointers. I don't have Pd at hand now to patch an example (maybe Monday), but basically you first define a data structure with one float x field and one with an array of these float-items in addition to its own float x. [pd $0-f]: structure with one float item: [struct $0-f float x] [pd $0-record]: structure with an x-float for sorting and the array data to hold all the list items: [struct $0-record float x array data $0-f] Then you create the structured data from the lists and write them to a subpatch as usual with data structures. The first element in an incoming lists doubles as x position, the array holds the rest of the list. [r one-list] | [t a a a] | | | | | [list split 1] | | | ... traverse subpatch blabla | | [append $0-record x] | | | | | [s $0-current-pointer] | | | [list length] [r $0-current-pointer] | | | | [setsize $0-record data] | [list-enumerate] - list-drip with index numbers, i.e. list a b - 0 a, 1 b | [swap] [r $0-current-pointer] | \ | [element $0-record data] | \ [set $0-f x] Then sorting is just a message sort to the subpatch receiver, afterwards dump the lists again using basically the opposite from above. You're only interested in the data array now. Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : store and manipulate multiple lists
My problem is similar to your case b. Maybe I shoud mention at this point that the lists are midi messages, and the first number of each lists are timestamps. I'm looking for a solution within pd. I shall have a look at all your suggestions, they look all very good. The [coll] object seems to be the easiest solution to adapt to my patch, but I don't like the fact that the [sort fonction strips out the number it uses to do sorting, in my case the timestamp which is off course an important information. But well, thats quite easy to fix. For your interest, the goal of the patch is to create a text file which will be converted into a midi file using [seq]. It seems that [seq] works well only with sequentially ordered midi messages. Thanks again Benoît De : Lorenzo Sutton lorenzofsut...@gmail.com À : pd-list@iem.at Envoyé le : jeudi 15 mars 2012 8h41 Objet : Re: [PD] store and man On 14/03/12 23:04, Benoît Fortier wrote: Hi everybody, I need to store multiple lists of numbers in a text file in a specific order : the first number of each list must be ascending, from the first line of the text file to the last. The problem is this : my patch outputs the lists in an unordered way. I could rewrite the patch so that the lists gets outputed the correct way, but to be able to store all the lists somehow and then write a patch to order them afterward feels to me like a much more elegant solution. Any toughts on this? For me it is not very clear if: a. your patch outputs some unordered lists for which you want to save the produced order E.g. [x y z( [z x y( [a b c( should be written to the text file in that order 1 x y z; 2 z x y; 3 a b c; or b. your patch outputs lists like [3 x y z( [1 z x y( [2 a b c( in an unknown order and you want to save them in the text file as: 1 z x y; 2 a b c; 3 x y z; In case a. it's quite trivial just add a counter which grows at each list production and prepend it to the list then add the list to the [textfile] In case b. I would probably save the lists unordered with [textfile] and then use some scripting like python to easily sort them Lorenzo. Thank you all, this list has been very helpfull to me, and its also quite entertaining! Benoît ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] store and manipulate multiple lists
Hi everybody, I need to store multiple lists of numbers in a text file in a specific order : the first number of each list must be ascending, from the first line of the text file to the last. The problem is this : my patch outputs the lists in an unordered way. I could rewrite the patch so that the lists gets outputed the correct way, but to be able to store all the lists somehow and then write a patch to order them afterward feels to me like a much more elegant solution. Any toughts on this? Thank you all, this list has been very helpfull to me, and its also quite entertaining! Benoît ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : store and manipulate multiple lists
Thanks Andy. But as far as I know, [list-sort] will sort the number in a list, and what I really need is to sort multiple lists according to their first element (which are numbers)... is there a trick with [list-sort] that allows to do that? Benoît De : Andy Farnell padawa...@obiwannabe.co.uk À : Benoît Fortier benoitfort...@yahoo.ca Cc : pd-list pd-list@iem.at Envoyé le : mercredi 14 mars 2012 18h17 Objet : Re: [PD] store and manipulate multiple lists [list sort] maybe? a. On Wed, Mar 14, 2012 at 03:04:25PM -0700, Benoît Fortier wrote: Hi everybody, I need to store multiple lists of numbers in a text file in a specific order : the first number of each list must be ascending, from the first line of the text file to the last. The problem is this : my patch outputs the lists in an unordered way. I could rewrite the patch so that the lists gets outputed the correct way, but to be able to store all the lists somehow and then write a patch to order them afterward feels to me like a much more elegant solution. Any toughts on this? Thank you all, this list has been very helpfull to me, and its also quite entertaining! Benoît ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : store and manipulate multiple lists
Thanks, that looks like what I need! Benoît De : Jonathan Wilkes jancs...@yahoo.com À : Andy Farnell padawa...@obiwannabe.co.uk; Benoît Fortier benoitfort...@yahoo.ca Cc : pd-list pd-list@iem.at Envoyé le : mercredi 14 mars 2012 18h25 Objet : Re: [PD] store and manipulate multiple lists cyclone/coll can sort the messages you store in it. -Jonathan - Original Message - From: Andy Farnell padawa...@obiwannabe.co.uk To: Benoît Fortier benoitfort...@yahoo.ca Cc: pd-list pd-list@iem.at Sent: Wednesday, March 14, 2012 6:17 PM Subject: Re: [PD] store and manipulate multiple lists [list sort] maybe? a. On Wed, Mar 14, 2012 at 03:04:25PM -0700, Benoît Fortier wrote: Hi everybody, I need to store multiple lists of numbers in a text file in a specific order : the first number of each list must be ascending, from the first line of the text file to the last. The problem is this : my patch outputs the lists in an unordered way. I could rewrite the patch so that the lists gets outputed the correct way, but to be able to store all the lists somehow and then write a patch to order them afterward feels to me like a much more elegant solution. Any toughts on this? Thank you all, this list has been very helpfull to me, and its also quite entertaining! Benoît ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : sigmund~
Thanks Frank and Michael. So I understand that linearity of amplitudes in this case and, i guess in many other case as far as pd is concerned, refers to the -1 to 1 scale used to calculate waveform. I do understand the whole idea of linearity and non-linearity but I guess my confusion come from that I tend to see linearity in a relative way. For example, one could say that a linear increase in decidel does not correspond to a linear increase of peak amplitude, and vice et versa (of course). None of the two correspond to a linear increase of the sound that we ear either(as in twice the value = twice the volume).I'll go have a look at all the readings you suggested to me, thanks you again for that. I do remember I've read something about it in Miller's book. Is there anyone else out there using pd to make tools for composers? stuff like spectral analysis that outputs notes in midi format, or tools that transform and modulate melodic patterns in various ways, and then output the result in midi? Thanks again! Benoît De : Frank Barknecht f...@footils.org À : pd-list@iem.at Envoyé le : Vendredi 30 Septembre 2011 3h44 Objet : Re: [PD] sigmund~ Hi, On Thu, Sep 29, 2011 at 06:35:51PM -0700, Benoît Fortier wrote: I'm using the sigmund~ object to get amplitude and pitch information for the loudest peaks of a signal (see the sinusoid-tracking help patch, which can be found in the sigmund~ help patch). Out of that information, I want to create, let's say, 5 midi notes corresponding to the 5 loudest peaks of the signal. How would you transform the peak amplitude outputs of sigmund, which are linear, into midi velocities in order to make those 5 notes sound with the same relative amplitude that they have in the analysed signal? It might be a stupid question but what are those linear peak amplitude values exactly? Do they have any unit? They don't have a unit, they specify the actual peak amplitude of a sine component in a signal. If you feed a sigmund~ with an unscaled [osc~] the peak reported should be close to 1, as the sinewave coming out of an [osc~] goes from -1 to 1, so the absolute peak is 1. If you attenuate this [osc~] by multiplying it by 0.5, sigmund~ should report a peak near 0.5 accordingly. The amplitude is linear in that it directly outputs this multiplication factor - multiplication by constants (homogeneity of degree 1) and addition (additivity) are the two linear operations here. See e.g. http://en.wikipedia.org/wiki/Linear_map for some gory details. There also are non-linear operations possible. For example multiplication of a signal with itself is a first step into the non-linear world. You may remember the parabolic curve if you plot f(x)=x*x which looks like a glass of wine and obviously is not a straight line(ar) anymore. dB-curves are similarily skewed, as are square root, log, or other [pow] curves. Now it's possible to express the amplitude of signals in various ways. The peak amplitude above actually already is a modification in that it only considers the absolute value of the actual amplitude (which is negative sometimes in the case of an [osc~], but not for a [phasor~]!). You could also look at the instantaneous amplitude of a signal with [snapshot~] for example, or calculate some kind of average, or use the absolute peak-to-peak-amplitude (which would be 2 for an [osc~]!) A very important amplitude specification is the RMS or root-mean-square amplitude. This is especially interesting as a signal's power is proportional to the square of RMS. RMS in Pd is calulated by the [env~] object. Now in music you very often are interested in powers, intensities or loudness (more complicated) values, for example you want something to be twice as loud as another sound. That's where logarithms and decibels come in. Check e.g. this http://hep.physics.indiana.edu/~rickv/Loudness_Scales.html for some details. In Pd an important thing to know is its non-standard use of the term dB: For example [env~] outputs values in dB which are scaled so that a [sig~ 1] will have an RMS of 100, and [sig~ 0] has RMS of 0. But to convert these into linear amplitude multipliers from 0 to 1 you cannot just divide by 100, as your intermediate values would be wrong: [sig~ 0.5] gives an [env~] of about 93.97 and not 0.5 as might be expected! Instead use [dbtorms] here, and [rmstodb] for the undo-operation. The attached file shows these operations in action. More reading stuff: http://en.wikipedia.org/wiki/Amplitude http://www.iu.edu/~emusic/acoustics/amplitude.htm Ciao -- Frank ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] sigmund~
Hello all, I'm using the sigmund~ object to get amplitude and pitch information for the loudest peaks of a signal (see the sinusoid-tracking help patch, which can be found in the sigmund~ help patch). Out of that information, I want to create, let's say, 5 midi notes corresponding to the 5 loudest peaks of the signal. How would you transform the peak amplitude outputs of sigmund, which are linear, into midi velocities in order to make those 5 notes sound with the same relative amplitude that they have in the analysed signal? It might be a stupid question but what are those linear peak amplitude values exactly? Do they have any unit? More generally, can you give me any good reference, preferably online, that explain in details the physic and mathematic behind sound amplitude? I manage to work many things out by myself but i have to admit that my actual understanding of it is a little bit superficial. By the way, I have a good background in physic and mathematic so don't hesitate to suggest me more advanced readings. Thank you! I've learned a lot from you already just by reading the list. Benoît ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : connecting a samphold and a phasor together
Thank you, I just tried the loop~ object and it works very well for what I'm doing (a looping sampler which allows to change the offset and the size of the repeated segment without transposing it... rather simple stuff I suppose but fun to work on when learning!). One more question came up to my mind when trying the loop~ object : it is recommended under certain circonstances to add 3 samples to an array to allow a better playback (or something like that) when building a sampler. Anyone can explain me why and when it is necessary to add those 3 samples? I hope I'm not spaming this list with obvious, newbie questions! Thanks in advance. Benoît De : Miller Puckette mpuck...@imusic1.ucsd.edu À : Roman Haefeli reduzie...@yahoo.de Cc : Beno?t Fortier benoitfort...@yahoo.ca; pd-list@iem.at Envoyé le : Jeu 29 avril 2010, 11 h 43 min 23 s Objet : Re: [PD] connecting a samphold and a phasor together There's also the loop~ object (in pd/extra) which I had to write for exactly this reason. But I doubt it's general enough for every possible purpose :) Miller On Thu, Apr 29, 2010 at 04:26:13PM +0200, Roman Haefeli wrote: On Wed, 2010-04-28 at 08:03 -0700, Beno??t Fortier wrote: First time on this mailing list, so hello everyone! I started using pd a couple of month ago and I'm completely addicted. Ok I have a simple problem for which I'm looking for the most elegant solution. I need a phasor (in a looping sampler) which frequency can be changed only at the beginning of it's period (when it drops to zero). That's usually the kind of problem a samphold can handle very well but when I connect a phasor and a samphold directly together I get a dsp loop detected (some tilde objects not scheduled) error. One solution could be to pipe the new frequency to the phasor with a delay calculated from the previous frequency but I have the feeling there must be a more elegant solution to this problem. Anyone got a suggestion? In order to avoid recursiveness, you could do it by using [metro] and [vline~]. Then you have the feature 'update the frequency only loop-start' for free. Roman ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] connecting a samphold and a phasor together
First time on this mailing list, so hello everyone! I started using pd a couple of month ago and I'm completely addicted. Ok I have a simple problem for which I'm looking for the most elegant solution. I need a phasor (in a looping sampler) which frequency can be changed only at the beginning of it's period (when it drops to zero). That's usually the kind of problem a samphold can handle very well but when I connect a phasor and a samphold directly together I get a dsp loop detected (some tilde objects not scheduled) error. One solution could be to pipe the new frequency to the phasor with a delay calculated from the previous frequency but I have the feeling there must be a more elegant solution to this problem. Anyone got a suggestion? There is a thread in the archive that is adressing a dsp loop issue but the solution proposed dosen't seem to be adapted to my specific problem. Thank you Benef ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re : connecting a samphold and a phasor together
Thank you, I didn't knew about the one block delay. Problem solved very elegantly indeed! Benef De : Jack j...@rybn.org À : Benoît Fortier benoitfort...@yahoo.ca Cc : pd-list@iem.at Envoyé le : Mer 28 avril 2010, 11 h 26 min 41 s Objet : Re: [PD] connecting a samphold and a phasor together I am not an expert in sound but with a [s~] (from [samphold~]) and a [r~] (into [phasor~]), you should avoid dsp loop. [r~] receive with one block delay. Don't know if there is better solution. ++ Jack Le mercredi 28 avril 2010 à 08:03 -0700, Benoît Fortier a écrit : First time on this mailing list, so hello everyone! I started using pd a couple of month ago and I'm completely addicted. Ok I have a simple problem for which I'm looking for the most elegant solution. I need a phasor (in a looping sampler) which frequency can be changed only at the beginning of it's period (when it drops to zero). That's usually the kind of problem a samphold can handle very well but when I connect a phasor and a samphold directly together I get a dsp loop detected (some tilde objects not scheduled) error. One solution could be to pipe the new frequency to the phasor with a delay calculated from the previous frequency but I have the feeling there must be a more elegant solution to this problem. Anyone got a suggestion? There is a thread in the archive that is adressing a dsp loop issue but the solution proposed dosen't seem to be adapted to my specific problem. Thank you Benef ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
