Fluid.plotter labels ( pure data / linux )

[yogi]

Hello,

in order to test flucoma
I adapted a max patch in pure data,
that slices and analyzes a sound, then plot in
2D it seems to be working , then I tried
to add labels, and failed. I must be doing
something wrong, I spent some time trying to figure out,
here is the patch attached, if anybody can help
me find out.

Cheers

fluidCorpus2D.pd (8.1 KB)

[tremblap]

ok the problem is triple:

• Pd transforming float to strings. We need to change our examples because 0.00000 seems to not be recognised as a label… in your code I have added a [makefilename %d] object in the label making in [pd mfcc analysis]

• if you use the nightly builds (you should for the fixes) then you will see I have made fluid.plotter in C - faster but I didn’t include 8 colours in my array so 8 classes freaks out - if you change numclusters to 6 you’re fine (for now, I’ll add another 10 colours in the array and deal with the size cap too in a more elegant way) 16 classes should be enough to plot no?

so this patch works for 6 clusters. I’ll correct the C code to allow for 16 clusters in [fluid.plotter] later today or tomorrow.

p
fluidCorpus2D.pd (8.2 KB)

[yogi]

Thank you !

I did notice the floats as indexes in my datasets and added the “makefilename %d” but didn’t think about reducing the cluster number.

I noticed when using “highlight” message that after while the selection of points in the plotter is slowing down.

[tremblap]

@yogi

I noticed when using “highlight” message that after while the selection of points in the plotter is slowing down.

yes but that is Pd’s graphic API’s fault. It is very old. like 30 years old. So the more you add points, the slower it gets. That community is in discussion to change their graphic API (which will mean a painful recode from us but for a good cause)

[tremblap]

So I’ve pushed a fix - it is compiling on the ‘nightlies’

I’ve used 16 equidistant colours from CET06 (CET Perceptually Uniform Colour Maps) as we did in other places. I could have used the 10 we use in SuperCollider but that is only 10 classes (https://github.com/d3/d3-scale-chromatic/blob/main/src/categorical/category10.js) although it might be better for cohesion.

if you can live with “only” 10 categories, let me know and I’ll change them for a more unified fluid-world

[tremblap]

actually as geek is a geek - I couldn’t resist to compare. @tedmoore do you have a preference?

if we feel 10 is enough I think I might prefer the SC colour scheme…

comments welcome, change is trivial, unified world is my favourite option as usual

[tremblap]

ok 10 will have to be enough - this is so cute:

[tedmoore]

I don’t really have a preference. If anything I’ll observe that if the black circle around the dot needs to be there, then the lighter colors are better perhaps, they help differentiate, but I don’t know if that’s the 10 or 16 category scheme.

But as you say, it’s not too important.

[yogi]

I don’t have an opinion on how many classes is enough, I’m slowly discovering the Flucoma library since last november, I like the Flucoma pd documentation a lot by the way, the patches are instructive both about the library and pure data itself

[tremblap]

1.0.7 is SUPER FAST now that I found a hack around the (curse word) C+TCL interface memory issues.

try it in this thread:

Ohhhh looked what appeared almost a year later... v. 1.0.7!

ok dear people. 1.0.7 is tested by me. I’m going in holidays for 9 days. Please download and road test… and maybe even someone might write the release notes…

feedback welcome. I’m offline until the 2nd but hey, road test it please!