• nicnut

    I would check the midi settings in Pd to make sure the midi out put is going to the right interface. Depending on the RPi operating system sometimes midi settings and connections are hard to set up.

    posted in technical issues read more
  • nicnut

    @amazingrolo Wow that's great to know! thanks for checking that out.

    posted in technical issues read more
  • nicnut

    @amazingrolo Thanks for this update. Yes it's an annoying problem for sure. I made some really convoluted python script that takes 30 seconds to connect my midi devices and pd. Not very ideal in a live performance setting.

    I did see in the pd facebook group that someone posted what sounds like a great Rpi disc image with a real time kernal. I haven't tried it out yet, but it sounds promising. Here's the link if anyone is interested:

    https://blokas.io/patchbox-os/?fbclid=IwAR0bnDB-rkzJPeWAev8FF4Wjf646fzF0weJH1Pb733AJ7avImPJ7Z9sMKdA

    when I get to it I'll let you know if the there's problems with connecting midi devices.

    posted in technical issues read more
  • nicnut

    hey @robbielongcat and @emviveros. I was thinking about starting another thread on Raspberry Pi and Pure data. This disk image does work great, but I am sort of annoyed at how much work it is to connect Pd and Midi controllers using this disk image. You have to do all these commands in terminal using aconnect ( i've researched this for like months). On my old disk image (Raspian I think) you can just have it set and saved and Pd automatically connects to my midi controller when it opens.

    I was wondering if there are other good OS options for Rpi and Pd. I was going to download a couple and experiment to see if there are any that automatically connect as my old disk image did. If any one has thoughts on this please chime in.

    Nick

    posted in technical issues read more
  • nicnut

    If anyone comes up with anything, I'd love to see how this was worked out.

    thanks, Nick

    posted in technical issues read more
  • nicnut

    @EEight, Oh ok, that's good to know. THanks.

    Also I forgot to mention, I'm on a raspberry Pi. Getting midi messages to Pd is kind of involved, I'm doing some commands in terminal with aconnect. I thought once Pd is connected to my midi controller it would be the same for all instances of Pd, but I guess not. That might be why I can't use ctlin.

    Is it possible to have non audio signal inputs in a Pd~ object? The only inputs I've been succesful with are adc~

    posted in technical issues read more
  • nicnut

    Hi,

    I am new at using the Pd~ object, so forgive me if this is a super basic question. I have a pd~ object with a filter in it. I want to use my midi controller to use this filter, and i have some ctlin objects in my patch (that is in the Pd~ patch) and they aren't responding to midi. In the parent patch the midi is working fine. Is there some trick to this? I can try send and receive, but I was wondering what the best way is.

    Also, I was going to put all my audio effects in Pd~ patches. Is it OK to have like 10 different Pd~ windows open? It would be a lot of terminal windows too, that's why I am asking.

    Thak you for any insight into these issues.

    posted in technical issues read more
  • nicnut

    Hey Everyone. I finally figured this out.

    For me sending a message with: pd~ start pd~-mypatch.pd didn't work for some reason. I had to send my message as: pd~ start mypatch.pd I don't know if the help file should be changed, but thank you to @EEight for your example image.

    Also I am using 2 channels of audio in/out. inside the patch that my pd~ object is opening I had to have an [adc~ 1] and [adc~2] to get the audio in. I was trying to use inlet~ or just two adc~ objects and that wasn't working.

    To get audio out I needed [dac~ 1 2] instead of an outlet~ or just dac~. I thought dac~ would work because that has left and right. I also had to have a load bang inside the patch that pd~ is opening that starts the audio.

    Anyway, I have something working. Now I'm gonna divide up all my patches.

    Thank you all for your help.

    posted in technical issues read more
  • nicnut

    Hi everyone,

    thanks for your replies. The problem I am having is that I can't open a separate patch with the pd~ object. I was thinking I would put my audio delays and reverbs (audio effects in general) in a pd~ patch to start. But I can't open a patch with pd~. Do you create a patch with inlets and outlets, store it in the same folder as the parent patch, then send the pd~ a message like "pd~ start -mypatchname.pd" ? Because that isn't working for me.

    When I send "pd~ start -mypatchname.pd" to pd~ object a new terminal window opens. I can't get audio into or out of a pd~ object, I can't view what's happening in mypatchname.pd, and I can't tell if it even opened that patch. If someone can just explain how this works I'd appreciate it.

    thanks.

    posted in technical issues read more
  • nicnut

    sptest.pd

    sp3.pd

    hi,

    I have some questions about the pd~ object. My Raspberry Pi 3 has one processor running at 100% and the other 3 running at almost 0%. So I’d like to allocate some processing power to those other processors. I’m guessing that’s what the pd~ object is for correct?

    If I have an audio signal and I go into the inputs of a pd~ object will all the processing above that pd~ object be allocated to another processor? Or do I need to make a separate patch and open it with the pd~ object, and everything in that patch is run on another processor?

    Or if I send audio into a pd~ object and have reverb and delay effects happen in a subprocess, would just those effects be created on a different processor?

    I read this document:

    http://www.pdpatchrepo.info/hurleur/multiprocessing.pdf

    which explains the concept behind why the pd~ object is necessary. And I looked at the pd~ help file, but I can’t get this to work.

    I uploaded some of the things I tried out. If anyone can alter these to demonstrate how this object works I’d appreciate it.

    thanks, Nick

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!