-
lacuna
posted in technical issues • read morectrl+t for messages, too:
https://forum.pdpatchrepo.info/topic/14071/msg-a-message-object-bug-fixI prefer keyboard over mouse.
Using the shortcuts ctrl+1 or +2 or +3 ect. keeps the flow already being connected.
[bng] [tgl] ect same for GUI objects.In Windows system settings I have activated this shortcut:
zero on number-pad for click-hold. Although I'd prefer a different key, it is very useful in Pd to avoid arm strains.And this looks promising:
Keyboard navigation/patching
https://github.com/pure-data/pure-data/pull/869This one too:
canvas zoom and scroll with mousewheel
https://github.com/pure-data/pure-data/pull/1659(Wish to connect a whole chain easily by simply dragging a cable across several objects/msgs, without the need to release the mouse-button.)
Also: in editmode ctrl+click on GUI, instead of ctrl+e
essential: hold shift + drag on number box
-
lacuna
posted in technical issues • read moreconnections in bezier curves
not in Vanilla, as far as I know, only in other flavours as PurrData, L2Ork or PlugData.
One trick for clean patching is to use the patcher more text-like, with many horizontal lines, as you can see from more advanced users here in the forum (lately here f.e. : https://forum.pdpatchrepo.info/topic/14461/can-an-array-be-used-to-arrange-amplitude-changes/2 )visualize what's going in the chords (which I remember I had in pd-ext)
I never tried, @svanya has made this:
https://forum.pdpatchrepo.info/topic/13046/a-movable-autoconnnecting-vu-meter-esp-for-debugging-codeand something like insert function (insert the block between two objects when dragging), adaptive chords drawing
Not all, but some are available by "intelligent patching"
https://forum.pdpatchrepo.info/topic/13471/shortcut-replacing-wiresedit/production modes
ctrl+e
learn all the shortcuts@oid recommended this, I haven't tried yet:
https://github.com/RVirmoors/maxhotkey-pdhard on PD

-
lacuna
posted in technical issues • read more@whale-av yes, copying a selceted file in win-file-browser does full path in clipboard...
I think sending via pdsend is slick. And I believe and hope and am interested in if Pd receives it without [netreceive].
Otherwise, opening a [netreceive] patch with a startup-flag (in terminal or preferences or in a script) should do the trick:
https://forum.pdpatchrepo.info/topic/13895/opening-a-patch-inside-another-patch-by-filename/2 -
lacuna
posted in technical issues • read moreAlso you could try to
use the terminal to browse,
ctrl+shift+c copy > alt+tab switch over to Pd task > ctrl+o open > ctrl+v paste > enter.At least this works for me with the Windows file-browser and portable Pd.
-
lacuna
posted in technical issues • read moreYour [clone] idea would be the way to go!
@Obineg said in Chords (polyphony) as arrays/lists:if you code your own external at one point you always have to iterate the list into single values.
And have a look into the help-file of [clone]: Adress clone instances with the first number of a list or with
nextin a serial manner.Instead you could send the whole list to
alland in each instance cut-out the snipped of interest by getting the instance-# with [f $1] and cut-out with two [list split]s.Maybe upload your non-working clone-version and we can fix it.
In your hard-coded patch only [mtof] and [phasor~] or only [phasor~] are required to duplicate, - sum all the [phasors~] into one [lop~] ect.
Maybe use [poly], if you like it.
Also, there are many examples of polyphonic synths floating around, in the patch-subforum for example.
-
lacuna
posted in technical issues • read more@ddw_music said:
there is a need for an arbitrary-format [pipe]. Does such a thing exist?
maybe [text sequence]
unpackOSC handles timestamps, but also outputs each message immediately
Ports and networking introduce jitter: the stream out of [netreceive] jitters. This is where timestamps come in handy:
Buffering, and comparing timestamps to a steady (and delayed) clock eliminates jitter. -
lacuna
posted in technical issues • read more@bobpell sounds like a new bug species.
Does it happen 1/4 times by just new patch > save > close > reopen?Please give more info on your screen and GPU setup? Screensaver? Are there other things running doing sth related to the screen?
Does it happen after waking up or hybernating > saving the patch > reopening?
