• 0 Posts
  • 93 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2024

help-circle

  • In thousands of songs, I’ve never noticed Picard doing anything to the length of the files. I tend to manually review every album by running it through Picard and letting it handle the renaming and tagging. That structure used to be Artist/Year Album/Song. I’ve been less strict about naming the songs themselves. It’s always at least track - Title, but sometimes Artist - Album - Disc # - is prepended. Eventually I ran into a situation where I had multiple versions of a release/album with different enough content to warrant keeping both, so now I throw a release ID number (if is exists) after the album name, and inside brackets, for the directory name.

    It’s a very flat structure by design, so I’m never quibbling about where I sourced something or what particular genre it is when I’m looking for it. That dramatically reduces the likelihood of duplicates too. Real metadata is better left to tags, since that’s mostly what any player will see anyway.

    If I’m having trouble getting Picard to recognize something it always because: musicbrainz.org is missing the release, doesn’t have acoustic ID, or Picard preferred the album track when I’m trying to rename and tag a single or EP. Adding the release info and acoustic ID to musicbrainz is easy and I can usually use the info before the release is even reviewed, but often in trying to add the release I’ll find the correct one and now I can help fill out the data about it.

    I treat musicbrainz.org as MY metadata database. If a release is missing or has problems, I do the work to make it better. It’s good digital citizenship and learning about their rules for releases helps me manage my server better.



  • I spent a little more to get the upgraded newest model of the android phone I’m currently typing this on, released in January 2021 and received by me in March. I had to replace my previous phone because the battery started to fail and it was failing behind in Android versions, meaning some newer apps could no longer be installed and some older apps could no longer be updated. Current phone still going strong, no signs of being any slower than it was originally. Mostly have used wireless charging and battery protection schemes in the OS, so USB port still works well and charges just fine either way. I feel like phones hit a performance plateau a few years ago and I see no reason for an “upgrade”. If my current phone needs to be replaced, I fully expect to be forced to pay more for less given the costs of memory these days. Previously I’d been basically forced to upgrade every 2 years because I always bought the contract special “free” phone and updates stopped or the battery pillowed.





  • “No participant study has been run yet, so we’re not claiming superiority ahead of the evidence,” he said.

    Why not? Seems a simple thing to do before the development gets very far, certainly before the “press release” stage. Probably because they have actually done participant studies and found that trippy map visualizations aren’t particularly good for info at a glance or safe for use while driving. The whole design should have been driven by participant studies from the beginning.

    The whole article wreaks of a “solution” in search of investors and a problem. No one needs a near street level view for navigation, they’ve got that already. Adding a layer of Escher-like distortion seems unlikely to make getting information at a glance from a map any better.


  • The idea is to have the server safely shutdown BEFORE it loses power, so that BIOS setting wouldn’t mean anything. The server does not loose power while it it running, so it will never “restore last state after AC loss”. The idea is that you can run a low power device (the raspberry pi) for which you don’t care if power is cut abruptly and that can talk to both the UPS and the wake-on-lan of the server directly over ethernet. It being local means those WOL are much more likely to work than trying to send them from outside your network when you’re remote. It’s a lot simpler to set this up once than it is to recover a server with a corrupted file system due to power loss or lose access to your server for weeks because a thunderstorm knocked out power for 30min at the beginning of a long trip. That pi can also take care of other always on services like a pi-hole, home assistant, etc.





  • Wolf314159@startrek.websitetoSelfhosted@lemmy.world•Beets tips & config
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    4 months ago

    So much safer to go one album at a time using Picard. Picard makes it easy to go down the list of a disorganized directory, identify most things automatically, allow in depth review and modifications to what Picard came up with, and standardize file naming. I’ve tried to let programs like Lidarr and beets automate it, but they always ends up causing more and more complex problems to discover and solve after awhile. Music releases are complex and sources are diverse, using distinct standards of form and format. It’s not a problem that can realistically be solved for my entire music library without the guiding hand of a librarian. I could listen to my library for over six months without repeating, even 1 album out of a 100 mis-tagged or misidentifyied could take me years to discover.

    I do like to automate the less critical and more machine oriented library tasks like adding genres tags, replaygain, and lyrics as you do. Just not things like the metadata tags, file naming, or album art (embedded or otherwise).







  • Not OP, but I have similar feelings and they have nothing to do with the client or plugins. If I can’t easily and securely share my Jellyfin with the Internet beyond my LAN without resorting to a VPN, then Jellyfish is not going to come close to replacing Plex. Sharing my library securely with tech illiterate family and any browser I have access to, without modification, was the one and only reason I moved away from XBMC/Kodi and installed Plex in the first place. Jellyfin is fine inside my LAN and for my personal use, totally fails at hosting.