Line~ only two pairs in message , right ?
@ddw_music said:
The reference panel says "Origin: cyclone." This tells you that it did not load the vanilla [line~] object -- it loaded the one from cyclone, which is modeled after Max's [line~], which does accept a series of breakpoint pairs.
hjh
It does not accept multiple pairs , even the cyclone one.
This should go to 1 instantlly , to 0 in 200ms, back to 1 in 100mS and back to 0 in 100 ms
It doesn't
As a matter of fact , I think the reference to cyclone is just wrong , because pure data vanilla loads it fine and I don't have any externals at all
Methods for 1 unit sample feedback
Different methods of using 1unit sample feedback loops
Why are these important , for doing karplus strong , and for FM operator feedback ( where an operator is a phasor~into cos ~)
The only rules are
1-It needs to be in subpatcher
2- an explicit block~ module has to be inserted 'block~1 '
You can achieve 1 unit feedback with delwrite~ and delread~ ( make sure delay time is 0 )
Or you can use a " tabsend~ tabread~" ,or "tabsend~ tabreceive~" when the tabsend~ method is used , it's crucial that an array is created withe same name .
The size of the array doesn't really matter , since only the first sample of the array is used to write into.
Here are some examples of the different methods
Left is the carrier ( phasor~ into cos~) , right is the modulator with self feedback .
I also added phase shift to the modulator to create a perfect trian gle ,which is only possible with operator feedback and phase shift
Controlling mouse position coordinates (Linux)
@oid said:
Using [command] and xdotool [...]
Yes! It works fine in pd.
This move the mouse cursor to (120, 70):
[exec xdotool mousemove 120 70( ---- [command]
And this make a click:
A double click:
But...there is a problem: the "click" has no effect inside the window (of another app).
As you were saying, the cursor needs to know "which" window needs to be activated.
The command should be this one that I added in the middle:
xdotool_test.pd
Note: 0x4c00006 is the "Window id" I copied from the target window information obtained with xwininfo.
Any tips?
I will do further tests.
Thank you,
a.
Unexpected behavior for 1-sample-block subpatch with multichannel-outlet
i was about to report an issue on the pd github - but since i really don't know what's going on, i thought i'd share this here first and maybe someone has an explanation for it ....
i've been experimenting with a simple patch for random-walking the surface of a sphere. the current algorithm is not very elegant since it uses random steps that don't have equally distributed distances (but rather form the shape of a cube). i use 1-sample-send~/receive~ to feed back the current position for the calculation of the next position. the weird thing is that it works perfectly well if i output my coordinates with 3 outlet~s ... but the result looks different for the exact same algorithm if i output it via 1 multichannel outlet.
so it seems like the outlets are affecting what's happening inside the subpatch?!?
here are 2 screenshots for these 2 cases - with 3 outlets:
with multichannel outlet (the coordinates are no longer on the surface of the sphere, but start to blur into a cubic shape):
and here's the patch for testing (vanilla besides requiring Gem ... and the relevant part is in the 2 subpatches obviously):
spherical_randomwalk_1sampleblock_mc-outlet.pd
Karplus strong and strange issues with fexpr~
these are some pictures with the pd patch and below a spectrogram so you can see what I mean
Using TouchOSC to draw into a 16 step array? communication back'n'forth? Show Array content in TouchOSC?
continuing with OSC:
there's apparently this command arp -a
that i can run on the terminal
i get a list of bunches of IP addresses, then when i move a slider on TouchOSC, the iPad-specific IP appears:
$ arp -a
? (10.0.1.1) at f0:99:bf:0:c2:5c on en8 ifscope [ethernet]
? (10.0.1.2) at 3a:69:f1:6f:e7:a4 on en8 ifscope [ethernet]
? (10.0.1.6) at (incomplete) on en8 ifscope [ethernet]
? (10.0.1.8) at 64:4b:f0:13:9d:b7 on en8 ifscope permanent [ethernet]
? (10.0.1.15) at (incomplete) on en8 ifscope [ethernet]
? (10.0.1.255) at ff:ff:ff:ff:ff:ff on en8 ifscope [ethernet]
? (169.254.7.238) at (incomplete) on en8 [ethernet]
esaipadmini.local (169.254.68.27) at c6:b:31:36:6b:a6 on en12 [ethernet]
esasoftabilitym1.local (169.254.168.156) at c6:b:31:40:41:93 on en12 permanent [ethernet]
? (224.0.0.251) at 1:0:5e:0:0:fb on en12 ifscope permanent [ethernet]
? (224.0.0.251) at 1:0:5e:0:0:fb on en8 ifscope permanent [ethernet]
broadcasthost (255.255.255.255) at ff:ff:ff:ff:ff:ff on en8 ifscope [ethernet]
so armed with this knowledge, i went in and did
and
and then ..
it works!! it.. works!!!!!
and @beep.beep - i'm running fully usb-tethered with all wi-fi bluetooth mobiledata off. can you have a look and see if this will solve your "OSC only works with wi-fi" issue?
cpu saving methods - should i pause subpatches that are just leftovers and not in use?
@seb-harmonik.ar said:
Actually the process that is 70% CPU is the GUI process, the lowercase letter one is the one doing the audio
That 70% is probably just from drawing a lot of GUI stuff
that's very interesting! so it seems like my best choice would be to start looking at optimizing the amount of GOP stuff i have, as my GUI for the main script is pretty busy.
ok looks like just simply dumping the [else/spectrograph~]
(the large pink one), resulted in a massive drop
EDIT: just noticed one interesting thing. whichever part of the script i'm in (lower part or top part), has a massive effect on CPU usage. it's the one with more GOPs (the mixer strips) that ramps Pd up to 80% or more. so now i gotta figure out how to start reducing the GUI load.
trying to set PageUp/PageDown to get to the top and the bottom of the canvas - need it in abstraction instead of mainview due to display space considerations
hi, i've got this:
the purpose of which is to use multiple ways of switching between "top of the canvas" and "bottom of the canvas". I think here's a complete list
- a midicontroller (two midi messages) (Loupedeck Live device) (the button-presses on the device sends Midi messages)
- the pageup/pagedown buttons on the keyboard, if available
- shift-° to switch between the top and the bottom of the screen
- Karabiner (macOS) configured mouse buttons to send the very same message
- two red buttons (aligned so that whether in top canvas area or bottom canvas area, the button stays in the same place
..but i'd really prefer to not have this large amount of objects on the main script canvas, taking up space, since space is at a real premium for me. so i'm wondering how i could have this inside an abstraction and still get the same results on the main canvas. any ideas?
if it helps, here's my current main script view:
"Page up" :
"Page down"
so i'm really trying to reduce the amount of extra objects i have on my screen.
if you have any other suggestions on how to reduce the amount of "non-clickable objects" on screen, i'm open for anything.
Question about [tabread4~]
please try this help file:
https://forum.pdpatchrepo.info/topic/14301/add-delete-guard-points-of-an-array-for-4-point-interpolation-of-tabread4-ect
The Lagrange interpolation uses n-1, n, n+1 and n+2 for interpolation at sample n+frac.
The only way without harsh artifacts with such a small array of 32 samples + 3 guardpoints = 35 (sample 0 to 34)
is reading it from sample 1 to 32
reading the sine wave only and using the guard points (0, 33, 34) for interpolation.
As patched above.
Looking again into
else\Live-Electronics-Tutorial\Part.07-Sampling.Delay.Granulation\27-Sampling(buffer)\3.Interpolation
Yes, the read-points are clipped. But that clipping causes a discontinuity of the sine.
It gets less obvious and even non-perceivable with higher resolution samples, because the artifacts become more silent and phasor~'s frequency running it, stays the same.
B04.tabread4.interpolation.pd is using [+~ 1] instead of the [1( into the right inlet of [tabread4~] :
pd on raspberry pi 2B stuck multiple times
btw - I'm getting a popup message of i/o error and I think is because the audio dialog choose a inputdevice that doesn't really exist(?)
Is it possible to untick the audio input device via thr [audio-dialog] message i'm banging when patch is first loaded, so it will not be choose?