You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with hundreds of videos in VMS, we often have to resort to uploading multiple .zip files (eg. 1 GB each, to avoid mega-files)
This practice of having multiple archives containing .mp4 videos + .txt captions is nearly identical to the WebDataset file format, which is designed for large AI/ML training datasets.
Proposal
Add basic support for uploading/importing WebDataset
Implement end-to-end support for WebDataset (see branch webdataset)
Propose the support of WebDataset into Finetrainers
For point 2, here end-to-end support means performing all our processing and transformations (black band removal, captioning..) inside the WebDataset space, instead of the OS file system.
While using WebDataset internally doesn't automatically allow to train datasets greater than what Finetrainers can support, the idea is more about having a long-term vision for VMS to be architecturally independent and adopt future-proof design.
The vision for VMS is to be a standalone app that can be used for annotation only, and to potentially support alternative training backends (Job API, Replicate, Fal, diffusion-pipe etc).
The text was updated successfully, but these errors were encountered:
Context
When working with hundreds of videos in VMS, we often have to resort to uploading multiple .zip files (eg. 1 GB each, to avoid mega-files)
This practice of having multiple archives containing .mp4 videos + .txt captions is nearly identical to the WebDataset file format, which is designed for large AI/ML training datasets.
Proposal
For point 2, here end-to-end support means performing all our processing and transformations (black band removal, captioning..) inside the WebDataset space, instead of the OS file system.
While using WebDataset internally doesn't automatically allow to train datasets greater than what Finetrainers can support, the idea is more about having a long-term vision for VMS to be architecturally independent and adopt future-proof design.
The vision for VMS is to be a standalone app that can be used for annotation only, and to potentially support alternative training backends (Job API, Replicate, Fal, diffusion-pipe etc).
The text was updated successfully, but these errors were encountered: