Several small items have such an insignificant width after being calculated. When enough of these occur the desync becomes really obvious, and only grows along with how much is rendered on the playlist.
Main contributors:
padding and border properties for .show items (currently is 2px L/R and 1px L/R = 6px)
- Current time density of
120px per 30 minutes: 1 minute = 4 pixels
Significant, wider items are not problematic due to box-sizing = border-box, their widths account for the additional padding and border.
Solutions:
- Increase the default time density
- Thus increasing the width of the guide
- The code is already in place to just modify
rtv.guide.config.markerWidth to see results
- The only way to really win by doing this is ensuring at least 1 pixel per second, which is not fun
- Make relevant small items harder, or impossible, to see by dropping
padding/border
- Reclaim the space by shortening wider items, they may come too late and only soft reset the problem
- Ditch guide (no)
Several small items have such an insignificant width after being calculated. When enough of these occur the desync becomes really obvious, and only grows along with how much is rendered on the playlist.
Main contributors:
paddingandborderproperties for.showitems (currently is2pxL/R and1pxL/R =6px)120pxper 30 minutes: 1 minute = 4 pixelsSignificant, wider items are not problematic due to
box-sizing=border-box, their widths account for the additionalpaddingandborder.Solutions:
rtv.guide.config.markerWidthto see resultspadding/border