Revision history [back]

as of today, it seems, only exactly 68 landmarks are supported.

there is a hardcoded pupils list which only covers this case. using any smaller number of landmarks will lead to a buffer overflow later here

please try to run this with a DEBUG build, from gdb or such, and you'll be able to reproduce it:

add a line here

params.n_landmarks=29;

then

facemark_demo_lbf cascade.xml lbf_img.txt lbf_pts29.txt lbf.model

(using 2 images & 2 pointslists from the attachment below, (renamed to .zip !!))

C:\fakepath\lbf_2img.tiff

as of today, it seems, only exactly 68 landmarks are supported.

there is a hardcoded pupils list which only covers this case. case.

using any smaller other (smaller) number of landmarks will lead to a buffer overflow later here

please try to run this with a DEBUG build, from gdb or such, and you'll be able to reproduce it:

add a line here

params.n_landmarks=29;

then

facemark_demo_lbf cascade.xml lbf_img.txt lbf_pts29.txt lbf.model

(using 2 images & 2 pointslists from the attachment below, (renamed to .zip !!))

C:\fakepath\lbf_2img.tiff

as of today, it seems, only exactly 68 landmarks are supported.

there is a hardcoded pupils list which only covers this case.

(i can't even find a consistent descripton of the 29 point model !)

so, currently, using any other (smaller) number of landmarks will lead to a buffer overflow later here

please try to run this with a DEBUG build, from gdb or such, and you'll be able to reproduce it:

add a line here

params.n_landmarks=29;

then

facemark_demo_lbf cascade.xml lbf_img.txt lbf_pts29.txt lbf.model

(using 2 images & 2 pointslists from the attachment below, (renamed to .zip !!))

C:\fakepath\lbf_2img.tiff