purr-data issueshttps://git.purrdata.net/jwilkes/purr-data/-/issues2020-05-24T16:06:00Zhttps://git.purrdata.net/jwilkes/purr-data/-/issues/590array name should be inside the array to provide a more predictable bbox calc...2020-05-24T16:06:00ZIvica Bukvicarray name should be inside the array to provide a more predictable bbox calculation and keep consistency with 1.0 branchKeeping it where it is now limits array's utility for visualization purposes--its bbox detection is not accurate (at least not in vanilla) as it does not factor in the label. Perhaps this should be one of the additions to the -legacy fla...Keeping it where it is now limits array's utility for visualization purposes--its bbox detection is not accurate (at least not in vanilla) as it does not factor in the label. Perhaps this should be one of the additions to the -legacy flag to support both vanilla and new behavior, even though outside the bbox inconsistency it should not have any major impact on the compatibility/operability. Long-term-wise this may be also something that can be repositioned?https://git.purrdata.net/jwilkes/purr-data/-/issues/849Ask for saving the patch when the user closes an edited patch2022-02-28T09:48:39ZPrakhar AgarwalAsk for saving the patch when the user closes an edited patchWe can ask the user to save the edited patch before closing it to avoid any unintentional data loss.We can ask the user to save the edited patch before closing it to avoid any unintentional data loss.https://git.purrdata.net/jwilkes/purr-data/-/issues/504attempt to upgrade OSX runner and use valgrind with it2019-01-31T02:28:08ZJonathan Wilkesattempt to upgrade OSX runner and use valgrind with itGo ahead and try to upgrade OSX runner to mojave.
If it works, try making valgrind a requirement in the CI instructions. Then track down any memory errors that valgrind catches.Go ahead and try to upgrade OSX runner to mojave.
If it works, try making valgrind a requirement in the CI instructions. Then track down any memory errors that valgrind catches.https://git.purrdata.net/jwilkes/purr-data/-/issues/594Attempting to open subpatcher twice in a short period of time on Windows crea...2020-03-23T20:54:24ZIvica BukvicAttempting to open subpatcher twice in a short period of time on Windows creates a ghost windowhttps://git.purrdata.net/jwilkes/purr-data/-/issues/30audio devices aren't preloaded in prefs2018-01-07T17:58:17ZJonathan Wilkesaudio devices aren't preloaded in prefsThe Audio preferences tab doesn’t preload the devices. When first launched, the drop down boxes are empty then suddenly fill & adjust the layout.The Audio preferences tab doesn’t preload the devices. When first launched, the drop down boxes are empty then suddenly fill & adjust the layout.https://git.purrdata.net/jwilkes/purr-data/-/issues/402audio dropout while opening subpatches with lots of elements2018-01-09T06:50:31ZXRoemeraudio dropout while opening subpatches with lots of elementsThis might not be a real issue, but it's annoying, not to have the possiblity to open rich subpatches while playing. Bad response / high cpu usage of the gui seemes to be a general problem of pd and Purr Data. I wonder if there's any cha...This might not be a real issue, but it's annoying, not to have the possiblity to open rich subpatches while playing. Bad response / high cpu usage of the gui seemes to be a general problem of pd and Purr Data. I wonder if there's any chance to change that behaviour in future?
I attached a file with 8 sequenzers, which are initially hided and can be opened one by one. Opening one of them causes audio dropouts. I tried this file with vanilla also where it causes audio dropouts as well, but Purr Data is much worse than vanilla.
On vanilla I've installed these libraries to make the patch work:
cyclone,iemguts,zexy,iemlib,moonlib,hcs
[sequenzer.zip](/uploads/950fa4ae32ac9efec8a4e6a8867175ae/sequenzer.zip)
win7/win10, pd 48.1.test3, PurrData 2.4.6https://git.purrdata.net/jwilkes/purr-data/-/issues/472Audio multi-channel configuration not saved2018-05-19T14:31:54ZOlivier Van RompuyAudio multi-channel configuration not savedI compiled the latest build and tried to setup jack (for my ES-8).
There are 2 problems :
First of all when i configure an alternate channel amount then 2 for input/ouput it is not persistently saved. I even tried to change the config in...I compiled the latest build and tried to setup jack (for my ES-8).
There are 2 problems :
First of all when i configure an alternate channel amount then 2 for input/ouput it is not persistently saved. I even tried to change the config in the .purr-data/user.settings without luck
The config file seems to be adapted correctly, but the application seems to ignore the values.
Also something is wrong with the jack channels.
If I adapt the config to 12 in/ 16 out
Patchage always shows the original 2in/2out remain and on top of that 12in/16out is added. The original 2in/2out channels should be removed. This would make alls dac/adc automatically connect to my ES-8 channels in jack.https://git.purrdata.net/jwilkes/purr-data/-/issues/682Auto-complete feature in Purr Data2020-09-11T21:28:56Z60-hzAuto-complete feature in Purr DataPurr Data still miss one great feature which is auto-complete for objects boxes.Purr Data still miss one great feature which is auto-complete for objects boxes.https://git.purrdata.net/jwilkes/purr-data/-/issues/415Automatic adjustment of width 0 number widgets stopped working2018-02-12T01:51:27ZAlbert GräfAutomatic adjustment of width 0 number widgets stopped workingThis seems to be a new regression in 2.4.9, what I can say right now is that 2.4.7 doesn't exhibit this issue. (Currently building 2.4.8 so that I can confirm that it's in 2.4.9.)
Here's a screenie from 2.4.9:
![image](/uploads/fc44a09...This seems to be a new regression in 2.4.9, what I can say right now is that 2.4.7 doesn't exhibit this issue. (Currently building 2.4.8 so that I can confirm that it's in 2.4.9.)
Here's a screenie from 2.4.9:
![image](/uploads/fc44a09931f1ed992f7f4592181a0786/image.png)
Here's how it's supposed to look (screenshot from 2.4.7):
![image](/uploads/6ff799837e8faf09833afb60f9645707/image.png)
Note how the widget automatically resizes, which is what it's supposed to do when it has zero width.
Neither the main window nor the dev console shows any errors. Maybe some more fallout from the GUI refactoring?https://git.purrdata.net/jwilkes/purr-data/-/issues/269automatically calculate actual font sizes for arbitrary fonts at startup2017-10-16T12:25:44ZJonathan Wilkesautomatically calculate actual font sizes for arbitrary fonts at startupCurrently we're using some hard-coded pixel font sizes in the GUI tailored to fitting DejaVu Sans Mono exactly into the maxwidth/sizes listed in sys_fontlist of s_main.c. By ignoring the fi_width and fi_height members on the C side, we ...Currently we're using some hard-coded pixel font sizes in the GUI tailored to fitting DejaVu Sans Mono exactly into the maxwidth/sizes listed in sys_fontlist of s_main.c. By ignoring the fi_width and fi_height members on the C side, we guarantee pixel-exact object/message/atom box sizing across all platforms.
This means that boxes aren't guaranteed to tightly fit around the text. For example, on Ubuntu 16.04 the font engine changed and happened to make DejaVu Sans Mono wider than previously. When we made a special hard-coded fix, it turned out that there is no pixel size that corresponds exactly to the previous size-- the new font engine quantizes the pixel sizes in a way that is incompatible with the previous font stack. So a message/object box with a long string of text in it under Ubuntu 16.04 will have some space left between the right edge of the text and the right side of the object box.
This may seem like a bug, but it's actually a feature. It prevents users under Ubuntu 16.04 from positioning boxes so tightly horizontally (or vertically) that they create collisions for users on the other systems.
To be able to support this for arbitrary fonts, we need to expand the HTML5 canvas font measuring trick in pdgui.js. Essentially, I think we need to do the following:
1. start with a suitably small actual font size guaranteed to fit the sys_fontlist spec.
2. write it to the HTML5 canvas and check if it fits into the maxwidth/maxheight for that sys_fontlist size
3. if it fits, double the actual font size and goto step 2
4. if it is too large, then make a "vice grip" with the current actual font size and the last known actual font size that fits
5. find the mid-point of the "vice grip" and goto 3
Now, figure out a reasonable number of times to loop 3-5. At the end of it, find the last known actual font size that fits and use that for the corresponding Pd font dialog size.
Then do the same thing for each other Pd font dialog size.https://git.purrdata.net/jwilkes/purr-data/-/issues/374automatically encapsulate in a subpatch2017-10-03T17:11:51ZAlexandre Porresautomatically encapsulate in a subpatchhi, what's the shortcut to automatically encapsulate a part of your patch as a subpatch in purr data?hi, what's the shortcut to automatically encapsulate a part of your patch as a subpatch in purr data?https://git.purrdata.net/jwilkes/purr-data/-/issues/5autopatching a new box requires two clicks to instantiate2020-06-05T15:22:16ZJonathan Wilkesautopatching a new box requires two clicks to instantiate1. create an object like `[float]`
2. select it.
3. click `<ctrl-1>`. An empty box is created and selected below the `[float]`.
4. Click on an empty part of the canvas.
Bug: clicking on an empty part of the canvas fails to instanti...1. create an object like `[float]`
2. select it.
3. click `<ctrl-1>`. An empty box is created and selected below the `[float]`.
4. Click on an empty part of the canvas.
Bug: clicking on an empty part of the canvas fails to instantiate the empty object. You have to click again to instantiate it.
Jonathan WilkesJonathan Wilkeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/148autotips not implemented yet2017-10-16T12:24:19ZAlbert Gräfautotips not implemented yetWould be nice to have that as well. Currently it just pops up a dialog box saying "Please implement this".Would be nice to have that as well. Currently it just pops up a dialog box saying "Please implement this".https://git.purrdata.net/jwilkes/purr-data/-/issues/493autotune~ uses float instead of t_sample2019-03-03T17:11:09ZJonathan Wilkesautotune~ uses float instead of t_sampleLooks like `[autotune~]` hard-coded `float` in some places instead of `t_sample`.
Fix this and test to make sure the algo itself doesn't depend on any single-precision float bitmath or anything else like that.Looks like `[autotune~]` hard-coded `float` in some places instead of `t_sample`.
Fix this and test to make sure the algo itself doesn't depend on any single-precision float bitmath or anything else like that.https://git.purrdata.net/jwilkes/purr-data/-/issues/189bad help file for [output~] in extra / new abstraction suggestion2017-10-16T12:24:19ZAlexandre Porresbad help file for [output~] in extra / new abstraction suggestionI see in pd-l2ork / purr data 3 [output~] objects; two are the same and come from vanilla: one in "3.audio examples" and another in "4.data structures". These both have no help file, but there is the A05.output.subpatch.pd file in 3.audi...I see in pd-l2ork / purr data 3 [output~] objects; two are the same and come from vanilla: one in "3.audio examples" and another in "4.data structures". These both have no help file, but there is the A05.output.subpatch.pd file in 3.audio examples. This should probably just stay as it is...
Then in the "extra" folder there's another version from pd extended. This object is the one that gets called if you type its name in an object box! The help file for this one - found on the same extra folder - is really poor and is the same help file you find in extended. But then, we find another and better help file for in "5.reference" - this help file is nice!!!
But there is an inconsistency here with help files, because you still have the other one (which is bad), and this other one is the help file that opens when you right click and ask for help. Also, if you are on the nice help file and click on help for the object, the poor and bad help file comes up...
So, I suggest getting rid of the bad help file and replace it with the good one, which seems to be sitting somewhere else and not getting called upon.
Another suggestion would be to include a new output~ abstraction I worked on and that I'm using for cyclone. It offers more features than the existing [output~] found in purr data's extra.
I hated one thing the most in the [output~] abstraction and had to change it: it uses the terrible log scale from the slider, if you use it in a performance you'll notice how the sound will appear strongly at the first value: Bad! I got rid of that and put it with a quartic scaling by default, but also allowing dB scale (as in the output~ abstraction from vanilla).
find it attached,
cheers
[output.zip](/uploads/fefcde9c2b55aba3c8a30de5e84a4b10/output.zip)https://git.purrdata.net/jwilkes/purr-data/-/issues/378Bad install?2017-11-08T14:05:34ZMike HukinsBad install?I've had zero luck with installing Purr.
I've tried the last three versions for windows and each one comes out with the same few major issues:
objects don't appear until blank canvas is clicked
cannot see text whilst typing name in
cann...I've had zero luck with installing Purr.
I've tried the last three versions for windows and each one comes out with the same few major issues:
objects don't appear until blank canvas is clicked
cannot see text whilst typing name in
cannot put spaces in object boxes to give arguments
cannot get out but from bang objects.
this is after only a few minutes of testing so there could well be more issues but it seems like I'm just missing something pretty big.
Any ideas? I'm on windows 10 ver.1511https://git.purrdata.net/jwilkes/purr-data/-/issues/186bad linebreak in canvas properties2017-10-16T12:24:19ZAlbert Gräfbad linebreak in canvas propertiesThis only affects the German translation (see screenshot below), but is easily fixed by a judicious use of `<nobr>...</nobr>`. (Merge request will follow.)
![canvas-props-de](/uploads/74da8e327a61e93b2cb4a2108ae35ecb/canvas-props-de.png)This only affects the German translation (see screenshot below), but is easily fixed by a judicious use of `<nobr>...</nobr>`. (Merge request will follow.)
![canvas-props-de](/uploads/74da8e327a61e93b2cb4a2108ae35ecb/canvas-props-de.png)https://git.purrdata.net/jwilkes/purr-data/-/issues/470behaviour of [pow] for nans2018-09-13T19:31:01ZAlexandre Porresbehaviour of [pow] for nanshi, I'm checking this discussion https://lists.puredata.info/pipermail/pd-list/2013-04/102309.html
and I agree that there should be no special handling of this case, and that it should output nan instead of 0, like expr doeshi, I'm checking this discussion https://lists.puredata.info/pipermail/pd-list/2013-04/102309.html
and I agree that there should be no special handling of this case, and that it should output nan instead of 0, like expr doeshttps://git.purrdata.net/jwilkes/purr-data/-/issues/659Better touchscreen support2020-07-17T21:09:19ZAlbert GräfBetter touchscreen supportOur current OOTB experience on touch screens is not very good, to put it kindly. :) You can select menu entries and click on objects, that's about it. But if you're using a touchscreen, you also want to be able to operate GUI objects, dr...Our current OOTB experience on touch screens is not very good, to put it kindly. :) You can select menu entries and click on objects, that's about it. But if you're using a touchscreen, you also want to be able to operate GUI objects, drag around objects, draw a rubberband to select a range of objects, etc., which currently doesn't work at all with the default touch support that the OS and/or nw.js offer.
This probably isn't straightforward, because mouse event handling needs to be modified in our GUI code. But having proper touch support would certainly be a big improvement, if not a killer feature, especially when running Purr Data on convertibles, as well as in teaching on a digital whiteboard (I actually have one of those in our MIDI lab, which works without a hitch on Linux). So can we please have a go at this?
I have no idea how to do this myself, but over at my Purr Data Github mirror, spidercatnat has submitted a [pull request](https://github.com/agraef/purr-data/pull/15), still WIP, which already has the basics implemented. ATM, this still has some bugs and is based on a pretty old (around 2.10.0) revision, but it rebases easily on the current master, you can find that in my [copy of spidercatnat's branch](https://github.com/agraef/purr-data/tree/touch-support-master) on Github (of course, I can pull that over to Gitlab if anyone here wants to play around with it).
It would be great if someone who knows this stuff better than me could lend spidercatnat a helping hand, so that we can make this work. (I suspect that it's Ico's branch which gives trouble trying to merge spidercatnat's work with HEAD right now. But that's hopefully not a big deal. I'm willing to do the grunt integration work, with a bit of help from Ico if needed.)Albert GräfAlbert Gräfhttps://git.purrdata.net/jwilkes/purr-data/-/issues/566Bigger Cross size inside small [toggle]2019-11-22T00:33:05ZJoseph GastelaisBigger Cross size inside small [toggle]Hello Jonathan,
Is it possible to increase the size of the cross (x) inside the small [toggle] for improving user's readability? See attached files.
Thank you. Joseph
[prd_toggle_cross-size.pd](/uploads/70e44c819d8cc719bcb9ffefd95cf42...Hello Jonathan,
Is it possible to increase the size of the cross (x) inside the small [toggle] for improving user's readability? See attached files.
Thank you. Joseph
[prd_toggle_cross-size.pd](/uploads/70e44c819d8cc719bcb9ffefd95cf424/prd_toggle_cross-size.pd)
![mdre+034](/uploads/140586832bfcc19ae53ec71b4239214f/mdre+034.png)