Open SeanBannister opened 2 years ago
Thanks Sean. What similar thing were you attempting to do?
I'm new to next and react, and the hydration warning has me puzzled. For now I'm OK with the fact that an optimized production build (npm run build
/ npm start
) suppresses that warning.
Regarding delay, I'm experimenting with various GPT-3 max_tokens
values to strike a balance between rich / quick responses. I asked the supplier of the video avatars about reducing the frame rate but they said that quality would suffer.
I do plan on updating the repo soon, adding the ability to ask for current and relative dates/times, and dates/times in various locations, using the four languages supported so far. The main objective for this and upcoming improvements is to provide practice in areas that GPT-3 can't help with (e.g. accessing date/time). Another improvement will be that the AI characters attributes (e.g. favorite foods, friends names) will be more easily customized via generated prompts.
Thanks for reaching out, James Weaver
Thanks for the response. The similar thing I was looking to achieve was talking avatars with GPT-3, there was a part of me that really wanted to integrate with Unreal's Metahuman characters because they're so life like and easy for anyone to create, there's a project already integrating Amazon Polly with Metahumans https://github.com/aws-samples/amazon-polly-metahumans
Brilliant project, thanks for your work on this as I was attempting to do something similar. I'm particularly interested in helping to minimize the delay between responses and possibly improve the virtual character.
I don't usually work with next or react so just wanted to report the following error I received on the first run of
next dev
(the project still seems to work fine):