Jeff Almasol • Adobe Employee, Feb 08, 2024Feb 08, 2024
Hello all... The updated version of Character Animator, version 24.2, is now available in the Creative Cloud desktop app. It contains the fix (previously only available in the Beta build) for this issue. Thank you for your patience and help resolving it.
Same problem for me. Using Adobe Character Animator (in Starter mode) on a 2019 Intel MacBook Pro with Sonoma 14.1.1. The webcam video freezes, and I get the "handle value is not a number" error while using the standard included characters in current and Beta versions of the app and also with the older versions of the app that are still available. Total disaster. I need to teach an Animation Workshop for kids next week and need to use the Starter version. (The pro version works although sometimes the same error pops up.)
Solution! (Sort of.). After banging my head against he wall with Character Animator not working, the webcam freezing up, and getting the error code, I discovered that if I CHANGE THE BACKGROUND to one of the Alpha invisible backgrounds or one of my own custome backgrounds, then everything works. I have not extensively tested this yet, but that is my preliminary solution until Adobe fixes the problem. Please try this, and see if that works for you. (2019 Intel MacBook Pro, using Starter mode...even though I am well-verse in Pro mode)
We have a possible fix for this issue available in the Beta version of the app. If you're willing to try it, go to the Creative Cloud Desktop app, under the "Beta apps" category, then install Character Animator (Beta), v24.3.0.7 (or later). The Beta app installs separate from the released Character Animator, v24.0 app, so you can try it out without affecting your existing installation.
If you are able to try it, can you post whether the "Handle value is not a number (Container.js)" error is still appearing our not in Beta 24.3.0.7?
Hello all... The updated version of Character Animator, version 24.2, is now available in the Creative Cloud desktop app. It contains the fix (previously only available in the Beta build) for this issue. Thank you for your patience and help resolving it.