RTSPView 1.0.48

RTSPView 1.0.48

This stable release promotes all changes from 1.0.48-beta.2 through Patch 2, on top of the complete Stable 1.0.47 baseline.

Picture-in-picture layouts

• Both Standard View and Automation layout editors preview overlay snapshots with their saved size, shape, opacity and framing. Automation-only overlays are shown as placement previews; live visibility still follows automation rules.
• Click an overlay directly to select it, drag it within its host camera, enter exact positions, or use arrow keys (Shift for larger steps). Small overlays remain clickable over camera resize handles.
• Remove from this layout hides an overlay only in the selected layout, including when an automation rule requests it. Restore to this layout brings it back; other layouts retain their own visibility and placement.
• Moves and removals support Undo/Redo and the normal layout save/apply controls. The Windows viewer honors these settings in standard and resolved automation layouts.
• Use shared position clears a local position override. Shared source, shape and display-mode settings remain available through Edit shared overlay settings.

Dashboard consistency

• Corrected Display settings spacing and grouped monitor selection, identification and help.
• Consistent rounded cards, borders and spacing across settings, diagnostics, stream inventory and plugin panels; maintenance action cards have equal sizes.
• Aligned picture-in-picture actions and reduced excessive inspector gaps.
• Overlay deletion errors appear above the sidebar in an accessible dialog that identifies blocking layout or automation references, including disabled rules.

Optional application patches

Settings → Updates → Patches shows the installed version, available patch and check times, with Check for new patches and Install patch controls.

Automatically install patches during scheduled restarts is off by default. When enabled, compatible patches for the installed release are checked daily and installed at an enabled Live View restart schedule, using an enabled maintenance helper that supports patches. Installation restarts the whole application and briefly interrupts the stream wall and dashboard. No enabled schedule means no automatic installation.

Turning auto-install off retains daily checks and manual installation and cancels pending automatic handoff unless the installer has already started. Full version upgrades and channel switches still require confirmation. Streaming-component updates keep their separate policy.

Future stable patches use identities such as 1.0.48-patch.1 and apply only to their exact base release. Patches currently use the full verified installer package. See application patches for details.

Installing

Choose Stable in Settings → Updates, check for updates, and install 1.0.48, or run the attached Windows x64 installer. Existing settings are retained. Changing the selected channel alone does not install anything.

Users on 1.0.48-beta.2 or either beta patch should install this full stable release to move onto the 1.0.48 stable patch baseline. Beta patches are not stable patches.

Validation

The beta releases passed configuration, update, scheduler, native viewer and JavaScript regression checks, plus native synthetic streaming playback. Isolated browser checks verified dashboard changes, patch controls, direct overlay selection/dragging, keyboard movement, removal/restoration, Undo/Redo, saving/reloading and layout isolation. The stable release pipeline repeats the full regression suite and native playback checks before publication. Automated validation does not install software or modify live camera-host settings.

RTSPView 1.0.48-beta.2-patch.2

RTSPView 1.0.48-beta.2 · Patch 2

Picture-in-picture camera overlays can now be selected, moved and removed directly in both Standard View and Automation layouts.

Changes

• Click an overlay in the preview to select it and open its controls. Small overlays remain clickable when they overlap a host camera's resize handles.
• Drag within the host camera, enter exact horizontal/vertical positions, or use arrow keys (Shift for larger steps).
• Remove from this layout hides the overlay only in that layout. Other layouts retain it, and Restore to this layout brings it back. Layout removal also takes precedence over automation rules that show the overlay.
• Moves and removals support Undo/Redo and use the existing layout save/apply controls. The Windows viewer honors saved positions and removals in standard and automation layouts.
• Use shared position clears a layout's position override. Edit shared overlay settings still controls the common source, shape and display mode.

Installing

On Beta 1.0.48-beta.2 Patch 1, open Settings → Updates → Patches, choose Check for new patches, then Install patch. This cumulative patch also supports the original 1.0.48-beta.2 release through its Application patches controls.

Alternatively, run the attached Windows x64 installer. Existing settings are retained; installation briefly restarts the application and stream wall. Optional automatic patch installation still uses your enabled scheduled restart.

This patch applies only to the 1.0.48-beta.2 base and does not replace the normal Beta or Stable release listing.

Validation

Release build, configuration persistence/validation checks, native viewer checks and JavaScript regression checks passed locally. Browser verification covered direct selection, pointer dragging, keyboard movement, removal, restore, Undo/Redo, saving/reloading, and isolation between standard and automation layouts. The release pipeline runs the regression suite and native synthetic streaming playback before publication. No live camera-host installation was performed during testing.

streaming-1792938576

Automatically tested streaming components: yt-dlp 2026.10.23.233055dev, Streamlink 8.6.2. Requires RTSPView streaming updater protocol 1. Website availability is not guaranteed.

streaming-1792850758

Automatically tested streaming components: yt-dlp 2026.10.23.233055dev, Streamlink 8.6.2. Requires RTSPView streaming updater protocol 1. Website availability is not guaranteed.

streaming-1792768486

Automatically tested streaming components: yt-dlp 2026.10.21.233146dev, Streamlink 8.6.2. Requires RTSPView streaming updater protocol 1. Website availability is not guaranteed.

streaming-1792682674

Automatically tested streaming components: yt-dlp 2026.10.21.233146dev, Streamlink 8.6.2. Requires RTSPView streaming updater protocol 1. Website availability is not guaranteed.

RTSPView 1.0.48-beta.2-patch.1

RTSPView 1.0.48-beta.2 · Patch 1

This patch applies to Beta 1.0.48-beta.2 and fixes missing picture-in-picture previews and hard-to-find patch controls.

Changes

• Standard and automation layout editors now show picture-in-picture snapshots with their saved size, shape, opacity and framing. Automation-only overlays appear as placement previews; their live visibility still follows automation rules.
• Selecting a focus preview camera also previews that camera's overlays. Each camera tile has direct overlay settings links, and the layout toolbar provides a Picture in picture panel.
• Saving overlay settings refreshes layout previews while retaining unsaved layout drafts.
• Settings → Updates has a dedicated Patches section showing the installed version, available patch, check times, Check for new patches and Install patch. The install button remains visible and is disabled when no patch is available.
• Automatic installation during scheduled restarts remains optional and off by default.

Installing

On Beta 1.0.48-beta.2, open Settings → Updates and click Check for updates, then Install patch now under Application patches. After this patch is installed, use the new Patches section for future patch checks and installation.

Alternatively, download and run the Windows x64 installer attached to this release. Installation briefly stops the stream wall and restarts the application. This is a full installer package; existing settings are retained.

This patch does not replace Stable 1.0.47 or the normal Beta 1.0.48-beta.2 release listing. Automatic patch discovery requires that exact beta base.

Validation

Focused browser checks cover overlay previews and settings navigation, preservation of layout drafts, patch checks, installation confirmation and simulated handoff, no-patch state, and narrow-screen layout. Automated release checks and native synthetic streaming playback run before publication. Testing does not install the patch on a live camera host.

RTSPView 1.0.48-beta.2

RTSPView 1.0.48-beta.2

This beta starts from Stable 1.0.47, including every change through 1.0.47-beta.26. It adds dashboard consistency fixes and the updater needed for future small application patches. Stable remains 1.0.47.

Dashboard fixes

• Correct Display settings spacing and keep monitor selection, identification and help together.
• Use consistent rounded cards, borders and spacing across settings, diagnostics, stream inventory and plugin panels; maintenance action cards have equal sizes.
• Align picture-in-picture actions and reduce excessive inspector gaps.
• Show deletion errors in an accessible dialog above the sidebar. Referenced overlays remain protected; the dialog identifies the layouts or automation rules that must be changed before deletion, including disabled rules that retain references.
• Preserve the newer widget and navigation behavior from Stable 1.0.47.

Optional application patches

Settings → Updates includes Automatically install patches during scheduled restarts, off by default. When enabled, compatible patches for the exact installed release are checked daily and installed at an enabled Live View restart schedule. A patch restarts the whole application, including the dashboard; the maintenance helper must be enabled and support patches.

Turning auto-install off preserves daily checks and Install patch now. Opting out during preparation prevents installer handoff. An installer already started cannot be canceled by changing this preference. Full version upgrades and channel switches still require confirmation; no schedule means no automatic patch installation.

Future patches use identities such as 1.0.48-beta.2-patch.1, keeping the base release unchanged. Patch artifacts use the same verified installer packaging and publication checks, do not replace the advertised Stable release, and never appear as ordinary beta upgrades. The initial implementation still downloads a full installer; it does not hot-swap the dashboard or add transactional binary rollback. Streaming resolver updates retain their existing separate policy.

Install this beta normally to receive the updated Controller and maintenance helper. See application patches for scheduling, publisher instructions and verification limits.

Validation

Release builds and isolated checks cover patch selection, exact-base compatibility, preference persistence, opting out during preparation, scheduler behavior, authentication/CSRF, verified service-worker installation with mocked host actions, and existing update-helper failure paths. Browser checks cover the new toggle, manual confirmation and the dashboard fixes. Tests use synthetic streams and packages; they do not install updates or restart a user's host. A real unattended patch upgrade on a disposable Windows installation remains a rollout validation item.

The beta.1 build did not publish an installer because a fixed-delay native animation check failed on the hosted runner. This build waits for observed animation states, including intermediate opacity and cancellation, without changing production animation behavior.

RTSPView 1.0.47

Changes across the 1.0.47 beta series

This section consolidates the complete beta run, including the final padding-control adjustment.

Plugins and new widgets

• The Plugins page groups related capabilities and explains each switch. Weather, Aircraft, System stats, Date & time, Streamlink, yt-dlp, ONVIF, Picture in picture and Automations are all opt-in on new installations. Upgrades preserve existing plugin behavior; the new system and clock plugins start disabled.
• Disabling a plugin stops its runtime work and hides its controls while retaining saved settings. Direct camera streams do not require website resolver plugins. Auto source mode uses only enabled resolvers. MQTT and Tapo rules share the Automations switch.
• System stats displays this Windows host's CPU/GPU utilization, RAM use and available CPU/GPU temperatures, with temperature-unit and heading controls. Missing or stale measurements remain unavailable rather than appearing as zero; temperature availability depends on the host's sensors.
• Date & time adds a live clock with a selected time zone, 12/24-hour display, optional seconds, date and weekday, and long, short or ISO date formats. Time-zone conversion respects daylight saving.

Layout editing and responsive presentation

• Weather and aircraft are independent layout content rather than being tied to a camera. Layouts support up to 64 widgets, including system stats and clocks. Removing a camera does not delete independent widgets.
• Add content combines camera and enabled-widget choices. The layout toolbar uses available desktop width; selection, the content inspector, Enter to edit, keyboard movement/resizing, Delete, Undo and Redo support the editing workflow.
• New widgets use grid placement with row/column spans, weighted tracks and orientation changes. Floating placement supports edge/corner resizing, positioning presets and precise placement. Existing floating geometry is preserved during migration.
• Dialogs preview the actual target dimensions over the layout's camera snapshots. Monitor and native Live View follow shared responsive sizing rules. Content uses available width and height, with lower-priority rows omitted before primary readings become unreadable. Platform rendering is not guaranteed to be pixel-identical.
• Background color/opacity and content opacity are independent. Text, images and credits follow content opacity; the background can remain visible or be made fully transparent.
• Settings migration retains existing widgets and creates rollback backups, including settings.json.before-independent-widgets.json and settings.json.before-responsive-widgets.json when their respective migrations apply. Use the appropriate older backup when rolling back to an older binary.

Aircraft

• ADSB.lol supplies nearby traffic, filtered by location, radius and optional altitude limits. Persistent widgets and conditional camera replacements support empty/stale/unavailable states; conditional replacements return to the camera when eligible traffic is absent.
• Cards display at most two aircraft. Responsive/photo-emphasis views and two-aircraft boards retain a stable selection during ordinary updates and rotate through nearby traffic every 20 seconds. Departure, expiry and empty-feed handling prevent stale aircraft lingering.
• Callsign/tail identifiers remain readable, two-aircraft columns align at the top, and the optional Nearby aircraft heading can be hidden to reclaim space. Unknown detail rows are omitted. Full model names and registered owners use adsbdb and verified FAA records when available; lookup data can differ from other flight-tracking services.
• Users can reorder aircraft detail fields and toggle optional information. Earlier fields take priority when space is limited. The primary identifier remains fixed, and the aircraft photo control is grouped with information choices but is not reorderable.
• Photo lookup uses Planespotters, Airport-Data and attributed Wikimedia Commons fallbacks, including representative model/family images where available. Representative photos are labelled; a different livery may appear. Coverage is provider-dependent and is not guaranteed for every aircraft.
• Native image requests follow validated provider redirects, identify the application and retry failures after a cooldown. Diagnostic logs trace photo lookup/download/decode outcomes. Loaded photos use available space, preserve aspect ratio and have rounded corners; missing or failed images do not reserve an empty image box.
• Two-aircraft cards allocate remaining height to photos, keep both columns aligned and place small photo/source credits at the bottom. Photo and ADS-B attribution remain visible when their associated content fits.
• Wait for aircraft photo optionally holds an aircraft until its image is ready. A configurable 1–60 second timeout (10 seconds by default) or a failed download permits a text-only card; a later image does not pop into that encounter after fallback.
• Fade transitions cover appearance, disappearance, one/two-plane changes, rotation between pairs and arriving photos. Old content fades out before new content fades in. Routine reading updates do not restart the transition. Entrance and exit durations are independent, 0–5,000 ms; zero is instant. Try 800 ms each for gentler transitions.

Weather

• Temperature and supporting readings grow with the card while source attribution stays small. Wide cards can distribute information across two columns; smaller cards prioritize temperature, high/low and condition. Left, center and right text alignment work in preview and Live View.
• Optional backgrounds cover all 29 documented API condition codes: clear/partly cloudy/overcast, fog/rime fog, drizzle/rain/showers, freezing precipitation, snow/snow grains/snow showers, thunderstorms and hail. Related codes share effects while retaining their exact condition labels. Unknown or unavailable conditions use a plain fallback.
• Weather background and Animate weather background are separate switches. Clear scenes distinguish day/night. Background opacity controls the effect independently of content opacity, and animation can be disabled for a quiet display.
• Content padding is under Advanced appearance. It controls minimum edge spacing and can reach zero, with responsive limits for small cards. Content remains vertically centered: reducing padding does not resize the card or necessarily remove the space above/below the text. Reduce card height to remove that extra vertical space.

Administration, startup and validation

• Refreshing administration restores the selected section and subtab instead of always returning to Monitor. Unsaved drafts still require saving before a reload.
• Windows startup can be inspected, enabled, disabled or repaired through Settings → Display → Windows startup. The installer and web setting use the same helper for the intended interactive Windows account, a 20-second sign-in delay and battery operation. A new sign-in resumes Live View despite an earlier intentional stop; watchdog recovery within the same session still respects that stop. This does not configure automatic Windows login.
• Regression coverage includes plugin gating, migration/persistence, native/browser sizing and weather-code parity, aircraft metadata and photo fallbacks, fade timing/cancellation, real native overlays, and synthetic streaming playback. Browser fixtures exercise responsive sizes, editing and photo/transition states. These checks do not guarantee third-party feed or hardware sensor availability.

RTSPView 1.0.47-beta.26

Changes across the 1.0.47 beta series

This section consolidates the complete beta run, including the final padding-control adjustment.

Plugins and new widgets

• The Plugins page groups related capabilities and explains each switch. Weather, Aircraft, System stats, Date & time, Streamlink, yt-dlp, ONVIF, Picture in picture and Automations are all opt-in on new installations. Upgrades preserve existing plugin behavior; the new system and clock plugins start disabled.
• Disabling a plugin stops its runtime work and hides its controls while retaining saved settings. Direct camera streams do not require website resolver plugins. Auto source mode uses only enabled resolvers. MQTT and Tapo rules share the Automations switch.
• System stats displays this Windows host's CPU/GPU utilization, RAM use and available CPU/GPU temperatures, with temperature-unit and heading controls. Missing or stale measurements remain unavailable rather than appearing as zero; temperature availability depends on the host's sensors.
• Date & time adds a live clock with a selected time zone, 12/24-hour display, optional seconds, date and weekday, and long, short or ISO date formats. Time-zone conversion respects daylight saving.

Layout editing and responsive presentation

• Weather and aircraft are independent layout content rather than being tied to a camera. Layouts support up to 64 widgets, including system stats and clocks. Removing a camera does not delete independent widgets.
• Add content combines camera and enabled-widget choices. The layout toolbar uses available desktop width; selection, the content inspector, Enter to edit, keyboard movement/resizing, Delete, Undo and Redo support the editing workflow.
• New widgets use grid placement with row/column spans, weighted tracks and orientation changes. Floating placement supports edge/corner resizing, positioning presets and precise placement. Existing floating geometry is preserved during migration.
• Dialogs preview the actual target dimensions over the layout's camera snapshots. Monitor and native Live View follow shared responsive sizing rules. Content uses available width and height, with lower-priority rows omitted before primary readings become unreadable. Platform rendering is not guaranteed to be pixel-identical.
• Background color/opacity and content opacity are independent. Text, images and credits follow content opacity; the background can remain visible or be made fully transparent.
• Settings migration retains existing widgets and creates rollback backups, including settings.json.before-independent-widgets.json and settings.json.before-responsive-widgets.json when their respective migrations apply. Use the appropriate older backup when rolling back to an older binary.

Aircraft

• ADSB.lol supplies nearby traffic, filtered by location, radius and optional altitude limits. Persistent widgets and conditional camera replacements support empty/stale/unavailable states; conditional replacements return to the camera when eligible traffic is absent.
• Cards display at most two aircraft. Responsive/photo-emphasis views and two-aircraft boards retain a stable selection during ordinary updates and rotate through nearby traffic every 20 seconds. Departure, expiry and empty-feed handling prevent stale aircraft lingering.
• Callsign/tail identifiers remain readable, two-aircraft columns align at the top, and the optional Nearby aircraft heading can be hidden to reclaim space. Unknown detail rows are omitted. Full model names and registered owners use adsbdb and verified FAA records when available; lookup data can differ from other flight-tracking services.
• Users can reorder aircraft detail fields and toggle optional information. Earlier fields take priority when space is limited. The primary identifier remains fixed, and the aircraft photo control is grouped with information choices but is not reorderable.
• Photo lookup uses Planespotters, Airport-Data and attributed Wikimedia Commons fallbacks, including representative model/family images where available. Representative photos are labelled; a different livery may appear. Coverage is provider-dependent and is not guaranteed for every aircraft.
• Native image requests follow validated provider redirects, identify the application and retry failures after a cooldown. Diagnostic logs trace photo lookup/download/decode outcomes. Loaded photos use available space, preserve aspect ratio and have rounded corners; missing or failed images do not reserve an empty image box.
• Two-aircraft cards allocate remaining height to photos, keep both columns aligned and place small photo/source credits at the bottom. Photo and ADS-B attribution remain visible when their associated content fits.
• Wait for aircraft photo optionally holds an aircraft until its image is ready. A configurable 1–60 second timeout (10 seconds by default) or a failed download permits a text-only card; a later image does not pop into that encounter after fallback.
• Fade transitions cover appearance, disappearance, one/two-plane changes, rotation between pairs and arriving photos. Old content fades out before new content fades in. Routine reading updates do not restart the transition. Entrance and exit durations are independent, 0–5,000 ms; zero is instant. Try 800 ms each for gentler transitions.

Weather

• Temperature and supporting readings grow with the card while source attribution stays small. Wide cards can distribute information across two columns; smaller cards prioritize temperature, high/low and condition. Left, center and right text alignment work in preview and Live View.
• Optional backgrounds cover all 29 documented API condition codes: clear/partly cloudy/overcast, fog/rime fog, drizzle/rain/showers, freezing precipitation, snow/snow grains/snow showers, thunderstorms and hail. Related codes share effects while retaining their exact condition labels. Unknown or unavailable conditions use a plain fallback.
• Weather background and Animate weather background are separate switches. Clear scenes distinguish day/night. Background opacity controls the effect independently of content opacity, and animation can be disabled for a quiet display.
• Content padding is under Advanced appearance. It controls minimum edge spacing and can reach zero, with responsive limits for small cards. Content remains vertically centered: reducing padding does not resize the card or necessarily remove the space above/below the text. Reduce card height to remove that extra vertical space.

Administration, startup and validation

• Refreshing administration restores the selected section and subtab instead of always returning to Monitor. Unsaved drafts still require saving before a reload.
• Windows startup can be inspected, enabled, disabled or repaired through Settings → Display → Windows startup. The installer and web setting use the same helper for the intended interactive Windows account, a 20-second sign-in delay and battery operation. A new sign-in resumes Live View despite an earlier intentional stop; watchdog recovery within the same session still respects that stop. This does not configure automatic Windows login.
• Regression coverage includes plugin gating, migration/persistence, native/browser sizing and weather-code parity, aircraft metadata and photo fallbacks, fade timing/cancellation, real native overlays, and synthetic streaming playback. Browser fixtures exercise responsive sizes, editing and photo/transition states. These checks do not guarantee third-party feed or hardware sensor availability.