The tech
behind 469Hz

Our event series. Developed together by Rainer Heitzmann and Johannes Zitzelsberger.

Take a closer look
469Hz

469Hz / Event series · SEKTØR / Venue

From ticket
to check-in.

QR scanning right in the web app. Behind it: a protected server, a shared ticket status and clear feedback for the entry team.

Online check-in / System flowInteractive explanation · no live data

Entry team / Smartphone

Browser · /scan
469Hz / ENTRYWEB APP
Ready to scanQR code or manual entry
Alternatively: enter short codeDEMO-CODE

Schematic web app. This illustration does not activate a camera.

REQUEST
Ticket codeHTTPS · JSON
RESPONSE
Check resultTo the same web app

Server side / not on the phone

Check-in API01
POST /api/checkin

Check team login.
Validate input.

Authorized staff only
Ticket database02
Ticket statusQuerying
Check-inNot checked yet

Redemption and check event are processed on the server.

Step 1 of 4

The camera is part of the web app.

The entry team opens the scanner in the smartphone browser and allows camera access. The web app reads the QR code from the guest’s ticket – on their screen or on paper. Alternatively, the short code can be entered manually.

QR detection: ZXing in the browser · prefers the rear camera · no separate app download

Step by step at your own pace – or as a sequence.

Technical insight: what happens behind the scan

Client & interface

React / Next.js with ZXing for QR detection. The browser decodes the camera image locally and sends the code as JSON. The scanner page and API require a valid team session.

Tokens instead of personal data

The QR code contains a random ticket token, not a name or email address. The server matches its hash against the ticket record. The readable short code is a second way to enter it.

Preventing double redemption

In PostgreSQL, the switch to “redeemed” only happens while the ticket is still valid. The conditional change and the check event share one transaction – not just a local counter on the smartphone.

Handling errors deliberately

No offline queue and no automatic approval on connection errors. Server responses are not cached. After a successful camera scan, scanning pauses; without camera access, manual code entry remains available.

This shows the online ticket check-in. All states shown are local examples; no tickets are checked or changed.

From model
to space.

PSL / Replica for visualization
PSL replica with two bass cabinets and one top cabinet2 bass cabinets
1 top cabinet

Replica based on outer dimensions and photo reference

Replica built to dimensions – not a technical model.

The real sound system is from Pro Sound & Light (PSL). The model shown was rebuilt from published outer dimensions and photo references for the room visualization. It shows proportions and appearance, not the technical interior design.

No manufacturer CAD, no acoustic simulation and no construction or rigging plan. The separated cabinets and their spacing are for illustration only.

Capture the space.
Take it further digitally.

  1. Capture

    Record the geometry and surfaces of the existing space as a starting point.

  2. Prepare

    Check the raw data, optimize textures for the browser and keep gaps in the capture visible.

  3. Develop

    Discuss variants on a separate model base without overwriting the source data.

Venue SEKTØR II / Mainfloor

The venue as it was captured. With its surfaces and the traces of the scan.

Mainfloor · actual raw scan with gaps in the capture. A reference for the visualization, not a verified survey. Missing surfaces are not filled in automatically here.
Floor plan & raw geometry
Derived floor plan of the Mainfloor with room outline, center point and radial guide lines
Derived floor plan reference · not a verified dimensional plan
Source data of the room capture with floor plans and raw geometry of both floors
Source data of the room capture

469Hz in pictures
and motion.

Project film

Animation without sound.