#Files API is... tragic
1 messages ยท Page 1 of 1 (latest)
The only word i can use to describe this is tragic
What ever happened to plain old we-heart-multipart, or basic client support ๐
I understand that the team is (probably) working on this, but like, seriously, dumping this on users in the state that the Files API is currently in? not that big of a fan of this tbh
DX is not that great on this recent change (or lack thereof?) ๐
Hi Bedros, thanks for the feedback. The File API is currently in private preview - we will be adding support file upload to the SDK soon.
Regarding video & frame extraction - frame extraction for videos can be lengthy and there are numerous configurations you can tune (1 FPS? less fps? resolution of the images, skip some parts of the video etc). So we wanted to start by with allowing developers to be in full control in how they want to extract the videos and knowing exactly what is being sent to the LLM model itself. The colab is an illustration of how to do so. We will discuss the feedback regarding this with the team. Please keep the feedback coming!
Yeah, I'm all for giving devs control, but there is a diff between unnecessary abstraction and desperately needed abstraction ๐ญ
A simple videoconfig param would do, with fps and compression controls
or for max control, the ability for the dev to add their own video processing handler, but again, i don't see much purpose in that
from my perspective as a dev using this stuff, all a dev would want is to set the fps & compression options
saying its a work in progress wouldve been good enough
claiming that the lack of developer support is a feature is really upsetting