I've had the same problem frequently with GUI-heavy patches. For what it's worth, minimizing & restoring the window will display updated GUIs, but the pixels will continue to be frozen until I minimize & restore again.
After removing about 90% of the GUI objects from one particular patch that did this, I can now use it for hours without any of the display issues.
On Thu, Feb 13, 2014 at 5:37 AM, Billy Stiltner billy.stiltner@gmail.comwrote:
---------- Forwarded message ---------- From: Billy Stiltner billy.stiltner@gmail.com Date: Wed, Feb 12, 2014 at 1:13 PM Subject: Re: [PD] pd gui: partial interface freeze To: Py Fave pyfave@gmail.com
I have the same problem , both recordings I did last night crashed, I think it's the number of objects loaded but might be wrong. First one crashed at about 50 some minutes after I loaded my mandelbox sequencer. If I turn up the BPM that will do it also. The second one I started up with the mandelbox sequencer and ran it for about 30 minutes till it froze completely. I'm not sure how long the controls were froze, the checkboxes still were working but couldnt scroll the record window to stop the recording so I alt tabbed to the terminal and ctrl+Ced the turing tarpit.. luckily I have an auto sail button and the sliders work still even though they are not graphically active, also I can type numbers into numberboxes and adjust with mouse. The audio part works just not the gui. https://archive.org/details/26edonum2
I do have some sort of logical error with the voices - there are things in the patch that make a -1 to send to the main envelope for a ramp down if voice stealing occurs (a voice is still sounding when triggered with a non 0 velocity.) The problem is that it seems that if the release part of the envelope is non 0 it seems as if all notes triggered after a new voice is triggered the releases add up or the audio kinda gets stuck like in "reverb freeze like mode".
On Sat, Jan 18, 2014 at 12:36 PM, Py Fave pyfave@gmail.com 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@xdv.org ub@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@xdv.org mailto:ub@xdv.org <ub@xdv.org <mailto:ub@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@iem.at <mailto:Pd-list@iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list