![]() |
Snakeoil Firmware - 1.1.0 Alpha 3 - Printable Version +- Snakeoil Forums (https://forums.snakeoil-os.net) +-- Forum: Snakeoil Testers (https://forums.snakeoil-os.net/Forum-Snakeoil-Testers) +--- Forum: Test Builds (https://forums.snakeoil-os.net/Forum-Test-Builds) +--- Thread: Snakeoil Firmware - 1.1.0 Alpha 3 (/Thread-Snakeoil-Firmware-1-1-0-Alpha-3) |
Snakeoil Firmware - 1.1.0 Alpha 3 - agent_kith - 15-Apr-2018 Almost at the finishing line now. Just the web remote and documentation left to do. Refer to the Blind Testing Road map for details. First seen in this alpha - cpuset, this feature allows you to run your music players in a CPU group. Seems to sound alright for me ![]() ![]() Annnnd, I'm still looking for the first SnakeoilOS patron. If you havn't donated before, and want to support this project, please sign up to Patreon and be a Snakeoil big fan ($1 a month)! Need somebody to do this so I can find a way to automate this. Alpha 3 Downloads
RE: Snakeoil Firmware - 1.1.0 Alpha 3 - agent_kith - 15-Apr-2018 If using cpuset, make sure there are numbers showing in the text below. e.g. Code: "Running in (user): XXXX, XXXX, XXXX" I have tested this for a week, and it always worked, until I released the software - it failed once ![]() If you find any problems with cpuset, just uncheck and check a cpu, and hit SAVE. Your music programs should be isolated in it's own group then. Note also the number should not be in this (user) list. RE: Snakeoil Firmware - 1.1.0 Alpha 3 - agent_kith - 17-Apr-2018 A second heads up. Sometimes your browser decides to reuse older versions of the WebApp even when there is a newer edition. If you see something like this, it means it's not loading the newer elements correctly. To fix, do a force browser refresh:
RE: Snakeoil Firmware - 1.1.0 Alpha 3 - agent_kith - 17-Apr-2018 Found another bug.. Due to the change in player output options, I changed the front end (web app) but forgot to update the backend. So while it looks good, the new options aren't used when loading the player. ![]() This will be fixed in the next release (hopefully soon). |