-
ddw_music
I have used pix_multiimage successfully in the past. But in this patch, I'm getting a fat load of nothing.
There is a folder adjacent to this file called "pix" -- in it, there are 13 files, pic0.jpg, pic1.jpg ... pic12.jpg.
Selecting any image 0-12 in the right inlet produces:
[pix_multiimage]: selection number too high: 1 (max num is 0)
I'm definitely clicking the "open" message, and no error is reported... but nothing is loading.
I dunno here, AFAICS I'm following the helpfile to the letter and doing stuff I've done before. So my guess is that the object is broken...? Can someone confirm?
hjh
-
ddw_music
I guess it all begs the question though: Why is the rpi program sending numbers as strings?
hjh
-
ddw_music
@dmanz could you print the raw netreceive output, before oscparse? They will appear as lists of bytes -- that would confirm what is the type tag for the number, and how the number is being represented.
It's all guesswork without knowing that.
hjh
-
ddw_music
@whale-av said:
The message to [vline~] cannot set times to be longer than 500ms because your tempo is 120bpm.
Perhaps not a critical error, because, if a new envelope comes into vline~ while an older one hasn't finished, the older one is (correctly) just abandoned. They don't interfere.
hjh
-
ddw_music
Right -- the OP actually mentions both types of blurring: blurring the contents of each frame individually (feathering edges), or blurring from one frame to the next (trails).
[pix_blur] does motion blurring but AFAICS it does not do image blurring.
[pix_convolve] does image blurring, but it's probably slow for the large kernels that would be required for extreme blurring effects.
I needed an extreme image blur (soft-edge alpha masking) so I looked to see if frei0r had an appropriate plugin, and it did
AFAICS Gem does not have a built-in IIR image blur object.
hjh
-
ddw_music
@FFW said:
For fun this is the cross product
Huh -- the visual is actually kinda comprehensible
Eventually I realized that my specific case can be done more easily with Cartesian coordinates, so I'm just keeping them in that space. This cross product is good for future reference
hjh
-
ddw_music
@willblackhurst said:
its always half at first. its for mesuring distance from the middle. like a radius.
Thanks -- I still don't get it. Maybe I'll have to file a bug report and ask the devs.
I also find that as I increase the grid resolution, the drawn shape grows -- a 5x5 grid with points at -3, -1.5, 0, 1.5, 3 draws half size, but a 6x6 grid draws slightly larger.
That's weird.
hjh
-
ddw_music
@jameslo said:
@ddw_music Is this what you're looking for?
Indeed -- thanks. Wouldn't have chanced across that.
Though, in
(3.0 / 250)
, Pd didn't truncate the 3.0 either.Thanks --
hjh