• jameslo

    @tungee Thanks. What's going on with the rightmost [bob~] instance? Should it's attenuated output be connected to the outlet?

    posted in technical issues read more
  • jameslo

    @oid I was afraid to reach that conclusion, but you make a strong case. I wonder if [audiolab/pp.ladder~] is closer?

    @bocanegra He he he....

    posted in technical issues read more
  • jameslo

    How would you configure and use [bob~] to demonstrate what the ladder filter fuss is all about? For some reason (inexperience? poor taste?) I keep returning to [vcf~].

    Edit: after an hour or two of monkeys at the typewriter, I'd say that the 2 main differences from [vcf~] are the roll-off slope ([bob~] never completely mutes signal even when the cutoff freq is 8 hz) and the resonance sounds brighter and grittier (bob at resonance 3 sounds like vcf at q 22 to me). There's got to be more to it than that, right?

    posted in technical issues read more
  • jameslo

    @lysergik iemlib has both Bessel and Butterworth filters in many configurations, and you could make your own Linkwitz-Riley with the latter. Go to Help->Find Externals and enter "iemlib".

    posted in technical issues read more
  • jameslo

    @Booberg Yes, I definitely hear it, and I've posted on a similar thing which I thought you weren't supposed to be able to hear (the relative phase of saw partials). And it's not just subjective--I built a double-blind randomized test which I consistently pass with a high confidence level.

    posted in Off topic read more
  • jameslo

    @olisaintpierre It might be simpler to use TouchOSC on the phones and having them connect to a single instance of the patch running on a shared computer.

    posted in technical issues read more
  • jameslo

    @nicnut I was just amending my post to say that there's nothing inherently wrong with putting a threshold trigger at, say, 0.5 on the rising slope, it's just that I often see people putting it as close to 1 as they can so as to trigger just before the phasor resets, and that seems unreliable to me.

    posted in technical issues read more
  • jameslo

    @nicnut [phasor~] only goes from 0 to 1 (at most, usually from a little over 0 to a little less than 1) so your signal will never trigger the upper threshold of 1. If it were me, I would trigger on the downward slope rather than the upward slope since it's more reliable and easier to detect. Try [threshold~ 0.6 0 0.5 0] and take the bang from the right outlet.

    posted in technical issues read more
  • jameslo

    @whale-av David, in the help patch for [netreceive] there is an option for specifying IP address for use with multicast. Could that be used? (I don't know what multicast is....)

    posted in technical issues read more
  • jameslo

    @ddw_music +1 to [makefilename], but in instances where I also want to stop Pd from truncating my float, I prepend an escaped space to force Pd to treat the string of numbers as a symbol. [f] is happy to convert it back to a number when needed.
    Screenshot 2021-07-31 082944.png

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!