Seerr requests from Discover, Quick Connect for Jellyfin, Spanish and
German, and the What's new screen: version 0.5.0 (contentVersion
00.005.000, same param.json profile), README with the Discover capture
and the services' new uses, a short console checklist, and where the
app's own files are seen from FTP during console tests.
REGIE5_DRY_REQUESTS=1 logs a request instead of sending it, and
REGIE5_SHOW_VERSION shows the version a test build tries out; the
release script turns both off.
From Settings (Options on Jellyfin's line) and the welcome screens'
check: a code shown on the TV, approved in Jellyfin on a phone, and the
account's session written into config.json, never shown by the phone page
and dropped when the address changes. Régie5 introduces itself with a
device id made once (settings.json). An account that is not an
administrator is accepted: its line is orange and the screens that need
one say so; a session removed in Jellyfin says so too. An API key still
comes first; Emby is unchanged.
A third view under Requests: a search field (the PS5's system keyboard,
SDL text input on Linux), rows of trending, popular and upcoming films
and series, a title's page with where it stands, season by season, and
a request: the seasons, 4K when Seerr has a 4K server, the server, its
quality profile and folder, asked again with Cancel first. Requests go as
the API key's account. Made-up fixtures for --mock and --demo, whose
search keeps what matches; tests for the paths, the parsers and the
request's body. Square (X on a keyboard) clears the search.
docs/CONTRIBUTING.md: reporting a bug, suggesting an idea, translating,
changing the code, and the rules every change follows. A short GIF of the
demo mode at the top of the README's features (scripts/capture-gif.sh).
A glass panel with the version's few new things, at the first start of a
new series (0.5; not for a fix such as 0.5.1), never on a first install,
with the welcome screens or in --mock (REGIE5_WHATSNEW=1 for captures).
The version seen is kept in settings.json ("seenVersion"); on the PS5 a
first install is told by the launch counter. Settings gets a sixth
button, and the buttons get smaller together when they do not fit.
A line that names Jellyfin is left out for Emby users.
The "emby" state left the Library after a series' page (no Options
menu with Emby) and drifted to the end; "noconfig" was covered by the
welcome screens, it now runs with "Later" already chosen. A "welcome"
state captures the six screens, and the README captures gain one of
the media server's choice.
Its activity log's kinds and user numbers, the last played dates it gives
only on request, series dated from their latest watched episode (the
cleanup would have taken a series watched yesterday for long unwatched),
hardware acceleration from the transcode's pipeline. fixtures/emby/ from
the test server, REGIE5_MOCK_EMBY=1, tests.
Emby in a container on 127.0.0.1:18096, its data under build/emby-test/,
a library of short clips named after the Blender films with .nfo files
(nothing from the internet), and a setup script: first-run wizard, an API
key, two libraries, a second user, a Régie5 config.json with Emby alone.
0.2.0's param.json with attribute3's 120 Hz bits (0x80040) added: on the
console (app-14) Régie5 starts in the Games area, opens the phone page and
gets 120 Hz. Settings offers 120 Hz again, marked experimental; Auto stays
at 60 Hz. release-ps5.sh takes REGIE5_RELEASE_NAME for a second candidate
of one version.
build-ps5.sh writes REGIE5_HZ120 from attribute3's bit 0x40. Without it the
app asks for 60 Hz, Settings no longer offers 120 Hz (Auto and 60 Hz), and a
120 Hz setting kept from 0.3.0 is shown as not available in this version.
REGIE5_NO_120=1 shows it on Linux.
0.3.0's param.json (Jelly5's Media profile) starts and gets 120 Hz, but the
console refuses to let the app listen: Settings > From your phone fails with
"listen: permission denied".
- ps5/app/param-profiles.json: what each profile did on the console (area,
start, listening, 120 Hz); scripts/check-param.py warns in build-ps5.sh and
refuses in release-ps5.sh a profile never seen to start and to listen.
- The start-up probe logs bind and listen apart (port 8085 and a port the
system picks) and the installed param.json's profile; the phone page's
error says which call failed.
- 120 Hz endurance test: a file named stress in the title's folder forces
120 Hz and runs the tour in a loop, the heap logged every 10 s, GET
requests only.
- RELEASING.md: the phone page, the tile's area and the refresh rate are
checked at every release.
param.json takes Jelly5's profile, the only one that starts in the Media
area on firmware 13.60: category 65536, badge 1, the launchActivity
intent, attribute 0, attribute3 0x80040, no amm or kernel block. With it
the console also accepted 120 Hz. build-ps5.sh widens ps5-homebrew-ui's
check to this profile in its temporary copy and takes REGIE5_PARAM for
test builds. INSTALL.txt says where the tile appears.
Settings › "Display refresh: Auto / 60 Hz / 120 Hz" (Auto asks for 120 Hz;
a display that refuses it keeps 60 Hz; applied at the next start). The log
says the rate asked and the rate accepted, and the driver's answer reaches
the main log. The first frame after a pause steps one period of the
display, and a slow frame is one and a half periods. Test builds: a bench
file runs the tour and times each frame in parts (drawing, the scene
finished on the GPU, the copy to the screen, the swap); output-1440p to
compare render sizes.
Libraries with their counts (films, series and episodes, or items) and
their size, added up from Radarr and Sonarr since Jellyfin gives none.
Users with their last activity, most recent first; no address or device.
Made-up fixtures; three users given distinct names.
The Requests tab gets two views in pills (Requests · Issues). Issues are
listed open / resolved / all with the title's poster, the kind of problem,
the episode, who reported it and the last comment; ✕ shows the thread.
Options › Resolve… and Comment… (a few ready-made sentences), each asked
again with Cancel first. Made-up fixtures, demo data regenerated.
Vivian