Skip to content

4.0.17-beta.1

Pre-release
Pre-release

Choose a tag to compare

@realtechspecs realtechspecs released this 26 Oct 07:56

Ray headless 4.0.17 - release notes

Ray headless is Ray's subtitle server for a NAS, home server or any always-on box. This release connects it to your Plex, Jellyfin and Emby libraries, lets Ray support help when a job fails on the server, and makes Ray Cloud jobs wait through used-up allowances and dropped connections instead of failing. NVIDIA graphics cards now separate voices for Sunlight too.

Images: techspecs/ray:4.0.17-beta.1-cpu, techspecs/ray:4.0.17-beta.1-cuda, techspecs/ray:4.0.17-beta.1-vulkan (and the moving cpu, cuda, vulkan tags). Guides: NAS install guide · container guide.

Upgrading from 4.0.16-beta.1? Read the upgrade notes first.

New

  • Plex, Jellyfin and Emby (Homewide). Ray watches your media server libraries and adds subtitles to every new video, so they show up in the library like any other subtitle. Connect a server in the new Servers tab (owners): Jellyfin and Emby on your network are listed by themselves, Plex connects with Sign in with Plex, and any server connects by its address. Then choose libraries and languages; Subtitle what's already here does the videos a library already has. It works for Ray accounts that include Homewide, is on by default, and RAY_ENABLE_HOMEWIDE=0 turns it off. Servers can also be set where the container starts (RAY_HOMEWIDE_SERVERS). From a terminal: ray-cli api homewide.
  • Remote help on the server. When a job fails in Ray Local, owners can ask for remote help in Help (or with Get remote help on the failed job), and Ray support can look into it. Only someone at the server's own terminal lets them in, with ray-cli support approve or ray-cli support request; the dashboard and an API key never can. Ray support can see the server's details and logs and run test jobs, never change settings. It uses no seat. RAY_SUPPORT_SESSIONS=0 turns it off.
  • NVIDIA graphics: voices separated for Sunlight. With techspecs/ray:cuda, Sunlight separates voices from the music and background sound on the NVIDIA card before it makes subtitles. The first such job downloads what it needs (about 2 GB).
  • Help for everyone. Everyone signed in finds Graphics cards in Help: how well the server's graphics card runs Ray, on the same scale as the Ray app. Owners also get Contact us, which sends a message to Ray support from the server, and the connection test now shows whether each of Ray's services is reachable from the server, with the address to allow in a firewall or ad blocker.
  • Copy diagnostics on every failed job, and ray-cli api diagnostics JOB_ID: the details Ray support asks for, never keys, folders or links.
  • Watch folders retry failed files. Choose Retry failed files after 1, 3, 6, 12 or 24 hours, at most 3 times, for failures that can pass, like a lost connection or a share that didn't answer. The folder's row shows the next try.
  • Several languages in one go. generate FILE --language bs,sr-Latn (and ray-cli api submit) makes one subtitle per language, each with its own name, and reads a subtitle with no language in its name the same way for all of them.
  • ray-cli gains api retry JOB_ID, api diagnostics JOB_ID, api homewide (with sync) and support (status, request, approve, end).

Improved

  • Ray Cloud jobs wait instead of failing.
    • When the daily limit or the allowance is used up, Ray Cloud jobs from the dashboard, the API and watch folders wait and go again by themselves after the reset or once you add credit. A used-up free trial waits for credit. Nothing is uploaded while a job waits, and Check now (or ray-cli api retry JOB_ID) asks again.
    • When the connection drops or Ray Cloud has a short problem during a job, the job waits for it and carries on. After a restart Ray follows the same Ray Cloud job, with no new upload.
    • Waiting work stays with the Ray account it was made for: after Switch account it never runs, or gets charged, on the other account.
  • The Jobs list is kept across restarts (up to 5000 jobs in /config). A job that was running when the server stopped comes back as failed, Stopped when this server stopped, and never runs again by itself.
  • Requests wait for an answer. A sign-in request to your Ray app and a request to connect one of your computers no longer run out after a few minutes: they wait until someone answers, and Stop asking takes them back.
  • Your devices on Docker's bridge network: a computer added by its address can now be chosen to run jobs.
  • A plan without Ray Cloud refuses a Ray Cloud job before anything is uploaded, and Run on says why Ray Cloud can't be chosen.
  • Ray Local says when the processor is the reason. A processor without AVX2 is named as the cause, with a hint for virtual machines (set the processor type to host).
  • Translations: a few lines Ray can't translate are left out, and the job says how many, instead of failing the whole subtitle. More than 10% still fails.
  • Large folders: a watch folder takes in at most 50,000 new videos per look and carries on at the next one, and says so.
  • When Ray Local can make out only part of what is said, the job finishes with what it heard and says so, instead of failing.
  • Memory in Docker: Ray Local sizes its work to the container's own memory limit, not the whole host's.
  • Language versions: Serbian in Latin letters is read as Serbian and keeps its own file name (Movie.sr-Latn.srt), and a Brazilian Portuguese subtitle is converted for a Portuguese (Portugal) pick instead of being shown as one.
  • Ray Local reliability: no timer stops work that is still going, files without sound are named up front, and files a job or a busy graphics card still uses are never removed.
  • Smaller Windows download: the server zip leaves out what only a window uses (about 55 MB less).

Fixed

  • With the cuda image, videos with music or hard-to-hear dialogue get their subtitles again: in 4.0.16 some of those jobs failed.
  • ReTime on the cuda image under Docker Desktop on Windows works again.
  • Use your devices: unticking This device no longer fails every job when no other computer can take it.
  • ray-cli speed-test no longer shows which country the connection comes from.

Upgrade notes

Update with docker compose pull && docker compose up -d. /config, /models and /data carry over.

  • Plex, Jellyfin and Emby (Homewide) and remote help are on after the update. Neither does anything until an owner connects a media server or asks for remote help. To keep them off, set RAY_ENABLE_HOMEWIDE=0 and RAY_SUPPORT_SESSIONS=0.
  • Ray Cloud may ask you to confirm it once on this server. A banner with Confirm now holds Ray Cloud jobs until then, and they go by themselves afterwards. Nobody is signed out.
  • Keep /config as a volume: the Jobs list and the Ray Cloud jobs that wait for the allowance are kept there across restarts.
  • For scripts: a Ray Cloud job on a plan without Ray Cloud is refused when it is added (403 cloud_not_entitled), a job that waits for the allowance stays queued instead of failing, and GET /v1/jobs also lists jobs from before the last restart ("from_before_restart": true).
  • Without Docker: Scoop now installs Microsoft's Visual C++ runtime from the extras bucket, so run scoop bucket add extras once. Chocolatey installs this beta with choco install ray-headless --pre. On a Mac, the server moves its settings once to a new place, by itself.

Known limits

  • Plex, Jellyfin and Emby: Ray finds Jellyfin and Emby by itself only with host or macvlan networking; on Docker's default bridge network, add them by address. Emby needs the media folder mounted in Ray's container. Connect each media server in one Ray only, or the work and the Ray Cloud use happen twice.
  • Sonarr and Radarr renames may drop the -latn from Serbian (Latin) and Romaji subtitle names.
  • The one-shot generate never waits for the Ray Cloud allowance: it fails with the reset time.
  • Remote help is for Ray Local problems only, and a server restart ends a request.
  • A computer with Ray before 4.0.17 still ends a sign-in request after 10 minutes and a connection request after 2 minutes: update Ray there.
  • ReTime on the cuda image can't run while other work holds the graphics card.
  • Ray Local needs a processor with AVX2.
  • Take work from your devices needs host or macvlan networking.
  • Sonarr and Radarr connections subtitle new episodes and movies; for the ones you already have, add the folder under Watch folders.