github RamazanKara/nightjar v6.1.0
Nightjar 6.1.0

one hour ago

Nightjar 6.1.0 puts the bitrate back in your hands and clears the settings: you can tell the PC to keep your bitrate, settings that can do nothing on your device stay out of the way, and Android TVs get an option for sets that freeze during a stream. Under that is a read of the whole code before this release, with the faults it found fixed.

Highlights

  • Keep my bitrate. Lower bitrate has a new choice, Never: keep my bitrate, and the stream menu a Keep my bitrate switch: on a PC that accepts bitrate changes from the device, the PC stops lowering the bitrate for that stream.
  • You are told when the PC lowered the bitrate, once per stream.
  • Settings shows fewer rows. A row that can do nothing on this device is left out until it can act; search still finds every setting and says why.
  • TV display compatibility (Android TV, off by default): an option for TVs that freeze, flash or restart during a stream.
  • The app keeps answering while the video decoder restarts: turning or folding the device, resizing the window or an automatic quality change no longer freezes it.

Bitrate

  • Lower bitrate has a new choice, Never: keep my bitrate: on a PC that accepts bitrate changes from the device, the PC stops lowering the bitrate for that stream. The default is now named The PC decides, and When frames are lost is named Lower it sooner.
  • Nightjar now says, once per stream, when the PC lowered the bitrate for the network. On a PC that accepts bitrate changes, the stream menu's new Keep my bitrate switch stops that at once and keeps the choice for later streams.
  • Keep my bitrate and Lower it sooner now start from the bitrate the PC names for the stream, so on a PC running Rubylight 6.0.1 or older they no longer raise the stream's bitrate above what it ran at.

Settings

  • Settings shows fewer rows: one that can do nothing here, such as the touchpad settings with no touchpad connected, is left out until it can act; one you changed stays and says why.
  • Debug is listed once App's new Show debug settings switch is on, or while one of its settings is changed.
  • Nothing was removed: search finds every setting and says why a row left out does nothing now.

Android and Android TV

  • TV display compatibility (Android TV, off by default): an option for TVs that freeze, flash or restart during a stream. It keeps one tiny dot on screen changing so the TV keeps drawing the app.
  • On MediaTek devices the video decoder gets fewer special low-latency settings and a milder performance boost.
  • Turning or folding the device, resizing the window or an automatic quality change no longer freezes the app while the video decoder restarts.
  • After the stream changes size, the picture no longer stays frozen for a moment when nothing on screen moves.
  • With Controllers set to Off, the PC no longer gets controllers that never send anything.
  • With Controllers set to Off, the built-in pad and a USB pad send nothing to the PC, while holding Back for the stream menu and the quit combination keep working.
  • With Controllers set to Off, a pad's mouse mode no longer says it is on when it cannot move the mouse, and the stream menu offers the controller mouse switch only to turn a mouse off.
  • With Controllers set to Off, the on-screen gamepad works.
  • Typing during a stream no longer closes the stream when the on-screen keyboard asks for no text before the cursor.
  • Leaving the shared-folders page just as an upload finishes no longer closes the app.
  • Microphone only keeps the phone awake on devices that refuse the Wi-Fi lock, so the audio no longer stalls with the screen off.
  • The controller test screen stops reading the phone's motion sensors once the controller is unplugged, and keeps showing a USB controller's motion after you leave it and come back.
  • Choosing a preset in the on-screen controls editor keeps the Steam Controller controls where you put them.
  • The game list's background no longer shows another game's picture after you move back to the game it already showed.

Desktop

  • A full-color (4:4:4) stream whose hardware decoder gives way mid-stream now ends with the message that it needs a hardware decoder, instead of showing a garbled picture.
  • A game you starred on a PC you have since unpaired no longer stays on Home as a card that cannot start.
  • Opening Settings from a game page, with Start or the Settings link, no longer closes the game's Neural Rendering panel: Back shows it as you left it.
  • With two PCs' pages open one after the other, opening Settings from the second no longer cancels its connection test, its shared folders, a co-op join on its way, or its file transfers page.
  • With a host that takes scrolling only in whole clicks, a trackpad or a free-spinning wheel no longer scrolls extra clicks after a moment when the connection could not take the scroll.
  • A graphics device lost while picture enhancement is being checked no longer risks a crash.

All devices

  • A USB device shared with the PC keeps taking the PC's requests while the PC is slow to take its answers, instead of stopping in both directions.

Tested. Before the tag, this release's code and 6.0.1 were streamed in turns, three one-minute runs each with default settings on both sides, 6.0.1 from a PC on Rubylight 6.0.1 and this release from a build of Rubylight 6.1.0's code without its last fix: desktop Nightjar on a Windows laptop over Wi-Fi at 2880x1800 and 120 fps (6,575 to 6,581 frames shown per run against 6,565 to 6,578 on 6.0.1, none late or dropped in either), Nightjar on Linux on a mini PC at 1280x800 and 60 fps (3,278 to 3,279 against 3,272 to 3,279, none late or dropped, decode time at the 95th percentile 11.9 to 12.1 ms against 11.8 to 11.9 ms), and a debug build of the Android app on a handheld over Wi-Fi at 1080p and 120 fps (6,420 to 6,429 frames and no lost packet against 6,382 to 6,407 with up to 18 lost packets and one or two frames that could not be repaired; decode time at the 95th percentile 2.5 to 3.0 ms against 2.5 to 2.7 ms). No run changed the bitrate. Keep my bitrate held the stream's bitrate against Rubylight 6.0.1 and against the new host build, on the laptop and the handheld, and with Controllers off the PC got no controller from the handheld while touch still arrived.

A debug build of the tagged source ran on the handheld after the tag. A 60-second stream held 60 fps with no dropped frames and one gap over 25 ms. The video decoder was restarted 16 times during streams (split screen, with a custom stream size and upscaling on): the picture was back within about 0.3 s, once within a second, the app kept answering, and a frame rate chosen in the stream menu just before a restart was applied once. Switching the screen off during a restart ended the stream; Reconnect pressed after that, in split screen, started no stream, which this release does not fix. The MediaTek decoder settings and TV display compatibility were not run on a TV; with the option forced on, the handheld's video stayed on its overlay plane. The Windows build starts and shows 6.1.0, and its zip and installer scanned clean with Microsoft Defender. Every platform builds and Nightjar's tests pass in CI on the tagged commit.

Don't miss a new nightjar release

NewReleases is sending notifications on new releases.