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
Feature request to support color6 (64 colors) for WebSocket/Browser output
Serum based colorisation uses 64 colors in a color6 encoding. Currently they are converted to 24bit RGB, producing so many web packets that the browser got lost, way behind in display, wrong order, even get stuck.
A solution would be to support color6 directly, which would reduce traffic drastically.
This would also require to support color rotation.
Still I noticed that often package (frames) arrives in wrong order, so a filter to skip older frames would help
The text was updated successfully, but these errors were encountered:
Feature request to support color6 (64 colors) for WebSocket/Browser output
Serum based colorisation uses 64 colors in a color6 encoding. Currently they are converted to 24bit RGB, producing so many web packets that the browser got lost, way behind in display, wrong order, even get stuck.
A solution would be to support color6 directly, which would reduce traffic drastically.
This would also require to support color rotation.
Still I noticed that often package (frames) arrives in wrong order, so a filter to skip older frames would help
The text was updated successfully, but these errors were encountered: