0.29.4

Viso Player 0.29.4

Current USB image: viso-player-0.29.4.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.27.0, 0.27.1, 0.28.0, 0.29.0, 0.29.1, 0.29.2, or 0.29.3 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is fixed

• The stream uses the quality you chose. A source that is already on a display is no longer reduced to 720p and a software encoder. 720p, 1080p, 4K, and Custom keep the resolution, frame rate, bitrate, and codec on the card. Automatic still tries the GPU encoder first. If that encoder cannot open, software encode keeps the same resolution.
• YouTube sees one picture per frame. Each picture is stamped on the frame interval of the rate you chose. A machine that delivers frames a little late no longer makes the platform read the upload as more video than the seconds that passed. Audio is counted from the samples that were captured, on the same clock as the picture.

Stream setups, recording jobs, and the files under /var/lib/viso-player/recordings stay on the machine.

What you should see after installing

1. Write viso-player-0.29.4.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Streams. Choose 1080p, or the quality you want, then Start. The card’s encoder matches that choice. On YouTube, stream health should no longer say the encoder is sending faster than real time because the picture clock ran ahead.

Already on 0.24.0 through 0.29.3

Open Device → Updates, check, and apply 0.29.4. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.29.4.iso	Try or Install. Install erases the target disk.
viso-player-0.29.4.iso.sha256	Verify the image
viso-player-0.29.4.tar.gz	In-place update for machines already on 0.24.0 through 0.29.3.
viso-player-0.29.4.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.29.4.iso	7a10856cf0190fb607dcce26573eebfe24d8d9e6c792fe0af2b55e4ce3c18cd0
viso-player-0.29.4.tar.gz	124a4b4f6475c54b90cdb231afa3ee458c219339616641660d88b09413e6bacc

0.29.3

Viso Player 0.29.3

Current USB image: viso-player-0.29.3.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.27.0, 0.27.1, 0.28.0, 0.29.0, 0.29.1, or 0.29.2 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is fixed

• Recorded picture and sound stay together. A recording stamps video and audio from the source clock. A signal running at 29.97 fps that was announced as 29 fps no longer drifts by about one second every half minute. This applies to every quality profile, and to both inputs and Viso streams.
• A skipped picture stays a gap. If the recorder misses a frame, that gap is in the video timeline. The audio keeps its own clock instead of being squeezed to match.

Files recorded before this update are unchanged.

What you should see after installing

1. Write viso-player-0.29.3.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Record a Viso stream for a few minutes, then play the file. Picture and sound still match at the end.

Already on 0.24.0 through 0.29.2

Open Device → Updates, check, and apply 0.29.3. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.29.3.iso	Try or Install. Install erases the target disk.
viso-player-0.29.3.iso.sha256	Verify the image
viso-player-0.29.3.tar.gz	In-place update for machines already on 0.24.0 through 0.29.2.
viso-player-0.29.3.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.29.3.iso	1547dd88d2ad38e821c00a21a5221cb5e103075a84ebd759bd59c39981096289
viso-player-0.29.3.tar.gz	ff3ab2426bcc82ec68853378e68f42f883d3ae5c63703454f34f77da5263ce32

0.29.2

Viso Player 0.29.2

Current USB image: viso-player-0.29.2.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.27.0, 0.27.1, 0.28.0, 0.29.0, or 0.29.1 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is fixed

• Recording starts on its own. Starting a recording no longer waits for the capture driver install. A stream recording writes a file as soon as the picture arrives. An input recording waits for that input's signal.
• Live streaming starts on its own. Sending a source to a live platform no longer waits for the capture driver install.
• Recorded files. While the recorder is not running, the recording card stays idle and Recorded files says the recording service is not reporting state.

What you should see after installing

1. Write viso-player-0.29.2.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Start a recording of a Viso stream. A file appears under Recorded files while that recording is running.

Already on 0.24.0 through 0.29.1

Open Device → Updates, check, and apply 0.29.2. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.29.2.iso	Try or Install. Install erases the target disk.
viso-player-0.29.2.iso.sha256	Verify the image
viso-player-0.29.2.tar.gz	In-place update for machines already on 0.24.0 through 0.29.1.
viso-player-0.29.2.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.29.2.iso	a1daf9f97870a35a358cf6f84861516c6cf1c9c1ac19ee3950e483589618bf55
viso-player-0.29.2.tar.gz	3bcaf2244e5b824bd5a0fb9b31bba4d44f56de7aa94bcb01edf114da86601da1

0.29.1

Viso Player 0.29.1

Current USB image: viso-player-0.29.1.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.27.0, 0.27.1, 0.28.0, or 0.29.0 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is fixed

• Lowest quality. A display set to lowest bandwidth decodes the small picture and puts it on the screen. The picture keeps moving. Audio no longer continues alone on the last high-quality frame.
• Back to highest. Choosing highest again shows the full picture and keeps it moving.

What you should see after installing

1. Write viso-player-0.29.1.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. On a display, choose lowest bandwidth. The picture becomes the small rendition and keeps moving. Choose highest again and the full picture comes back.

Already on 0.24.0 through 0.29.0

Open Device → Updates, check, and apply 0.29.1. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.29.1.iso	Try or Install. Install erases the target disk.
viso-player-0.29.1.iso.sha256	Verify the image
viso-player-0.29.1.tar.gz	In-place update for machines already on 0.24.0 through 0.29.0.
viso-player-0.29.1.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.29.1.iso	343a70f9a183db197ad0e4a2ffd092f73081454c41f40b364c16b5c004be9ab5
viso-player-0.29.1.tar.gz	339b78a5b1ff191c24299f9228091a5055a6b9b8f66bad5838ad961c3475e32c

0.29.0

Viso Player 0.29.0

Current USB image: viso-player-0.29.0.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.27.0, 0.27.1, or 0.28.0 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is new

• Streams. Send any input or Viso source to a live platform. YouTube, Twitch, Facebook, Kick, Trovo, and Vimeo fill in the server. TikTok, LinkedIn, X, and Custom RTMP take the server URL from that platform. Each stream is a card, with a name, a server, a stream key, a source, a codec, a quality, and audio. An input and a source can go out at the same time, and the same source can go to more than one destination. There is no limit on count. Start all and Stop all sit above the cards. A card turns green while that stream is live.
• Picture and sound. The platform receives H.264 with AAC. Quality is 720p, 1080p, or 4K at 30 fps, or Custom. The codec is Automatic, H.264 VA-API, H.264 Quick Sync, or H.264 software. Audio can be turned off.
• The screen stays live. An input is read from the capture picture. A Viso source is received on its own connection, so streaming does not take frames or sound away from a display. A destination that falls behind counts dropped frames on that stream and reconnects.
• The key stays on the player. Show and Hide reveal it on the card. It is not written to logs. Platform, server, key, source, codec, quality, and audio stay locked while that stream is live. The setup is kept across a reboot.

Also in this version

• Recorded files. The list updates while a recording is running. A file that is still open shows In progress. Play stays off until the file is closed.
• GPU. The header shows each engine on the card: Copy, Render, Video, and Video Enhance. A live stream’s encoder is included in that reading.

What you should see after installing

1. Write viso-player-0.29.0.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Streams → Add stream. Choose a platform, paste the stream key, choose a source, then Start.

Already on 0.24.0 through 0.28.0

Open Device → Updates, check, and apply 0.29.0. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.29.0.iso	Try or Install. Install erases the target disk.
viso-player-0.29.0.iso.sha256	Verify the image
viso-player-0.29.0.tar.gz	In-place update for machines already on 0.24.0 through 0.28.0.
viso-player-0.29.0.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.29.0.iso	7470425c195530ece80bb32b331fb131d729b2c3baa619a63720626899c60e29
viso-player-0.29.0.tar.gz	95257bfb99e05dd4a18479f950c8d6111fb21dd3b596858ccda473bfd761b651

0.28.0

Viso Player 0.28.0

Current USB image: viso-player-0.28.0.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, 0.27.0, or 0.27.1 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is new

• Recording. Add as many recordings as you need. Each one is a card, with a name, a source, a codec, and a quality. An input and a stream can be recorded at the same time, and the same source can be recorded more than once. There is no limit on count, duration, or resolution. Record all and Stop all sit above the cards. A card turns red while that recording is running.
• Inputs and streams. An input is read from the capture picture before it is published. A stream is received on its own connection, so recording does not take frames away from a display.
• Codec and quality. Automatic, H.264 VA-API, H.264 Quick Sync, or H.264 software, with the same quality profiles as Inputs. The file is a fragmented MP4 with AAC audio.
• Dropped frames. Each recording shows how many frames the source produced that this recording did not write. The number stays on the file after it stops.
• Recorded files. A second section lists every file on this player, with the recording details, the codec, and the quality. Play it in the browser, download the MP4, or delete the file.

What you should see after installing

1. Write viso-player-0.28.0.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Recording → Add recording. Choose an input or a stream, then Start.

Already on 0.24.0 through 0.27.1

Open Device → Updates, check, and apply 0.28.0. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.28.0.iso	Try or Install. Install erases the target disk.
viso-player-0.28.0.iso.sha256	Verify the image
viso-player-0.28.0.tar.gz	In-place update for machines already on 0.24.0 through 0.27.1.
viso-player-0.28.0.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.28.0.iso	0bb04fc8fea2be0788575c39eb89e60c7ff870063b5b914014a83ce953f8c43a
viso-player-0.28.0.tar.gz	d9b15a9f566eaa357be637b88dab217ea171588ddd00b3af94015f973ca872e4

0.27.1

Viso Player 0.27.1

Current USB image: viso-player-0.27.1.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, or 0.27.0 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is new

• Transport on Network → Viso Communication. Choose Automatic, UDP, or TCP. Apply restarts the player.
• Automatic. The player sends the UDP JOIN. If the Gateway does not answer within 1 second, the player opens TCP to the announced control port and picture and sound come back on that connection. If TCP drops, it tries UDP again.
• UDP. Only the UDP JOIN. Silence does not open TCP.
• TCP. Connects to the control port immediately and does not send a UDP JOIN. If the connection fails, it tries TCP again.
• A player with no saved choice uses Automatic.
• Capture sends TCP. An HDMI input published by this player listens on the announced control port, the same way Viso Gateway does. Picture and sound go back on that connection. UDP on the same port is unchanged.
• Live transport on each display. Under Connected, the card shows UDP or TCP for the session that is carrying the picture. It appears when the session connects.

What is fixed

• Two displays, one source. A display that is following a live shared decode waits for that picture. It no longer treats the wait as a dead session and tears the shared decode down.
• A display that blinks off the probe. A sink that was live and then fails the probe keeps the session through a short grace. A closed lid still stops immediately, and a cable that stays out still ends the receiver.

Viso Gateway

Pair with Viso Gateway 0.5.0 when you use TCP. Gateway 0.5.0 listens for UDP and TCP on the announced control port. UDP still works with Gateway 0.4.0 and 0.3.1. An older Gateway does not accept the TCP connection.

What you should see after installing

1. Write viso-player-0.27.1.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Network → Viso Communication → Transport — Automatic, UDP, or TCP. Apply restarts the player.

Already on 0.24.0 through 0.27.0

Open Device → Updates, check, and apply 0.27.1. You do not need to reinstall from USB unless you prefer a clean install.

Downloads

File	Purpose
viso-player-0.27.1.iso	Try or Install. Install erases the target disk.
viso-player-0.27.1.iso.sha256	Verify the image
viso-player-0.27.1.tar.gz	In-place update for machines already on 0.24.0, 0.25.0, 0.26.0, 0.26.1, or 0.27.0.
viso-player-0.27.1.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.27.1.iso	e12130d2480f094ac378fd2ae39100612279cb43a2695ffc628774d854bc50ff
viso-player-0.27.1.tar.gz	fdb5bae3ed80a42f5cda0444f1ecbe8eb3019c7f71d3c76f2b27c21ae37ce036

0.27.0

Viso Player 0.27.0

Current USB image: viso-player-0.27.0.iso. Machines already on 0.24.0, 0.25.0, 0.26.0, or 0.26.1 can apply this build from Device → Updates. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is new

• Inputs tab. A player with a Blackmagic capture device now turns its HDMI input into a Viso source. The new Inputs tab shows signal, format, encoder, receivers, and dropped frames for each input, and lets you name, enable, or disable it.
• One card per capture device. Each device gets its own card, with a tab per connector (on the UltraStudio Recorder 3G, HDMI and SDI). Each tab shows the input's name, with the connector below it. A card appears as soon as a device is connected and shows Disconnected when it is unplugged. The list stays empty until a device is connected.
• Devices you name and keep. Click a device's title to rename it. The player remembers every device it has seen, with its name and input settings, across reboots and unplugging, and connecting another device does not change the ones already there. A device that is disconnected and no longer needed can be deleted from its card, together with its input settings.
• Captured video on the network. Each enabled input is published as a viso:// source that other players and Gateways can pick like any other source. It follows format changes, cable pulls, and device replugs without editing routes.
• Captured video on the same player. The player's own displays can show its inputs directly, without going through the network.
• Blackmagic driver included. The ISO, Try, and the OTA package include Blackmagic Desktop Video 16.4a1. Try has it ready to use. An installed player builds it during install or on the first start after the update; that build needs a network connection, and without one it retries on the next start or boot. The OTA package is larger than usual (about 315 MB).
• Conversion and H.264 on the GPU. On Intel GPUs the player converts and scales the captured picture on the GPU and encodes it there (VAAPI), so a 1080p60 input uses a fraction of the CPU it used to. If a GPU step is not available, it falls back to copying through the GPU and then to the CPU (libx264), and the Inputs tab says which path is in use and why.
• Quality settings per input. Each input has a profile: Automatic, Low latency, Best quality, Save CPU, or Custom. Advanced exposes every setting that affects the picture: GPU or CPU conversion, scaler, color matrix, deinterlacing, denoise and sharpening, rate control and bitrate, keyframe interval, H.264 profile, encoder presets, the GPU device, the low-resolution copy, queue depth, overload behaviour, and network pacing. Each setting shows the value in effect and stays on Automatic until you change it; options the hardware cannot do are greyed out.
• Overload behaviour you choose. If a machine cannot keep up, the input halves its frame rate by default until the encoder restarts. Advanced can make it return to full rate once the load drops, or never reduce it.
• Readable screen captures. A captured computer screen with small text arrives sharp on the receiving players, at the automatic bitrate and above.
• Input settings kept across updates. Updates after this one keep each device's name and each input's settings.
• API. GET /api/inputs lists devices and inputs with their live state; inputs and devices can be changed, renamed, and deleted through the API. See API in the web UI.

What is fixed

• Try: restart and power off finish. Restarting or powering off a player running Try from USB no longer stops at a hidden prompt at the end.

Supported capture

• Tested with the Blackmagic UltraStudio Recorder 3G on Thunderbolt 3, through HDMI, up to 1080p60, with embedded HDMI stereo audio. The SDI connector appears in the Inputs tab but was not tested. A device captures from one connector at a time.
• One 1080p60 input per player. Two inputs at once are not supported on the tested machine (Intel HD 520 graphics).
• On the tested machine, a captured input reaches another player's screen in about 70 ms, and the same player's own screen in about 60 ms (95th percentile, including the capture device).
• With Secure Boot on, the Blackmagic driver does not load and the Inputs tab reports it. Turn Secure Boot off in the firmware, or contact support to enroll the driver's signing key.
• Update the players that receive an input to 0.27.0 as well. Older players can show it, but may lose parts of the picture on sharp, detailed content at high bitrates.

Viso Gateway

Pair with Viso Gateway 0.3.1. 0.27.0 needs no Gateway change. If a Gateway is older than 0.3.1, update it at the same time: players in other rooms and departments get picture and sound only when both are updated.

What you should see after installing

1. Write viso-player-0.27.0.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Device → License — email contact@sysontech.com with the Device UUID, paste the token, Activate.
5. Inputs — connect the Blackmagic device. Its card appears with a tab per connector; plug in a source and the HDMI tab shows signal and format. Name the input and turn it on to publish it.
6. Displays — pick the input's source on this player or on any other player.

Already on 0.24.0, 0.25.0, 0.26.0, or 0.26.1

Open Device → Updates, check, and apply 0.27.0. You do not need to reinstall from USB unless you prefer a clean install. The download is about 315 MB, and an installed player needs a network connection on the first start after the update to build the Blackmagic driver.

Downloads

File	Purpose
viso-player-0.27.0.iso	Try or Install. Install erases the target disk.
viso-player-0.27.0.iso.sha256	Verify the image
viso-player-0.27.0.tar.gz	In-place update for machines already on 0.24.0, 0.25.0, 0.26.0, or 0.26.1.
viso-player-0.27.0.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.27.0.iso	0176256f1fb1f96a2af4351f20ed503281e8fc1895afc7ad6c2166ebdfe92092
viso-player-0.27.0.tar.gz	b47672bd6d73eed5984aa35189c80cbd993f35f15037549fd0918d8cb80f3a25

0.26.1

Viso Player 0.26.1

Current USB image: viso-player-0.26.1.iso. Machines already on 0.24.0, 0.25.0, or 0.26.0 can apply this build from Device → Updates when the OTA package is published. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is fixed

• Sources from other rooms and departments. A player on another part of the network could list a Gateway source but show no picture. With Gateway 0.3.1, picture and sound now arrive, including through firewalls between networks.
• Older Gateways keep working. With Gateway 0.3.0 the player plays as 0.26.0 did.

Update Viso Gateway too

Pair this Player with Viso Gateway 0.3.1. The fix needs both the Player and the Gateway updated. Replace Gateway, Gateway NDI, and Gateway Screen on the Mac at the same time.

What you should see after installing

1. Write viso-player-0.26.1.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Device → License — email contact@sysontech.com with the Device UUID, paste the token, Activate.
5. Displays — pick a Viso source for each screen. A source from Gateway 0.3.1 in another department now shows picture and, for NDI and Screen, sound.

Already on 0.24.0, 0.25.0, or 0.26.0

Open Device → Updates, check, and apply 0.26.1. You do not need to reinstall from USB unless you prefer a clean install. Update the Gateway Macs to 0.3.1 at the same time.

Downloads

File	Purpose
viso-player-0.26.1.iso	Try or Install. Install erases the target disk.
viso-player-0.26.1.iso.sha256	Verify the image
viso-player-0.26.1.tar.gz	In-place update for machines already on 0.24.0, 0.25.0, or 0.26.0.
viso-player-0.26.1.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.26.1.iso	1797e870c2a015c8b3725d4e8dda1dcf9354786ac784b38d2e745bd93bd8499f
viso-player-0.26.1.tar.gz	2510cb1a40141674e2671c74395d9cfc216c10bf281ee66647ec85fcd875f932

0.26.0

Viso Player 0.26.0

Current USB image: viso-player-0.26.0.iso. Machines already on 0.24.0 or 0.25.0 can apply this build from Device → Updates when the OTA package is published. Versions before 0.24.0 still need a USB install (see v0.24.0).

What is new

• Stable source binding by source_id. Display routes stick to the Viso source identity, not a frozen viso://host:port/… URL. After a Gateway cold-start on a new control/RTP block, the player rediscovers via VIS0 and rejoins without remapping Displays.
• Same-name publishers. If two Gateways announce the same source_id, the player keeps the host it is already using while that announce is live, then fails over when that announce expires.
• Lip-sync with Gateway 0.3.0. RTCP Sender Reports on video and audio map RTP time onto a local clock, so Mac and Player clocks can disagree without audio waiting seconds to start.
• Picture stays live. Video shows the latest frame as it arrives (holding to an absolute clock was freezing or lagging the image).
• Audio stays smooth. PCM plays into a primed buffer; the ring soft-trims when full instead of cutting out or stuttering when encode is slower than realtime.
• Built for Gateway 0.3.0. High Quality restart on the Mac can keep the same URL; this Player covers the cases that still move ports and consumes the new A/V timing.

Update Viso Gateway too

This Player needs Viso Gateway 0.3.0 (or later). Replace the Gateway apps on the Mac before you rely on this player in a room.

Download Gateway, Gateway NDI, and Gateway Screen from viso-gateway-releases.

What you should see after installing

1. Write viso-player-0.26.0.iso (Balena Etcher, or Rufus in DD Image mode). Boot from USB.
2. A 15-second menu appears. If you do nothing, Try starts. To keep the player, choose Install, let it finish, and remove the USB when asked.
3. Displays start black — press SPACE for the address. Open https://<IP>, accept the certificate warning, and set the operator password.
4. Device → License — email contact@sysontech.com with the Device UUID, paste the token, Activate.
5. Displays — pick a Viso source for each screen. If the Gateway restarts and the control port changes, playback should recover without editing the route URL. On Gateway Screen / NDI with 0.3.0, picture and sound should stay together without stutter.

Already on 0.24.0 or 0.25.0

Open Device → Updates, check, and apply 0.26.0. You do not need to reinstall from USB unless you prefer a clean install. Update the Gateway Macs to 0.3.0 at the same time.

Downloads

File	Purpose
viso-player-0.26.0.iso	Try or Install. Install erases the target disk.
viso-player-0.26.0.iso.sha256	Verify the image
viso-player-0.26.0.tar.gz	In-place update for machines already on 0.24.0 or 0.25.0.
viso-player-0.26.0.tar.gz.sha256	Verify the update package
latest.json / latest.json.sig	Signed update manifest for Device → Updates.

File	SHA-256
viso-player-0.26.0.iso	20c9830523f8d1ec1e37659586e589f92386c5bbe3a98b0e79d0c76a870cb082
viso-player-0.26.0.tar.gz	968214cef6fb3aa441e25976c01777a6950a54c790650a577e808bd03e1621b8