Important
Glint only works in 60 Hz mode. If a game switches the PS5 to 120 Hz, capture stops until you restart the console.
- Glint turns 120 Hz Output off while it runs and puts your setting back when you stop it.
- Load Glint from the home screen, before you start a game.
- A fix for 120 Hz mode is in the works.
Lower latency
- Sound much closer to the picture: about 55-80 ms behind instead of 95-130 ms.
- Sound recovers after a console freeze: it skips the backlog instead of playing up to a second behind for half a minute.
- The payload hands over frames and sound sooner: it notices each finished capture call within 0.1 ms instead of checking every 5 ms.
- Pictures go to the screen at the next refresh where the graphics driver supports it.
Smoother on Wi-Fi
The payload now streams at 35 Mbit/s (was 50). Over Wi-Fi, busy games at 50 Mbit/s or more could stall for a second or two; 35 stays at a steady 60 fps. With the PS5 on a cable you can go higher with the bitrate=N start argument (up to 100 Mbit/s) for a sharper picture in busy scenes.
New look
- Centred connect screens with a larger logo.
- New fonts: Space Grotesk for headings, Inter for text, JetBrains Mono for numbers.
- Settings and the gallery scroll at your monitor's full refresh rate.
- The Picture tab has its heading like the other tabs, and some Settings labels are clearer (for example Picture fit and Game audio).
Also
- Browser view on a Mac no longer freezes and falls behind (Safari and Chrome).
glint.loggets astats:line every 10 s while connected (network lateness, decode time, sound buffer, frame size, encoder quality), which helps when reporting stutter.
Install
- Download Glint.exe and Glint-1.3-ps5.elf below.
- Upload the
.elfto your PS5:
/data/pldmgr/payloads/local/glint/Glint-1.3-ps5.elf
(you can delete the oldGlint-1.2.1-ps5.elf) - From the home screen, load it from Payload Manager, then open
Glint.exe.
If it doesn't start, please open an issue with /data/glint/capture.log from the PS5.
Only tested on firmware 13.60 so far. Full details in the changelog.