-
-
Notifications
You must be signed in to change notification settings - Fork 6
FAQ
See the page on Global Hotkeys
Note that using the function key in a hotkey is not supported due to macOS limitations.
In the menubar, click Splitter -> Settings/Preferences (or press ⌘->comma). In the window that opens, click "Hotkeys". You'll see a list of the hotkeys you can set, so just click "record hotkey" next to the one you want to set, and press whatever hotkey/key-combonation you like to set it.
If that doesn't solve the issue, see this page for more details
Splitter supports adding positive and negative offsets for a run. Just open the Run Info menu (that's the button with the eye on it), and enter your offset in the "Offset (Seconds)" field. For a negative offset, just include a minus symbol before the time (i.e. -3.00).
Check out Splitter's Overlay Mode - it's designed just for this purpose!
To use Splitter with OBS, it's recommended to use it as a Window Capture source. Add a new Window Capture, and set the window to that of the Splitter window that you'd like to capture.
If you don't want the buttons or title bar to appear when you're streaming, open the Layout Editor, click "Window", and turn "Hide Title Bar" on. If you save your run as a .split file after doing this, the settings will be kept whenever you open the run.
Splitter uses LiveSplitCore to handle the mechanics of keeping track of time. As a result, Splitter is as accurate as LiveSplit when it comes to timing your run.
Bring it up in the #feature-requests channel in the Discord Server
Bring it up in the #issues channel in the Discord Server, or file an issue on GitHub
Splitter does not include auto-splitting functionality at this time. If you want to, you can use Splitter's Shortcuts actions, together with the Shortcuts CLI to automate opening and splitting a run. Additional ideas for automation support is actively being considered - if you've got a use case, please let me know!
There's a few reasons for this:
- Due to MacOS' security limitations, Autosplitters would have to work by reading the raw video data output by the game, rather than hooking into the game itself - think VideoAutoSplit
- As a sandboxed app, it require Splitter to jump through some hoops to do such a thing, (even if Splitter wasn't sandboxed, many games are sandbox anyway).
- This would require porting VideoAutoSplit to macOS. Given that it relies heavily on certain Windows APIs (namely DirectShow), it's much easier said than done.
- The alternative would be to build a VAS parser from scratch, which again, is easier said than done.
- Ultimately, there are other things that I've deemed more important for Splitter to have (like increased layout customization, subsplit support, among other things) before adding Autosplitter support is at the top of my priorities. Though by all means, if you've put the time and effort into implementing it, open a PR and we'll talk.
When I first started working on Splitter, I considered distributing it myself so I could have some extra freedom. However, as I continued working on it, I realized that Splitter doesn't really do anything that isn't allowed in the Mac App Store anyway, and have no plans to make money directly from it, so there really wasn't a reason not to use the App Store. It makes it easier for people to find, and gets updated alongside other App Store apps you have installed, and generally makes life easier for me (as a developer) and you (as a user).