• Xeno

    Hi,
    i have some problems with the netsend~ and netreceive~ objects from Remu. I'm using pd extended 0.43.4

    I build two patches (client and server) for voice communication with several abstraction using dollar signs etc..
    The first patch (client) records audio on 8 channels with the [adc~] object after pushing a Press-to-talk button (PTT) and sends this signal with [netsend~] to the second patch (server). This second patch checks some conditions and sends the signal to other clients. The client receives the signal and sends it to a [dac~] object.
    In the beginning of this project I connected everytime I pressed the PTT and disconnected when I released the PTT. Pressing the PTT and connecting caused often errors from [netsend~]:

    • (Tcl) Invalid Command Name " " while executing; with different commands inside the "". Sometimes it was a part of the IP-Adress, the port, parts of other words like "ted" from connected or something different
    • Sometimes I got the Tcl error: bad option " itemconpdtk_text_set": must be addtag,bbox,bind,canvasx,canvasy,cget,..... while executing

    The results of this errors where a frozen GUI (number boxes and Sliders didn't change) or pd crashed.

    • (Tcl) missing close brace while executing. After this errror I had to kill Pd because nothing worked anymore...

    I couldn't find the reason for the errors so I changed the patches. Now [netsend~] connects directly when the patch opens. But sometimes the "invalid command name" error appears anyway and the GUI freezes, so I had to restart the patch.

    Another problem is an error from the [netreceive~] object while sending an audio signal over the network:

    • recv data: message too long (10040) or recv tag: message too long (10040)
      it is independent of the chosen format or blocksize. Everytime it happens the sound interrupts. It's not that bad, but sometimes there comes a block of errors and the sound interrupts for a hole second or more, which is disturbing.

    So I hope someone understands what i wrote and maybe someone had similar problems.

    Tanks for helping.

    posted in technical issues read more
Internal error.

Oops! Looks like something went wrong!