-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maybe webApp can output gif to share? #110
Comments
The issue is file size. Compression (zstd) is built into the format, but compression can only help so much. The reason cimbar works (imo) has a lot to do with the ephemeral nature of the frames -- we create one, show it on screen, and throw it away and move onto the next -- which allows it to sidestep the issue of the size of the encoded image. That said, the |
While I completely understand that the resulting GIF might be larger, I believe this solution can still be very useful. Perhaps storing images as separate PNGs could be a better approach than using a single GIF. @sz3 Thank you for your great work on this tool! |
This will depend on how many redundant frames we generate -- for over-the-air data transfer we use a multiple of the data size(e.g. "4x") to limit the chance of encountering duplicate frames: if we're already decoded a frame, seeing it again doesn't help us. For offline usage, whether shared as a gif or on paper, too many extra frames seems like a bad idea (too much redundancy is waste), so I've tended to assume 10-20% redundancy is ok. That is, the number of frames is the bare minimum + 20% extra, so we could afford to skip/lose 20% of the encoded frames (any of them) and still decode. |
Another use case for GIFs is for tunnling data. For example (I know this has been done better, this is an example), uploading a cimbar GIF to a video site. |
When I first found out about this project I was excited, but I realized that it is not a traditional static QR code and I didn't find a sharing solution. Do I think it is possible to share via gifs?
The text was updated successfully, but these errors were encountered: