![]() The highlights of Google Play Music was the excellent queue management, ease of music discovery and a radio that actually gave me relevant tracks. They added radio and a Spotify-like subscription service that molded seamlessly around your uploaded content. Shortly after Google raised the limit to 50,000 tracks, and refreshed the UI into what I felt was the best ui of any music app at the time. The fact that Google counted track numbers and not the size of the library was evidence enough that Google was catering to the consumer with the launch of the service. Within minutes I was able to upload my entire 20,000 track library to Google Play Music and access it instantly on my Android device for free. While I was quick to spoof my location and hop on the Spotify beta early I still had a proclivity towards wanting to own my music and GPM catered to that desire. Google Play Music was nothing short of revolutionary when it was first released in 2011. But I'm guessing that will be a no-go in the long run.Everything you loved about GPM, improved, and self-hosted What I loved about GPM I much prefer jails having their own MAC address, which means I can give them a unique IP and with local DNS it's easy to administer the services. ![]() What's the best solution here? Bite the bullet and go SCALE? Or is there another solution? Maybe CORE will be moving to Linux soon-ish and make the point moot?ĮDIT: option c) would be best - Plex implements Sonic features to BSD variants of the server and we're good to go. I have SCALE on the horizon at some point anyway because I'm thinking of getting a compute box up and running in a separate case for now, but I wouldn't mind consolidating that with the NAS (with ~20 cores for example) and run the compute part in a VM -> that would require running a Type-1 hypervisor, so CORE is out of the question for now (I'd prefer to virtualize it within TrueNAS, given SCALE can do it, as backing up everything and provisioning the hardware would be much easier than running for example ESXi or Proxmox and virtualizing TrueNAS as well). Is that still true? Not being able to run portainer is also less than ideal, but I guess I could manage that in the long run.ī.b)run an Ubuntu VM and run standard Docker? But I guess that doesn't make THAT much sense as well if the base system could (can?) run it properly. If I want to run the sonic features on my Plex server and, ideally, not run two distinct servers (I would survive with the docker one being a bit slower, but still, if I can optimise things, why not), I'd need to either:Ī) improve the performance of the VM in TrueNAS COREī.a)I've heard some comments that kubernetes takes up a lot of resources to run docker containers even just sitting there as well, with no containers set up. So, looks like the bhyve hypervisor is somewhat slow. The jail server has always been perfectly fine, snappy, I've also setup a Hyper-V Ubuntu VM on my main machine and that was perfectly fine and snappy even with two threads (I've now given it 12 off my 8700K to perform the sonic analysis hopefully a bit faster). The issue is that it's painfully slow, PlexAMP taking seconds to respond on a remote computer and load the album contents, start playing, etc., with the CPU often being pegged at 100 % usage on the 4 threads I've given the VM (of the 4 threads available). Since I'm running core (started off with FreeNAS 4,5 years ago) on my NAS (running an E3-1225 v5 and 32 GB of RAM), the only way to try out the Sonic features was to run a VM and setup another Plex server in Docker besides my jail that's been up and running basically since the iocage move. Sadly Plex does not support Sonic analysis on BSD and thus on TrueNAS Core.
0 Comments
Leave a Reply. |