• ricky

    This also fixed a related error that cropped up in Audacity, too. This 'solution' makes little sense to me.

    posted in technical issues read more
  • ricky

    @danielsomar - you're not wrong. I had some development plugs from a friend on my machine. I deleted those and that solved the issue. In my case, the issue was some AU devices.

    posted in technical issues read more
  • ricky

    Hi @coco. Your solution fixed my problem. This isn't ideal but Pd is working the way it should. How do we repair/reset/amend user privileges on our existing user accounts, I wonder? I flagged this with Miller.

    posted in technical issues read more
  • ricky

    @Coco Did you recently upgrade your OS?

    posted in technical issues read more
  • ricky

    Might try that! Thanks for the lead, @coco.

    posted in technical issues read more
  • ricky

    Yes, no matter what I/O configuration. I get this error consistently. I reported it to the list and I think the devs are incorporating a change;

    posted in technical issues read more
  • ricky

    Can't seem to add an array to a patch, @jancsika.

    posted in news read more
  • ricky

    @ezequielabregu said:

    [expr~ $v1/$f2*2-1]

    What is $f2 in this expression? The result of [expr pow(2, $f1)-1]? I tried your implementation but it doesn't sound quite right so I think I am not interpreting your signal flow correctly. Can you clarify, @ezequielabregu ?

    posted in abstract~ read more
  • ricky

    And, FWIW, I never received a pop-up asking to grant permission to anything at any point.

    posted in technical issues read more
  • ricky

    I only started experiencing this when I upgraded Pd to 0.51. Prior versions worked fine under Catalina.

    posted in technical issues read more
  • ricky

    @beep-beep - I'm getting "error opening audio: Internal PortAudio error" on Catalina, which I believe is related to permissions. What is the process for granting permission for microphone, as you have described above? Thank you in advance.

    posted in technical issues read more
  • ricky

    I thought this might be solved by the variety of solutions offered up online including granting permissions via terminal and deleting .plists but neither has worked for me. I also can't use Audacity I suspect because of the same issue. Anyone any ideas?

    posted in technical issues read more
  • ricky

    I'm having the same problem on Catalina.

    posted in technical issues read more
  • ricky

    @alexandros The Pi is not being restarted, no, although that could be one bandaid solution if I script a restart to reinitialize the patch after a defined period of time. A complete restart of the Pi is currently the only way to fix the issue. At the moment, the audio just ceases to work after a period of a few hours. Super weird. Oh, and I tried to remove the sleep flag but it seems to be a necessary delay for Pd to get up and running. I guess the OS needs time to get into shape to handle all things audio.

    @whale-av I don't think it's a Pd issue either. The patch is still up and running, receiving data over a network from the Arduino, and general functional/editable but no dice on the audio front so it's likely that it's specific to Linux. Thanks for the pointer to ALSA resources/issues. I'll have a dig and see what I can find. I don't know if this has any bearing but I am using a little Behringer 2 -channel interface.

    posted in technical issues read more
  • ricky

    [sigmund~ notes] - give it a go! You could also try [sigmund~ pitch env] and use the latter for additional thresholding.

    posted in technical issues read more
  • ricky

    Hi, all. I'm curious: will the Xbox Kinect V2 work with this approach or is this the same deal as before where I need dedicated Windows hardware to do some tracking? I've been totally out of the loop on this stuff for years so I'm curious if anything has changed in that regard.

    posted in technical issues read more
  • ricky

    @Butahuruf Hey! Actually, I totally forgot that [sigmund~] has a notes flag that will report on any given note event instead of a continuous stream of pitch data. You should use that.

    posted in technical issues read more
  • ricky

    Cool. I like the sound of this project. I'd love to see a video!

    posted in patch~ read more
  • ricky

    @gmoon Interesting. Not sure on the conventions regarding zero padding - I thought switch~ took care of all that for you in Pd, no? It is conventional to have either an IIR or FIR depending on your needs in terms of latency and phase distortion. Not something I've really pursued in Pd either. lop~ should definitely hit the CPU less than vcf~, correct. vcf~, if memory serves, is better suited if you want access to real and imaginary parts but could be consider band and low-pass outputs respectively.

    posted in patch~ read more
Internal error.

Oops! Looks like something went wrong!