11 messages in at.iem.pd-listRe: [PD] Best way to deal with many t...| From | Sent On | Attachments |
|---|---|---|
| B. Bogart | Feb 20, 2009 8:59 pm | |
| Roman Haefeli | Feb 21, 2009 1:59 am | |
| cyrille henry | Feb 21, 2009 2:51 am | |
| David Doukhan | Feb 21, 2009 4:32 am | |
| B. Bogart | Feb 21, 2009 9:52 am | |
| cyrille henry | Feb 21, 2009 12:48 pm | |
| Mathieu Bouchard | Feb 21, 2009 3:36 pm | |
| Jonathan Wilkes | Feb 21, 2009 6:03 pm | |
| David Doukhan | Feb 22, 2009 5:00 am | |
| marius schebella | Feb 22, 2009 2:05 pm | |
| cyrille henry | Feb 22, 2009 4:50 pm |
| Subject: | Re: [PD] Best way to deal with many tables. | |
|---|---|---|
| From: | cyrille henry (cyri...@la-kitchen.fr) | |
| Date: | Feb 21, 2009 12:48:11 pm | |
| List: | at.iem.pd-list | |
B. Bogart a écrit :
Thanks all for your comments. ...
Cyrille, This is an interesting idea, pix_histo outputs tables though. I don't know what you mean by 2D tables,
what i call a 2D table is just a 2D matrix...
they should be 3D for each colour channel right??
why 3D? density = function (image, color index) it's only 2D.
Even if there was an object to dump a hist into an image, rather than into a table, I don't think the gem pixel operations on pixels would be any faster than those on tables (slicing out, concatenating, listing etc..) Please share if you have some ideas already implemented that does this kind of thing.
i don't know if i did understand. do you have the hystogram and only wish to acces them in real time. or do you want to modify them in RT?
i originaly thought that you could script something to write the histogram of
your images in table of 3x256 value (1 table for 3 hysto). Then concatenate them
in "not real time" into 1 big image.
then accessing the data in RT was simple.
if you wish to modify this data in RT, it will be harder.
maybe a matrix will be the best...
Cyrille
_______________________________________________
Pd-l...@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list