Auckland, New Zealand

Brent Abernethy

Systems Developer &
Technical Integrator

I build and maintain practical systems that connect APIs, automation and browser-based applications. My work brings together backend services, installable web apps and self-hosted infrastructure.

I focus on making the parts work together, testing behaviour on real devices and improving the result through use.

Better Media Hub's interactive Earth with orbiting app icons
Better Media Hub · 3D project gatewayExplore the globe ↗ (new tab)
Backend APIs & automationInstallable web applicationsDeployment & ongoing operation

Selected work

Problems solved. Systems you can explore.

Examples from my independently developed, self-hosted portfolio, with the implementation and validation behind each one.

Live projects and implementation notes are linked below.

Browser audio · API integration

Better Radio

Live radio with artwork, visualisations and wireless playback.

An installable live-radio player with changing artwork and track metadata, independent stereo analysis and ten audio-reactive displays. Google Cast and Safari AirPlay integrate playback on compatible TVs and speakers.

Player features

  • Artwork & now-playing informationArtist, song and cover updates, with station-logo fallback.
  • 10 audio-reactive displaysWaveforms, spectrum bars, stereo scopes and analogue-style meters.
  • Independent stereo analysisSeparate left/right levels, smoothing and peak indicators.
  • Chromecast & AirPlayPlayback handoff and device controls on supported browsers and receivers.
  • Responsive station browsingA sliding drawer, expanded mobile list and landscape visualisers.
  • Installable PWAApp-shell caching, installation help and optional screen wake lock.
  • Web Audio
  • HLS
  • Google Cast
  • AirPlay
  • ASP.NET Core
Engineering & validation
Problem
Safari played live HLS audio, but its normal playback route left the audio meters flat.
Approach
A bounded buffered-audio path brings supported live chunks into Web Audio. Overlapping decode helps smooth the joins between chunks.
Evidence
Playback and stereo displays checked on a real iPhone. Unsupported streams fall back to ordinary playback.

The frontend shares one audio-analysis graph across waveforms, spectrum displays and independent left/right meters. The API resolves stream addresses and aggregates metadata. Recent work adds a responsive station drawer and reusable Cast/AirPlay transports. Receiver behaviour is browser- and device-dependent; Android hardware and background listening remain separate test areas.

Media library · Connected playback

Music Player

A music library with visualisations, casting and a custom TV experience.

A self-hosted music-library PWA with album artwork, audio-reactive visualisations and playback on compatible TVs and speakers. Its custom Google Cast receiver shows track information, progress, queue position and playback controls.

SQL-backed library & API

SQL Server Express stores the searchable track catalogue, artist/album/year metadata, artwork thumbnails and track-to-genre relationships. PowerShell scanning feeds the catalogue; ASP.NET Core and Entity Framework Core provide library browsing, search and filters while the original audio files stay on disk.

Player features

  • Artwork & track informationAlbum covers, artist/title and supported system media controls.
  • Audio-reactive visualisationsWaveforms, spectrum displays, stereo scopes and analogue-style meters.
  • Chromecast & custom TV receiverTV artwork, track details, progress, queue position and playback controls.
  • Native Safari AirPlayMusic to compatible TVs and speakers, with automatic next tracks.
  • Library search & discoverySearch artist, song, album, genre and year, with genre and decade filters.
  • Collections & playlistsBrowse Artists, Hits, Playlists, Rock and Shows from one library.
  • Queues, shuffle & repeatPlaylist order and receiver playback stay coordinated across track changes.
  • iPhone lock-screen playbackTrack information and system controls, with automatic next-track playback.
  • Web Audio
  • Google Cast
  • AirPlay
  • ASP.NET Core
  • SQL Server Express
  • Entity Framework Core
Engineering & validation
Problem
Keeping playback position and playlist order consistent when control moves between the browser and a TV.
Approach
Reusable playback transports, signed media links and receiver queue handling coordinate shuffle, repeat and local handoff.
Evidence
TV testing confirmed receiver controls, shuffle and repeat. Simulated-receiver checks cover queue windows and message sizes.

The receiver presents artwork and track information while playback status feeds back into the browser controls. Complete receiver queues can reorder in place; larger collections use bounded queue windows supplied by the open player. AirPlay uses a separate native-audio route. Local visualisations are disabled during Cast and AirPlay playback; the Cast receiver presents artwork and controls. AirPlay audio and controls have been checked on a Sony TV, where a persistent artwork display is not available.

The relational model links tracks and genres through a composite-key join table. Database-backed thumbnails reduce repeated artwork extraction, while Entity Framework Core/LINQ queries expose catalogue browsing and combined text, genre and year filtering through LibraryAPI.

Device sensors · Geospatial calculations

Signal Finder NZ

Turning handset readings into a practical field tool.

A mobile-first PWA for finding New Zealand television transmitters and calculating the direction to point an antenna. Transmitter details include polarity, power, elevation and channel numbers, with area selection and location-quality feedback.

Problem
Noisy compass readings, GPS drift and different browser sensor conventions make a simple directional arrow surprisingly difficult.
Approach
Separate Safari and Android sensor paths, heading smoothing, location-quality checks and offline WMM2025 magnetic-declination correction.
Evidence
A dependency-free ES-module app, with cached transmitter data and app files available offline after the initial download.
  • Geolocation
  • Device orientation
  • WMM2025
  • PWA
Implementation notes

The app calculates true bearings and distances in the browser, keeps heading movement continuous across north, and provides area selection and swipeable transmitter details. Location tracking pauses in the background and refreshes on return. Installation guidance and optional screen wake lock account for browser support.

Backend APIs · Scheduling · Operations

Live Stream Automation — DEMO

One booking interface, with scheduling and execution behind it.

A deployed sports-booking PWA backed by ASP.NET Core, PowerShell and FFmpeg. It combines programme discovery, conflict-aware stream allocation, scheduled playback and operational event history.

Problem
Coordinating programme times and limited extra-stream capacity while keeping existing channels independent of booking activity.
Approach
The API saves guide-only bookings for Sports 1–4 and reserves XTRA1 or XTRA2 for Sport Select and Sports 5–9. Allocation and saving share a file lock. A minute-based worker launches a shared stream supervisor for each reserved slot.
Evidence
Live tests confirmed two simultaneous extra streams, scheduled stops, off-air restoration and automatic booking expiry. Automated checks cover concurrent allocation, conflicts, cancellation and interrupted cleanup. Extended home playback testing reported five hours without observed buffering or glitches after targeted reliability fixes.
  • C# / .NET 8
  • PowerShell
  • FFmpeg / HLS
  • IIS
  • Windows Task Scheduler
Architecture & implementation

Booking and concurrency: ASP.NET Core validates programme times, checks the complete requested interval and reserves one of two extra outputs. Cross-process file locking protects the availability check and save as one operation; atomic file replacement avoids partial schedule writes. Programme details, cancellation and expiry use the same file-backed workflow.

Execution and recovery: One Windows scheduled task checks bookings each minute. A reusable PowerShell supervisor reads the configured HTTP(S) source and remuxes video and audio into HLS without transcoding. Each slot has its own process state, ownership lock, retry loop and HLS-progress watchdog. The supervisor enforces the booked finish time; the worker stops cancelled streams and restores the off-air playlist and segments before clearing state.

Client and operations: The PWA refreshes guide data and progress indicators while retaining an open programme panel. Monthly JSONL events distinguish a requested start from confirmed HLS output and record failures, stop reasons and cleanup. Source URLs are excluded from event records.

Reliability investigation: Defender performance recordings identified repeated scanning of changing timeshift files. Narrow exclusions for generated streaming data and completion-signalled named-pipe writes removed avoidable overhead in the continuous-channel pipeline. These changes were followed by extended playback checks on household TVs.

More deployed work

The wider portfolio.

Related applications and integrations, each built around a different practical use.

Live television · Guide API · Streaming server

Freeview NZ & AU

Television PWAs connecting programme guides, live playback and compatible Cast/AirPlay receivers.

Custom programme-guide API. A C# / ASP.NET Core service indexes XMLTV schedules and supplies current and upcoming programmes as compact JSON. Channel mapping and +1 listings connect guide data to the matching streams.

Self-hosted TVNZ streaming. A streaming server supplies the TVNZ channel streams used by the NZ app, connecting the viewing interface to the underlying media-delivery infrastructure.

The NZ app adds persistent sign-in, shared guest-preview timing and playback recovery. The AU app provides regional Now, Next and Later listings for eight state and territory choices.

  • ASP.NET Core
  • XMLTV / JSON
  • HLS
  • Streaming server
  • Cast / AirPlay
  • PWA

Head-unit interface · Radio · GPS mapping

Better Car Radio

A dashboard designed for Android head units, combining internet radio, track artwork and location instruments in one landscape interface.

A purpose-built touch layout. Large station tiles sit alongside album artwork and now-playing information, with a heading-up map and day/night map styles.

GPS and mapping integration. Leaflet mapping, GPS speed, heading and altitude share the dashboard with saved destinations. The menu provides destination controls, installation and optional screen wake lock.

  • JavaScript
  • Leaflet
  • Geolocation
  • Media metadata
  • PWA

Radio With Pictures (new tab)

A video-library player with fullscreen browsing, native AirPlay and Cast queues that keep Now Playing aligned with the receiver.

Video playback · Queue synchronisation

Better Media Hub (new tab)

A Three.js project gateway with seasonal sunlight, layered clouds, city lights, simulated auroras and responsive 3D navigation.

Three.js · GLSL · Pointer interaction

E-commerce Deployment (new tab)

A self-hosted nopCommerce store covering IIS and SQL Server configuration, PayPal integration and Razor/CSS customisation.

nopCommerce · IIS · SQL Server

Applied skills

The tools behind the work.

Technologies used across the projects above, from backend services through to browser behaviour and deployment.

Backend, data & automation

  • C# and ASP.NET Core APIs
  • PowerShell workers and scheduled processing
  • XML/JSON ingestion and transformation
  • Authentication and session handling
  • SQL Server Express and relational data modelling
  • Entity Framework Core and LINQ queries
  • Metadata ingestion and file-based workflows

Web applications & devices

  • JavaScript modules, HTML and CSS
  • Progressive Web Apps and app-shell caching
  • Web Audio and browser media APIs
  • Google Cast and Safari AirPlay integration
  • Geolocation, orientation and Leaflet mapping
  • Three.js and custom GLSL shaders

Hosting & operation

  • Windows Server and IIS
  • HTTPS and subdomain configuration
  • FFmpeg and HLS media pipelines
  • Browser and physical-device testing
  • Cross-layer fault diagnosis
  • nopCommerce configuration and deployment

How I work

From the requirement to the running system.

01 / Understand

Start with the workflow.

Work out what needs to happen, what the user needs to see and which existing systems need to connect.

02 / Integrate

Build the connections.

Join the API, automation, browser and infrastructure pieces, keeping responsibilities clear and behaviour inspectable.

03 / Validate

Check real behaviour.

Use focused regression checks, browser testing and physical devices. Distinguish simulated checks from device-confirmed results.

04 / Maintain

Operate and refine.

Deploy on self-hosted infrastructure, investigate faults and improve the applications through continued use.

AI-assisted development: I use AI coding tools to help implement and investigate solutions, while driving requirements, integration, testing and deployment.

Systems architecture

How the pieces work together.

These diagrams show the data flows, service boundaries and automation behind the applications, from source feeds through to the user.

Data processing & controlled delivery

Streaming Content Delivery Platform

PowerShell workflows turn external guide and playlist feeds into consistent XMLTV and playlist files. An ASP.NET Core API handles authentication, session controls and delivery to web and administration clients.

External guide sources flow through PowerShell ETL and XMLTV files to PlaylistService API, with authentication, IP session controls and protected EPG delivery, then branch to MyTVGuide and an admin dashboard
Open full-size diagram ↗ (new tab)

Why this structure?

Data preparation is separate from authenticated delivery. Upstream format changes can be handled in the processing pipeline while the clients keep consuming a consistent output.

Open the live platform ↗ (new tab)

Scheduling & automated execution

Live Stream Automation Platform — DEMO

The Booking PWA uses guide and playlist APIs for discovery and an ASP.NET Core booking API for validation and allocation. The API separates guide-only bookings from two scheduled extra-stream outputs, while the worker owns process execution and off-air recovery.

Sports booking demo architecture: guide and playlist APIs feed the Booking PWA and .NET 8 API; a file-backed schedule branches into guide-only bookings for continuous channels and a minute-based worker with shared XTRA1/XTRA2 supervisors; IIS serves HLS and a monthly log records lifecycle events
Open full-size diagram ↗ (new tab)

Why this structure?

The API is responsible for validation and reservations; the worker and supervisors are responsible for execution. Guide-only bookings leave continuous channels running independently. Shared scheduling locks and per-slot ownership protect against overlapping requests and duplicate processes. Completion is checked through HLS output and recorded lifecycle events.

Open the booking demo ↗ (new tab)

Get in touch

Have a practical technical problem?

I’m interested in work involving systems integration, automation, backend services and web applications. My portfolio provides working examples of how I approach those problems.

Desktop playback with album artwork and track controls