Skip to content

GoodBit 1.5.0

Choose a tag to compare

@github-actions github-actions released this 15 Sep 18:57
· 264 commits to main since this release

GoodBit names your clips itself now. No Python, no third party script, nothing running inside OBS.

Until now, getting a folder per game meant OBS running somebody else's script, which meant GoodBit downloading a private copy of Python to run it. That was the price of one fact: OBS names a recording after the clock and cannot be taught otherwise, and in GoodBit the folder name is the game name.

GoodBit does the naming itself now. OBS records into a folder GoodBit owns, GoodBit asks Windows which program was in front while that clip was recording, and files it under that game.

What changes for you

  • Nothing to install. The setup no longer downloads a script or an interpreter, and no longer asks OBS to run either. Two steps and about 25 MB of Python are gone from the first run.
  • Better names. The old script opened the game's process in a way protected games refuse, so exactly the games most likely to be protected ended up with no name at all. GoodBit asks Windows a question it will answer for anything, then matches it against your Steam and Epic libraries. That is the difference between a folder called Headliners-Win64-Shipping and one called what the game is called.
  • The clip goes to the game you were playing, not to whatever happened to be in front when the file landed. A clip arrives a few seconds after the moment it records, so the decision is a vote over the clip's own thirty seconds. Alt-tab to Discord and press the key, and it is still filed under the game.
  • A browser or a launcher is named too, because recording something that is not a game is a thing people do on purpose. Nothing lands loose at the top level.
  • Running setup again keeps what you chose. It used to reset the audio devices to the default every time, so adjusting one setting quietly offered to replace the five you had picked.
  • Change the setup goes straight to the questions. The quick route answers everything with a default, which is right for a machine with no setup and wrong for one you are adjusting.

If you already have Smart Replays installed, running the setup again removes it. The script and its Python are left on disk; only the entry that loads it goes.

Move your clips somewhere else

Settings, App, Clips folder has two buttons now. Change points GoodBit at another folder and leaves the files alone, which is what it always did. Move clips takes the library with it, which is new.

It carries every tag, star, note, display name and collection, because a clip's row is the only copy of those and its path is its identity. It keeps each recording's own date, so nothing refiles itself under today. It brings the thumbnails. It moves Videos into Videos/Clips correctly, which is the case it was built for. And it checks there is room before it copies anything across a drive.

It will not run while OBS is open, and it offers to close OBS for you, because a replay saved halfway through a move lands in the folder you just left.

Fixed

  • "OBS is set up and recording" on a machine with no OBS. Uninstalling OBS leaves its settings folder behind, and GoodBit was reading that as proof OBS was installed. The Start button could only fail.
  • The setup no longer keeps saying OBS is open after you have closed it. It re-checks while it is on screen, and offers to close OBS itself.
  • The library banner said the same thing three times over. It is one sentence now.

Installing

Windows 10 or 11, 64-bit. Any 1.0.0, 1.2.x, 1.3.x or 1.4.x install updates itself. A 1.1.0 install cannot start and has to be replaced with this installer directly.

Windows will interrupt you once. These builds are not signed with a paid certificate, so SmartScreen shows "Windows protected your PC" the first time, More info, then Run anyway.