On 29 March 2011 14:46, David Griffiths <[email protected]> wrote: > Hi Kassen, > > I haven't noticed this, tempted to say it's a jack thing.
Ok. I'm not that bothered by it; it's kinda ok as a notice that Fluxa managed to connect to Jack. I believe that the mackports jackd isn't held in especially high regard for stability and on top of that the "G4 factor" probably doesn't help. > The extra > zeroing is probably a mistake, I will investigate. I suspected it was either that, or that you too ran into this "beep" and tried to fix it. It's not used anywhere else like that, except, I think, in one instance relating to sample playback. > I will also attempt > to answer some of your questions - but generally many thanks for taking > up the cause and hacking fluxa! > > Happy you like it. I feel a bit better about it all now that we have the "branch" thing where I can experiment to my heart's content while syncing the G4 and my own desktop without bothering anyone too much. When you have a bit more time we should probably talk a bit about some overall strategy. I'm trying to follow the standards you set, but I'm not sure I agree with all of it. For example; the CV for distort gives more distortion for a lower value. That's IMHO counter-intuitive and I don't think that plays nice with ADSR. Also; I just committed a fix to the durations of ADSR and the duration of ramp; those could be negative which gave weird results, especially in ADSR. I applied a fabs, which I predict will be more fun than discarding negative values in the unlikely case of arguments that are nodes. Overall; I hope some of my stuff is useful to you, and maybe more people will come out & play. Yours, Kas.
