hi thanks to IOhannes indications i'm feeding my pix_mulitblob output into the iemmatrix now. as long as there're enough blobs in the picture it works pretty nice. but as soon as there're less blobs than given in the argument to pix_multiblob i get: error: $43: argument number out of range error: $44: argument number out of range ... for all the arguments of undetected blobs. and as soon as there's no blob in the picture the pd-shell reports: matrix : corrupt matrix passed do i do something wrong? i was using the attached patch thanks for help & hints olsen
olsen wrote:
hi thanks to IOhannes indications i'm feeding my pix_mulitblob output into the iemmatrix now. as long as there're enough blobs in the picture it works pretty nice. but as soon as there're less blobs than given in the argument to pix_multiblob i get: error: $43: argument number out of range error: $44: argument number out of range
without looking at the patch, i can tell you that this is because you are actually _not_ using iemmatrix for handling the matrix. instead your patch tries to manually parse the data using dollargs and whatelse; which obviously fails if there are too few arguments (because the matrix is too small)
... for all the arguments of undetected blobs. and as soon as there's no blob in the picture the pd-shell reports: matrix : corrupt matrix passed
this indicates that you _are_ using iemmatrix here. if no blobs are detected, pix_multiblob will output a somewhat illegal matrix with zero rows (and a number of columns).
now iemmatrix complains that this is not a legal matrix. probably putting a [mtx_check] helps to get rid of the error (or not)
do i do something wrong?
no.
fgmasdr IOhannes
IOhannes m zmoelnig wrote:
olsen wrote:
hi thanks to IOhannes indications i'm feeding my pix_mulitblob output into the iemmatrix now. as long as there're enough blobs in the picture it works pretty nice. but as soon as there're less blobs than given in the argument to pix_multiblob i get: error: $43: argument number out of range error: $44: argument number out of range
without looking at the patch, i can tell you that this is because you are actually _not_ using iemmatrix for handling the matrix. instead your patch tries to manually parse the data using dollargs and whatelse; which obviously fails if there are too few arguments (because the matrix is too small)
indeed i'm using matrix - at least i'm trying to - but i might handle the matrix data the wrong way. i could not find indications within the matrix help on how to handle the data 'correctly' means without gettin this error. so the way i solved it within the attached patch might be stupid, but i'll appreciate any alternative!
... for all the arguments of undetected blobs. and as soon as there's no blob in the picture the pd-shell reports: matrix : corrupt matrix passed
this indicates that you _are_ using iemmatrix here. if no blobs are detected, pix_multiblob will output a somewhat illegal matrix with zero rows (and a number of columns).
now iemmatrix complains that this is not a legal matrix. probably putting a [mtx_check] helps to get rid of the error (or not)
no mtx_check doesn't change it thanks for your help olsen
do i do something wrong?
no.
fgmasdr IOhannes
Hi mtx_slice finally fullfills my need to get certain elements like rows/colums of a matrix. might be nice to have this listed in the matrix-help.pd down in the 'see also help for' section? greets ø
olsen wrote:
IOhannes m zmoelnig wrote:
olsen wrote:
hi thanks to IOhannes indications i'm feeding my pix_mulitblob output into the iemmatrix now. as long as there're enough blobs in the picture it works pretty nice. but as soon as there're less blobs than given in the argument to pix_multiblob i get: error: $43: argument number out of range error: $44: argument number out of range
without looking at the patch, i can tell you that this is because you are actually _not_ using iemmatrix for handling the matrix. instead your patch tries to manually parse the data using dollargs and whatelse; which obviously fails if there are too few arguments (because the matrix is too small)
indeed i'm using matrix - at least i'm trying to - but i might handle the matrix data the wrong way. i could not find indications within the matrix help on how to handle the data 'correctly' means without gettin this error. so the way i solved it within the attached patch might be stupid, but i'll appreciate any alternative!
... for all the arguments of undetected blobs. and as soon as there's no blob in the picture the pd-shell reports: matrix : corrupt matrix passed
this indicates that you _are_ using iemmatrix here. if no blobs are detected, pix_multiblob will output a somewhat illegal matrix with zero rows (and a number of columns).
now iemmatrix complains that this is not a legal matrix. probably putting a [mtx_check] helps to get rid of the error (or not)
no mtx_check doesn't change it thanks for your help olsen
do i do something wrong?
no.
fgmasdr IOhannes
Submit an updated help patch to the patch tracker :)
.hc
On Dec 13, 2009, at 9:30 AM, olsen wrote:
Hi mtx_slice finally fullfills my need to get certain elements like
rows/colums of a matrix. might be nice to have this listed in the
matrix-help.pd down in the 'see also help for' section? greets øolsen wrote:
IOhannes m zmoelnig wrote:
olsen wrote:
hi thanks to IOhannes indications i'm feeding my pix_mulitblob
output into the iemmatrix now. as long as there're enough blobs in the
picture it works pretty nice. but as soon as there're less blobs than given
in the argument to pix_multiblob i get: error: $43: argument number out of range error: $44: argument number out of rangewithout looking at the patch, i can tell you that this is because
you are actually _not_ using iemmatrix for handling the matrix. instead your patch tries to manually parse the data using dollargs
and whatelse; which obviously fails if there are too few arguments
(because the matrix is too small)indeed i'm using matrix - at least i'm trying to - but i might
handle the matrix data the wrong way. i could not find indications
within the matrix help on how to handle the data 'correctly' means
without gettin this error. so the way i solved it within the
attached patch might be stupid, but i'll appreciate any alternative!... for all the arguments of undetected blobs. and as soon as there's
no blob in the picture the pd-shell reports: matrix : corrupt matrix passedthis indicates that you _are_ using iemmatrix here. if no blobs are detected, pix_multiblob will output a somewhat
illegal matrix with zero rows (and a number of columns).now iemmatrix complains that this is not a legal matrix. probably putting a [mtx_check] helps to get rid of the error (or
not)no mtx_check doesn't change it thanks for your help olsen
do i do something wrong?
no.
fgmasdr IOhannes
-- ETs DNA will not be televised
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war on
terrorism. - retired U.S. Army general, William Odom
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
olsen