JS selfie segmentation error after the first frame
235 views
Skip to first unread message
Марк Вавилов
unread,
Jul 21, 2021, 10:48:28 AM7/21/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to MediaPipe
Hello, everyone! I'm trying to use MediaPipe Selfie Segmentation and it works only for the first frame. After that it keeps calling send as it should, but instead of calling callback it fails with error:
Error:Uncaught (in promise) TypeError: m.C.then is not a function at ia.h (vendors-node_modules_mediapipe_selfie_segmentation_selfie_segmentation_js.js:63) at U (vendors-node_modules_mediapipe_selfie_segmentation_selfie_segmentation_js.js:21) at ka.next (vendors-node_modules_mediapipe_selfie_segmentation_selfie_segmentation_js.js:22) at vendors-node_modules_mediapipe_selfie_segmentation_selfie_segmentation_js.js:31 at new Promise (<anonymous>) at X (vendors-node_modules_mediapipe_selfie_segmentation_selfie_segmentation_js.js:31) at Object.onResults (vendors-node_modules_mediapipe_selfie_segmentation_selfie_segmentation_js.js:63) at methodCaller_void_$vector$ResultData$$ (eval at new_ (selfie_segmentation_solution_simd_wasm_bin.js:9), <anonymous>:5:26) at __emval_call_void_method (selfie_segmentation_solution_simd_wasm_bin.js:9) at selfie_segmentation_solution_simd_wasm_bin.wasm:0x1f907
If anyone has any idea on what may be going on, please help!
Ravindhran Sankar
unread,
Jul 27, 2021, 12:51:13 AM7/27/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to MediaPipe
I am running into the same error. Not sure what is going on.
The issue seems to go away when you decrease the frame rate, and reappears as you increase it.