Hi, thank you for pointing me in the (obviously) right direction.
As you all suggested, I'm also pretty sure that my LOCALE situation was the root of this evil ;-)
It actually turned out that there was a mixup of english/german in my locale settings (don't know how that happened, though) and i reset it.
Up until now (I'm still working on the patch) no more bugs happened, so i hope that this issue is solved. If not, I'll be back ;-)
Thank you all !
Best
Oliver
Dan Wilcox wrote:
Can also try forcing the locale before starting pd. See the readme in theo's source /po folder which mentions this lower down.
enohp ym morf tnes
Dan Wilcox danomatika.com robotcowboy.com
On Jun 8, 2025, at 6:37 PM, Antoine Rousseau antoine@metalu.net wrote:
Hi it really looks like a "locale" issue, where "0.1" gets encoded "0,1". Likely one of the externals the patch is using (vstplugin?). List every externals (send the list here) and try removing them one by one and retry saving the patch each time.
Le dim. 8 juin 2025 à 11:17, oliver <oliver@klingt.org mailto:oliver@klingt.org> a écrit :
Hi, dear list ! I'm growing slightly desperate as i recently encountered a weird bug in PD 0.55-2 on a LUUNTU 24 system that i can't seem to track down no matter what i try. Here's the outline: After a while of working on a patch, without any reason or reproducable scenario, PD starts to save patches converting commas to colons. Re-opening such a "wrong formatted" patch of course produces a lot of errors, f.e. in message boxes that i use for loadbang stuff. So, something like: [; foo 0.0345; bar 4.567; me 0.001;( becomes just [; foo 0( omitting all the rest of the message And i get an error in the console: canvas: no method for 'float' Repairing such patches of course is a long and cumbersome drag (because it's not immediately noticeable when this bug starts to kick in, only on patch re-opening). ===================================================================================== My patch is very big and involved (has lots of abstractions), so i won't post it here. First i thought it had something to do with an abstraction that used data structures quite heavily, which occasionally threw some errors. But i already removed that part from my patch. I am using a lot of "write" and "read" stuff in my patch (mostly [text]s, but also .fxp/.vstpreset files with [vstplugin~]. I can't seem to find any weird stuff going on in my patch that could lead to this bug. I have never experienced this before and i am beginning to think that either my computer or my system is messed up. But just before i throw it out of the window: Has anyone any idea what's going on here ? Or experienced something similar to this ? Best Oliver --- pd-list@lists.iem.at <mailto:pd-list@lists.iem.at> - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/5RHGAXNDWIY43HUBOVDWPT2GFX3RJEDC/ To unsubscribe send an email to pd-list-leave@lists.iem.at <mailto:pd-list-leave@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
pd-list@lists.iem.at - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/36AFRN2RE2...
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/