Oh... if you want to load 13 images, you have to specify 12 in the "open" message.

No error message, no hints, silent failure cheers, then.

hjh

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

I guess it all begs the question though: Why is the rpi program sending numbers as strings?

hjh

@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

@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

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

Pushing the boundaries of necrobumping a thread (19 years!)...

I just needed a more extreme blur than pix_convolve can do.

For future readers: pix_frei0r with the stock IIRblur plugin worked great, a trouble-free drop-in.

hjh

@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

@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

@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

I'm stumped. I'm generating control points between -3 and +3 (z = 0), and it's drawing -1.5 to +1.5. The white square is -3 to +3. The green circles show where -1.5 and +1.5 are.

Anyone know why?

why-is-it-half-size.pd

(I will be distorting the grid later, so the loop-generation of a control point grid is necessary.)

hjh

Is this documented? Surprised me rather a lot.

"You've got... integer division" is a bit too much like Max for my taste...

hjh

Pondering a thingy that would depend on adding/multiplying vectors (as in an angle and magnitude) -- perturbing points in a grid. Has anyone already built abstractions for the basic ops? Would save me some time.

EDIT: Turns out what I'm doing isn't so complicated, so, a library is not really necessary.

hjh

Is there any way, in Gem, to draw arbitrary curves ([curve3d], [surface3d]) with color gradients?

I guess, worst-case bad workaround would be to algorithmically generate a pix_texture (but Gem's support for this isn't marvelous either).

Or write a shader (yikes, that's gonna eat up hours that I don't have).

Would be nice if you could write per-control-point colors into the curve.

hjh

@dlask IMO:

Normalize your knob range to be 0-1 (or -1 to 1).

Then you can express any range you want, in terms of a range and an offset: value = range * knob + offset.

The radio button would change the range and offset.

"Sample and hold," I'm not sure now exactly what behavior you want. An easy behavior would be: use the radio button to change only the cold inlets of the * and + operators. Then, changing the radio button would not update the output value. The knob would be connected to the * operator's hot inlet, so that touching the knob would produce output.

hjh

@Luizagimenez said:

I have a work assigned to translate some Graphs from UV lightning on molecules to an array in Pure Data. Im trying to find a way to get the Quadratic Equations that have complex numbers to show on a somewhat precise array or graph, so i can use these numbers for frequencies, to create a movable bar to select a pixel of the graphic.

Pd can express any math formula, but it's more cumbersome for complicated math expressions than a text-based language. [expr] helps somewhat, though. A real-number (no complex) quadratic would look like this:

If a quadratic is ax2 + bx + c, and you need complex numbers, is it that a, b and c can be complex, or only x? Your graph suggests a real-number domain, in which case complex a, b, c would be the sum of 2 quadratics, one multiplied by i. So, the above patch, but duplicated, to give you a real and an imaginary result.

If x can be complex too, then it's more involved than that.

hjh

@ChicoVaca Yes -- whale-av is right about the problem. It's possible to collect, but the only way to know that the chord is over is to wait a short time.

This handles note-on. It will not remove notes from the chord upon note-off (which is easy in a programming language but rather laborious in patching -- not impossible, just cumbersome, and I'm short on time).

Every time a note is appended to the list, it also triggers a 50 ms delay. [delay] only fires the last one -- so if you play C 60 and E 64 quickly, the [delay] will fire only 50 ms after the second note, causing the list to be output.

hjh

@vk092 said:

@dreamer Information regrading how they are used in Pd is what I am concentrating on currently , but still it covers a lot of thing . I'd appreciate any suggestions on what specific aspects I should include in the PR for the community.

I guess, if anything, I'd suggest to keep it minimal. The main things users will care about are:

• How to choose a specific audio device
• How to set sample rate, bit depth etc.

Detailed ALSA configuration instructions... I wouldn't see much benefit in duplicating existing online materials.

Also... Pipewire is coming fast (Ubuntu Studio 24.04 ships with pipewire as the default audio system, no longer JACK). So, if you're going to write up something about audio frameworks, it would be great to handle this in advance. My understanding is that it's supposed to be as simple as doing pw-jack pd-gui instead of just pd-gui but when is it ever that simple...? (Haven't tried pipewire myself yet, maybe it is that simple.)

hjh

@hmp Should "text tolist 1" be an object box? Currently it's a message box, so it isn't doing any actual operation.

hjh

@Dizzy-Dizzy said:

To verify that I have the latest I used the "sudo apt-get upgrade puredata" command in the terminal and got the message "puredata is already the newest version (0.51.4-1)"

That's referring to the latest version in your Linux distro's package manager. Package managers aren't guaranteed to have the latest versions of everything. So there does exist Pd 0.55, but the package manager doesn't have it.

Agreed that Pd is one of the easiest packages to build. Readme instructions are straightforward.

hjh