This marks the first release after the move to Drupal and Discourse. Some bug fixes, but mainly introduces some changes to improve the overall Snakeoil experience.
My initial intention is to release this under the experimental branch. However that is too difficult right now as the experimental branch is a protected branch only activated users have access to. As such a lot of things in this release is technically not fully tested, like the attachment of your Pro subscription. Please report any bugs you see and they will be addressed in 1.4.5 or later.
THE SOFTWARE IS PROVIDED âAS ISâ, WITHOUT WARRANTY OF ANY KIND as stated in the Software Disclaimer.
Please refer to âHow To Install/Updateâ section of this post for installation/update instructions.
Please find list of known issues in the next post.
Whatâs New
Fix a bug when switching Snakeoil repository from Development â stable (#241)
Fix multiple issues with CIFS mounting in Snakeoil WebApp (#239)
Provide default Lyrion configuration upon Snakeoil Installation with stock options (#238)
Somehow the automation workflow for making a release is broken and I canât finish up the workflow. So the rest of the automation stuff can only be finished when I make a new release. Unsure when that will be .
Some of the features are not properly tested, so hopefully theyâll work well.
@PhantomGTR Please check the dashboard now and see if youâre getting proper pi metrics (power, etc)
And also let me know if the Ubuntu Pro subscription is working or not working. Note you need to manually reboot once youâre on the Pro subscription. Youâll get the RT kernel by default. Now I do not know whatâll happen when you detach from the subscription though - will the RT kernel still work?
BTW, would someone help to confirm the upmpdcli can be installed and âworkâ properly thru WebUI? Iâm sorry that I found that in previous version, so Iâve followed upmpdcli official website and installed it manually. Iâm not sure my gear is still suitable to test it.
Relying on external sources is always going to be problematic. Think I might just mirror this within the Snakeoil repository too. This should in theory reduce breakagesâŚ
Well, looks like I will fix this in 1.4.5 then. My bad. This 1.4.4 is really a transitional switch to move between stable (main) and experimental. Anyway, will look into this soonish.
On new Pi5 install, all I get is this:
Create an Ubuntu Pro account and generate a token to use this feature.
No place to put token in.
On both my NUCs, updated from 1.4.3, need to do a reboot before the 1.4.4 features turn up. I already have real time kernels running, so not sure what I am supposed to test?
I think it validates, perhaps at boot time ??? ** Tried to search but not clear what happens **
Need to reboot before seeing Ubuntu Pro, startup script sub tab
It adds all the standard players; should be respecting what user already has installed
When adding or removing players, get message âRest Server is not respondingâ before it comes good. Both NUCs have this problem all the time, but not on Pi5.
When installing new for Pi5:
Took at least 5 minutes before players downloaded; we have discussed this before, but how long is too long??? I knew that this is due to server but a new user can get frustrated ?
I set the fields for amd/intel systems to debug and forgot to remoe that. Not even sure how to unit test things like this. Will fix this in the next update.
Maybe try & remove the subscription and reboot? What happened? Are you still on the RT kernel? TBH I am too to try this, putting a screen and keyboard to my setup is not easyâŚ
This is most likely due to the browser caching the old WebApp. Youâll need to CTRL+F5 for this to go away. I am actually thinking of writing a new Android frontend for Snakeoil actually, and since itâs no longer web based it will not have this cache issue.
Can y
+1, Agreed. Will need to do some extra work to make this easier. i.e. going to split up all the players into their individual debian packages. And that will solve this problem weâre seeing.
Another option is the hide the players you donât want, however Iâll rather split up into individual packages as it will make everything smaller and more modular.
Thereâs some code in the new API thatâs âblockingâ⌠Remind me again later if I havnât get back to this.
Slow downloads on Pi could be because of the slower microsd media. Moving to a SSD or NVMe drive should speed thinks up. The server Iâm using is still relatively slow though, I believe thatâs 250 or 350 Mb/s. But it shouldnât take that long. Nothing I can do to speed up the downloads. If users are frustrated, Iâll just point them to the buymeacoffee link. Snakeoil have moved from VPS (very slow) to relative fast (bare metal server) because of donations. More donations and I will move to bare metal servers with gigabit networking. Right now should be fine, 250 Mb is âplentyâ.
Thanks for testing. Still so many Snakeoil is infested.
The 250 or 350 is in total - so if multiple people are downloading at the same time, then it will be slow for everybody. Hence breaking up the players into multiple packages is a good idea (even though the players donât get updated that often really).
Unfortunately the snakeoil package itself is also around the same size, and yeah it will be slow if multiple people are updating.
Hereâs the prices to rent cloud infrastructure: Dedicated server prices - Explore our full server range | OVHcloud Australia. The server needs to have enough space (hosting the files), enough RAM (for processing duties - development, blogs, forums and other daily maintenance - e.g. daily backups), and enough bandwidth to push data back and forth (downloading updates, etc.). The data center also has to be more or less reliable (no power outages, no break ins, no fires, etc).
These prices are the normal rates (there are usually black Friday discounts). Even so these normal prices have increased pretty significantly! I have 2 hosts and itâs only costing me $109 a month. Ad money is only around $5 to $10 a month, and I think itâll be a lot less now as I have disabled ads in the forums temporarily.
To rent good enough at other data centers (Especially Australia ones), itâll be anywhere from $500 to $2000 a month (likely to be higher).
Location also plays a part. My servers are hosted somewhere in Canada. So it may be slower coming to Australia, but it will not be elsewhere.
Hopefully, updating to 1.4.4 shouldnât brake anything vital. RT kernel should remain active but I will test this on my RPi5 first which is test board. Can I move this SD card with updated SOos to RPi4 which I actually using for music? And currently I donât have option to select clock source. Will this option appear after update?
I have RT kernels in both my NUCs and both running well after update.
Maybe, if both the Pi4 and Pi5 are standard??? But, it is generally safe to do SO updates. If, however, you have a major problem, @agent_kith will fix things quickly..
RT and clocksource are two different things. Will fix the pro option not showing up in pi over the next few days.once that it is done you should be able to switch to a RT kernel. But canât change clocksource on Pi via software, as thereâs only one.
To change clocksource, you kind of have to mod the pi physically.
Please refer to âHow To Install/Updateâ section of this post for installation/update instructions.
Please find list of known issues in the next post.
Unsure when that will be 
.
I set the fields for amd/intel systems to debug and forgot to remoe that. Not even sure how to unit test things like this. Will fix this in the next update.
to try this, putting a screen and keyboard to my setup is not easyâŚ
Snakeoil is infested. 