[PD] vjtools/videogrid was: pd gui: partial interface freeze

[ub at xdv.org]

ok, first i checked and realized i had [change] to most of my hid output.
so i tried without joysticks connected, [0] to [hid] and all metros off. 
froze the interface
within seconds by quickly changing the input to vjtools/videogrid so i 
guess that's the object that's bugging me.
i notice it does other strange things as well, like throw these errors:

image create photo imga1bbe04 -file /tmp/vigrid_4.ppm"
     ("uplevel" body line 1)
     invoked from within
"uplevel #0 $cmds_from_pd".pdwindow: no such object

though it seems they appear without an interface-freeze.

also i noticed some time ago, that when you use two instances together, 
they use the tmp/names for the same slots. i tried to hack
some sort of uniqe identifier into the filename but that didn't seem to 
improve things.
i might give that another try ...

is there a usable alternative otherwise. i remember i saw these guys 
ones, which had something like videogrid, made inside pyext or so ...
they said it worked absolute fine.

thanks+cheers,
ub

On 18.01.2014 18:36, Py Fave wrote:
> usb/hid did this if i remember correctly.
>
> i solved it by usind a different build or another object:
> [joystick] but it was on windows
>
> i guess this is a known bug because [hid]  is so useful
> perhaps someone has a better knowing of this .?
> or a workaround .
>
>
>
>
>
>
>
> 2014/1/18 ub at xdv.org <mailto:ub at xdv.org> <ub at xdv.org <mailto:ub at xdv.org>>
>
>     On 18.01.2014 17:07, Py Fave wrote:
>
>         i had the same problems while  using gem objects some time ago
>         it was because of text2d or text3d.
>
>     right. considered parts of gem as the culprit, but then i'm fairly
>     sure i did experience this, before i added text2d and text3d objects
>     and i'm hardly ever running them [0]->[gemhead].
>     i'll give it a shot and remove them.
>
>
>         you can remove some gui stuff too .
>         replacing bng by bang for instance
>
>     since i'm using them only as indicators not buttons, that's not an
>     option. guess i could use data strcuturs for sliders, but
>     that probably opens a new can of worms.
>
>
>         and use [change] on your inputs to reduce the flow .
>
>     i'll do that!
>
>
>         only suggestions , i don't remember what was the problem but i
>         solved it
>
>     good to know, someone has seen it too. thanks!
>
>
>
>
>
>
>
>
>
>
>         2014/1/18 ub at xdv.org <mailto:ub at xdv.org> <mailto:ub at xdv.org
>         <mailto:ub at xdv.org>> <ub at xdv.org <mailto:ub at xdv.org>
>         <mailto:ub at xdv.org <mailto:ub at xdv.org>>>
>
>
>             hey there,
>
>             i've been having this heisenbug for some time and learned
>         to live
>             with it, but having fixed some real bugs on my patch,
>             this is the last one on my list and i'd like to give it a
>         go, but
>             no idea where to start.
>
>             symptoms are:
>             some time into performing (20min to 1h) all the sliders,
>             messageboxes, dials and bangs sort of get stuck,
>             meaning they do not change their display state anymore. i can
>             however still drag and click their active parts
>             and their output will react accordingly, but none of this
>         is being
>             displayed.
>             i should probably mention, that checkboxes still work
>         correctly.
>
>             i had hoped it would go away moving from pd 0.42 to 0.43,
>         but it
>             didn't.
>
>             this is 64-bit linux (ubuntu 12.04), pd-extended (now
>             ubuntu-package, previously
>             self compiled from git)
>
>             speculations include:
>             from a gut-feeling i suspect something like an input
>         overload, ie
>             some input
>             shooting messsages at an insanely high rate, so the element's
>             message queue
>             (if there is such a thing) stops passing things on to the
>         display.
>
>             i also suspect vjtools/videogrid as it messes with the
>         interface,
>             but does have a few issues,
>             like race conditions between thumbnail creation and thumbnail
>             display, esp if there's
>             two of them.
>
>             hid: usb joysticks could maybe freak out and overload the
>             interface inputs
>
>             anyway i can not see any direct connection between what i
>         do and
>             when it happens.
>
>             re-opening the patch doesn't help, only restarting pd does.
>
>             has anyone ever seen (something like) that?
>             any ideas about how to debug, where to look or what to try?
>
>             thanks + cheers,
>             ub
>
>             _______________________________________________
>         Pd-list at iem.at <mailto:Pd-list at iem.at> <mailto:Pd-list at iem.at
>         <mailto:Pd-list at iem.at>> mailing list
>
>             UNSUBSCRIBE and account-management ->
>         http://lists.puredata.info/listinfo/pd-list
>
>
>
>