• jameslo

    @hwathwy Well if you have a chance, post what you've tried and why it doesn't meet your requirements. I gotta step out for a few hours but maybe someone else can help you in the meantime.

    posted in technical issues • read more
  • jameslo

    @hwathwy Yeah, I'm amazed too, but not with myself, and not in a good way :)

    posted in technical issues • read more
  • jameslo

    @hwathwy Wow, I'd love for someone to explain/defend this behavior because to me it's not good. Why should the behavior of [text get] be different for the same text, dependent on how it was entered? What state is being hidden? Anyhow, I found that the set method for [text define] works more as I would expect, try it and let us know if it works for you.Screenshot 2026-09-28 174912.png

    posted in technical issues • read more
  • jameslo

    I figured it out! My last post with a screenshot and instanceIDService3.zip can be made to work with plugdata by replacing [tcpclient] with [netsend -b]. In my previous tests I overlooked that [tcpserver] requires binary mode.

    posted in technical issues • read more
  • jameslo

    @jamcultur Oh! I didn't know one could change an application's priority, thanks.

    posted in technical issues • read more
  • jameslo

    @ddw_music But couldn't it also be that Pd didn't empty the queue fast enough, either due to Pd being busy doing something else, or Pd not getting enough CPU cycles?

    posted in technical issues • read more
  • jameslo

    @ddw_music I tested with multiple Pd processes on Windows and got the same behavior, but my point was: if this is a Pd behavior and there's nothing about running as a plugin that forces one to rewrite the networking facilities, then what can the plugdata team do about it?

    posted in technical issues • read more
  • jameslo

    @jamcultur I always turn off all networking when running a show or use a subnet that no one else can access. Maybe note the time when it happens again and then look at the Windows logs to see if anything unusual happened at that time (search "event viewer")

    posted in technical issues • read more
  • jameslo

    @jamcultur Do you have MIDI Real-time messages flooding in? Does your patch ever get really busy doing something so that it can't dequeue incoming MIDI events in time? Are you generating bursts of dense MIDI for output? Are there other applications or services running on your computer that steal CPU cycles from Pd? (If you're on a Mac, QLab has a great sheet explaining how to turn off all the things that might interfere with your show)

    Maybe try increasing the delay time in audio settings?

    posted in technical issues • read more
  • jameslo

    OMG, I'm gonna poke my eyes out. I just updated REAPER from 7.79 to 7.80 and the TCP closing issue changed. The connections still close more slowly than expected, but they at least close now.

    posted in technical issues • read more

Internal error.

Oops! Looks like something went wrong!