Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

meteoblue Community

  1. Home
  2. Website Help
  3. Bug Reports
  4. Scaling and refresh issues with meteogram widgets during high-res screen capture

Scaling and refresh issues with meteogram widgets during high-res screen capture

Scheduled Pinned Locked Moved Bug Reports
1 Posts 1 Posters 47 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      A Offline
      arno9989
      wrote last edited by
      #1

      Hi everyone,
      I’m hoping someone here has navigated this specific technical hurdle. I’ve been using the meteoblue All-in-One widgets to track local conditions for a project I'm working on, and they’ve generally been fantastic for accuracy. However, I’ve hit a snag regarding how the widget renders when I'm under a heavy system load.

      Lately, I've been doing a lot of video editing for some site promotional materials, and I like to include live, high-resolution screen captures of the weather widgets to show real-time changes. The problem is that when my system is processing these high-res video files, the widget seems to struggle to refresh its dynamic layers correctly. Sometimes the wind animation just freezes entirely, or the text becomes incredibly blurry if I try to scale the browser window up for a 4K capture.

      I’ve checked my hardware acceleration settings and tried both the iframe and the direct script embedding, but the stability just isn't there during these high-demand sessions. Is there a way to force a higher priority for the widget’s script, or perhaps a specific CSS trick to lock the resolution so it doesn't degrade when the system is busy? I’m also noticing that the historical data overlays occasionally desync from the current timeline if the page stays open while the background processes are running. If anyone has tips on maintaining widget crispness during resource-heavy tasks, I’d love to hear your thoughts!

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


        • Login

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular