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
I have a pretty big datastore; millions of image files. Given the scale, it was worth considering an investment into next-gen image formats. Between AVIF and JpegXL, it seems that JpegXL is substantially more balanced and has clearly more community interest. I therefore attempted to encode my data with JXL, saw good results and moved over.
Everything is on top of a BTRFS filesystem which can can reflink these files to labelstudio (which I prefer over symlinks as are safer). Labelstudio, however, does not support JXL, requiring me to transcode the relevant files back to JPEG (which I think it can be done losslessly) or PNG.
Not a whole lot of browsers support JXL (Safari + Firefox with flags). Depending on what takes Labelstudio to support a format, this might something worth considering now (if it is a matter of accepting a new mime) or postponing for later (if the ecosystem is deemed too immature).
The text was updated successfully, but these errors were encountered:
Label Studio Image Format Support:
Label Studio relies on the web browser's capabilities to display images within the labeling interface. Currently, support for JpegXL is limited across major browsers:
Chrome: Does not support JpegXL by default.
Firefox: Supports JpegXL when experimental flags are enabled.
Safari: Offers some support, but it's not widespread.
Due to this limited browser support, Label Studio does not natively support the JpegXL image format at this time. Integrating JpegXL would not guarantee a consistent experience for all users, especially those using browsers without JpegXL support.
My usecase is the following:
I have a pretty big datastore; millions of image files. Given the scale, it was worth considering an investment into next-gen image formats. Between AVIF and JpegXL, it seems that JpegXL is substantially more balanced and has clearly more community interest. I therefore attempted to encode my data with JXL, saw good results and moved over.
Everything is on top of a BTRFS filesystem which can can reflink these files to labelstudio (which I prefer over symlinks as are safer). Labelstudio, however, does not support JXL, requiring me to transcode the relevant files back to JPEG (which I think it can be done losslessly) or PNG.
Not a whole lot of browsers support JXL (Safari + Firefox with flags). Depending on what takes Labelstudio to support a format, this might something worth considering now (if it is a matter of accepting a new mime) or postponing for later (if the ecosystem is deemed too immature).
The text was updated successfully, but these errors were encountered: