Well.. you have a limited amount of CPU, that gets topped up with every request that comes in.. so y

Well.. you have a limited amount of CPU, that gets topped up with every request that comes in.. so you can't just have one request and use unlimited CPU..

ErwinOP•3/16/22, 8:43 AM

Also, streaming (a lot of) video is against the Terms of Service..

Aabrar https://ibb.co/VV6bYj5 is the problem from json? How can I fix it , from postman...

ben•3/16/22, 8:51 AM

In your code, you're still calling const { title, content } = await request.json()const { title, content } = await request.json() for the options request, which doesn't send the JSON body. You should check if it's a post request before that.

EErwin Well.. you have a limited amount of CPU, that gets topped up with every request ...

ben•3/16/22, 8:54 AM

Does that mean you could theoretically send a bunch of requests that do nothing and use the CPU allocated for those requests for the converting request?

DDeleted User you would get rate limited for DDOS

ben•3/16/22, 8:59 AM

If the CPU limit is 30s, then you only need to send a request once every 30 seconds minimum though?

ben•3/16/22, 9:00 AM

It would work though right..?

ben•3/16/22, 9:02 AM

I don't think workers even let you call workers in the same zone, so you would have to initiate the request from the client

DDeleted User like in the case they upload raw footage, edit it, export it with libav.js

ben•3/16/22, 9:03 AM

You'll probably get way better performance from running it on the client, because workers don't support webassembly multithreading (i think), and it's also sharing resources with a bunch of other workers

ben•3/16/22, 9:03 AM

also, 4k video would go over the memory limit

ben•3/16/22, 9:04 AM

Oh boy now we're talking

ben•3/16/22, 9:07 AM

You could use libav.js onto the client, use that to chunk the video into groups of like 5 seconds (maybe less, you'll have to use trial and error), and then send a request for each of them

DDeleted User I don't know if this is against ToS. It's not really streaming video the same wa...

ErwinOP•3/16/22, 9:19 AM

The whole point is to prevent you from streaming massive amounts of traffic on a free or cheap plan..

ErwinOP•3/16/22, 9:20 AM

And the term is 'non-HTML' content or something..

kian•3/16/22, 9:27 AM

you're trying to return resp when you've consumed the resp body already

kian•3/16/22, 9:27 AM

DDeleted User I don't mind paying for it. I want to sell video editing as a service

ErwinOP•3/16/22, 9:30 AM

It will be hard to make work on CF for now unfortunately.. encoding/transcoding isn't a great workload just yet.. Although with R2 and range requests, that might change?

DDeleted User I don't mind paying for it. I want to sell video editing as a service