#OpenAI CORS and tainted canvas (*)

9 messages · Page 1 of 1 (latest)

fringe ingot
#

Hello community. I am facing some problems with my application for dall-e2 and maybe someone here can brief me a bit, i would appreciate it. I have built an awesome outpainting feature inside my app but it seems like i can't avoid the cors errors that come with the API response. More exactly, the URLs that come from the response taint the canvas unless i save the images on my server. I could actually do that, but it takes a big amount of time in order to save all the photos. The function gets locked for like one minute in total. The response from OpenAI edits take like 30s to finish then another 30s i spend saving the files and I don't think its normal. Maybe there is some way to avoid the cors problem with OpenAI that i dont know of?
I would love to be able to use the openAI images directly into the canvases even tho i save the photos in the background. I hate that i have to lock the funciton for so much time to avoid tainting the canvas 😦
Thanks for your time!

north wadi
fringe ingot
#

I actually tried with the base64 and b64_json and the problems seems to persist. I am looking now at your repo and see whats up 😄 thanks for the reply

north wadi
#

That's not my repo, just something I found :) Good luck!

fringe ingot
#

sadly it doesn't help 😦 I am open to any suggestion. I also have a form file in my front-end and if i upload images from there and send to openAI, it works fine even tho the uploaded images don't really saves on the server but rather use the browser cache. Maybe I can do something similar

iron summit
fringe ingot
#

@iron summit I'm sure there should be a way

iron summit
#

Thanks