• francis666

    thats very encouraging! did u get any sound? if so would u mind sharing the patch so i could try it?

    posted in technical issues read more
  • francis666

    thanks, pardon me for not detailing but i am running pd headless and monitoring it from the terminal via ssh, as far as i know the sub process does not have to have the dsp turned on, the super process (mother patch) should - at least this is how its documented in the help patch. none the less i tried it and it does not make a difference - while the mother patch works the sub process is not, so if any one ever had success do so ill be happy to hear.

    posted in technical issues read more
  • francis666

    anyone ever used pd~ sub process on rpi? works ok on mac but no matter what i do i dont get sound when i run it headless on my rpi 3

    thanks!

    posted in technical issues read more
  • francis666

    very hard to say without looking at your code but i would guess that its either on the arduino side (inefficiant code, using delay etc) or maybe your baud rate settings dont match?

    posted in I/O hardware diyread more
  • francis666

    6 month and much more understanding of the command line later,
    actually the combination of while ! aconnect device name:port device name:port; do sleep 1; is the the most reliable because it repeats until actual connection is made
    setting a fixed delay time might work on one system but not on the other, plus it guarantees the least possible waiting time

    posted in technical issues read more
  • francis666

    @nicnut thats pretty weird, im doing the same and its almost instantaneous, do you aconnect by name or port nr? alternatively what you could do is merge your patches into one big patch with pd~ instances and turn parts of the patch on and off remotely to save cpu, or you dig into the undocumented pd msgs, im sure there is a way to tell pd to close a patch and load another one

    posted in technical issues read more
  • francis666

    @francis666 ok i realize now that array is obviously not audio/pcm format and saves 32bit. that clarifies this!

    posted in technical issues read more
  • francis666

    what you could do is first kill the running instance with "killalll pd" or "sudo killall pd" and then open the new patch

    posted in technical issues read more
  • francis666

    hey there, stumbled upon a weird behaviour, if i load a soundfile of 5mb to an garray and enable save content, the size of the saved patch is 14mb, is there a reason for this? the size of the patch without the array is 256bytes. is there any way to fix this?

    thanks!

    posted in technical issues read more
  • francis666

    same for me on 0.49, was on 0.48 also, not related filename space, only crashes on "save as" tho so its annoying but not fatal (it does save before crashing)

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!