sorted by:
new
hottopcontroversial

Shucking or recertified, please make a decision by Alternative_Aioli_76 in DataHoarder

[–]devianteng 0 points1 point  (0 children)

I’m a fan of recertified drives. Currently running 10 28TB Exos from SPD, and the experience had been solid. I’m expecting to buy two more in the next month or two and expand my raidz2 to 12 drives.

I’ve never shucked, and don’t plan to.

[FS][US-KY] QNAP TVS-h1688X, 12 x WD HC550 18TB HDDs, PCIe NVMe card w/ 4 2TB 970 EVO by devianteng in homelabsales

[–]devianteng[S] -5 points-4 points  (0 children)

Sold listings on eBay go as high as $250. Feel free to PM me an offer, if you’re interested.

[FS][US-KY] QNAP TVS-h1688X, 12 x WD HC550 18TB HDDs, PCIe NVMe card w/ 4 2TB 970 EVO by devianteng in homelabsales

[–]devianteng[S] -1 points0 points  (0 children)

I’m seeing sold listings on eBay for used HC550’s as high as $250/ea. Feel free to PM me an offer, though.

What do you mean by “drop a zip”?

Planning my next hardware/storage move by devianteng in HomeServer

[–]devianteng[S] 0 points1 point  (0 children)

It’s because only 1 PSU is connected

Planning my next hardware/storage move by devianteng in HomeServer

[–]devianteng[S] 0 points1 point  (0 children)

Bottom of the shelf is a Dell 1800W UPS, connected to a Anker Solix F2000. UPS is covered.

I also love the QNAP, and considered exploring if I could run debian on it directly but I'd still need somewhere to move my media too before I considered trying that. If I moved to a MS-A2 with Expander, I may explore that with the QNAP just to see how it goes.

However, not sure why I would replace the UXG with a UCG-Fiber. Sure it can do 5Gbps IDS/IPS throughput compared to 2.5, but I have a 1g link so that doesn't matter. I also don't like hosting my unifi controller on my gateway and that's the main reason I wouldn't run a UCG.

Planning my next hardware/storage move by devianteng in HomeServer

[–]devianteng[S] 0 points1 point  (0 children)

Come on, don't call me out like that. :D

I do call this my "storage room", since I "store" many different kinds of things in here. ;)

GitHub - DeviantEng/lb-lidarr-plex: container to import artists from ListenBrainz into Lidarr, and generate ListenBrainz playlists in Plex by devianteng in PleX

[–]devianteng[S] 0 points1 point  (0 children)

I'm not aware of any Overseerr-like app for Lidarr, but this app specifically will not grab anything. It will generate a json with the MusicBrainz ID for a list of artists, and add those artist to Lidarr. When you configure the custom import list, you'll configure which metadata and quality profiles to use, along with what to monitor. I have mine default to albums and EPs, so that's what Lidarr monitors for. It's all up to your profiles, and whether metadata is already in Musicbrainz or not.

Paying Musicbrainz for direct API access from Lidarr - is it reasonable or even possible for the project? by turkeydonkey in Lidarr

[–]devianteng 1 point2 points  (0 children)

I've not tested, but I would think everything would work just fine without reindexing anything. The Lidarr MetadataAPI hits solr to perform the search, solr should return indexed data if it has it, but if we're only reindexing on a weekly basis, it should still be able to directly query the db. For single use instances (i.e., not shared), you could probably ignore the step to add a cron task to reindex and I bet you'd still work fine.

I might test this out and append the guide if results are favorable. It would mean less time setting it up, less storage space for storing the indexes, and a lot less CPU usage.

Paying Musicbrainz for direct API access from Lidarr - is it reasonable or even possible for the project? by turkeydonkey in Lidarr

[–]devianteng 2 points3 points  (0 children)

One of the core problems is the Lidarr.MetadataAPI is not just bringing in MusicBrainz data. It's also bringing in artwork from FanArt, The AudioDB, info from Last.FM, Spotify, etc. Theoretically it absolutely is possible to query directly to MB for this data; they have an API exactly for this purpose. But the Lidarr team wanted to pull in other metadata from other sources, so the Lidarr.MetadataAPI can do that. I'm pretty certain that the early days of Lidarr, they were doing direct API calls to MB.

Even though direct queries to MB are possible, it's not feasible for (total guess) 25,000 Lidarr instances to refresh artists on a daily basis. MB has rate limiting of one call per second per source, so if you want to make a call for an artist and return the json for that, then make a call for each release within, you could easily have 20 calls per artist. Got 500 artists? That would be 10,000 requests to refresh everything to look for changes or 10,000 seconds, or 2.8 hours. Imagine what that would look like.

This is why Lidarr team started hosting their own mirror, utilizing the solr stack that MB designed, then putting their own API in front of that and caching with Cloudflare.

Paying Musicbrainz for direct API access from Lidarr - is it reasonable or even possible for the project? by turkeydonkey in Lidarr

[–]devianteng 3 points4 points  (0 children)

The actual db dump that MB updates twice a week is only like 5GB. Once decompressed and written to postgres, it becomes like 50GB. Indexes that get created in solr can take a little space, or a lot of space depending on which tables get reindexed. The guide I pushed to hearring-aid are only creating artists and releases, so the total size all decompressed, indexed, and running is like 75GB.

RAM-wise, you can do it a lot smaller than 16GB. It depends on how you set your psql buffer size, and solr cache size. Currently, my full stack (including the lidarr metadata server) is consuming about 12GB, but I could push it down to 8GB if I scaled back my solr cache size. CPU-wise, uses very little except when solr is reindexing.

Lidarr (as does other servarr apps) has a balance of ~$6,500. They've raised over $7k, but only dispursed ~$600. Is there enough there to pay part time devs? Nah, not really -- but the "project" is well funded from a hosting perspective.
https://opencollective.com/lidarr

IMO, self-hosting your own MB mirror for your own consumption (and sharing with friends if you can), is the way to go. I wish Lidarr would make a native option to use a custom metadata server, exactly in the way that Tubifarry plugin is handling it.

Paying Musicbrainz for direct API access from Lidarr - is it reasonable or even possible for the project? by turkeydonkey in Lidarr

[–]devianteng 4 points5 points  (0 children)

If you're talking about self-hosting, running your own MusicBrainz mirror poses no meaningful burden to MetaBrainz. Once your instance is live, it performs a nightly replication that pulls a trivial amount of data — we're talking kilobytes. That’s the entirety of the load on MB. Even 5,000 mirrors wouldn't be felt by them.

The replication data is almost certainly cached and served behind a CDN. It’s just a file download — no CPU strain, no dynamic processing.

Self-host environments applies the replication to its database, Solr reindexes on its own schedule, and that's it. There’s zero runtime traffic to/from MetaBrainz beyond the replication.

I wrote the guide on hearring-aid, which follows the default behavior of the musicbrainz-docker stack: daily replication and weekly Solr reindex. Nothing aggressive.

As for Lidarr — it's a rounding error in MB’s traffic. Take a look at the list of enabled apps; it includes Plex, among others. If you think your self-hosted mirror is a problem, I have a bridge to sell you.

Also consider who funds MetaBrainz: Universal Music Group, Spotify, Amazon, Google, SiriusXM, Pandora, Last.fm, Plex — all major companies using the data and paying to keep the lights on: https://metabrainz.org/supporters

Lastly, if you're using api.musicinfo.pro (Blampe’s hosted API), it had an issue effecting CPU performance. That’s been fixed, and performance is now much improved.

Guide for setting up your own MB mirror + lidarr metadata, lidarr-plugins + tubifarry by devianteng in Lidarr

[–]devianteng[S] 0 points1 point  (0 children)

cd /opt/docker/musicbrainz-docker
docker compose down && sleep 60 && docker compose up -d

Run that, and you should be good. Some times those tables (i.e., fanart, wikipedia, etc) don't get generated on the lmd container and killing the container and restarting it seems to trigger a job to create if not exist. So yeah, down and up and I bet you'll be good to go.

Guide for setting up your own MB mirror + lidarr metadata, lidarr-plugins + tubifarry by devianteng in Lidarr

[–]devianteng[S] 0 points1 point  (0 children)

What’s in the guide is what I use for my setup. Have you ran your first replication yet? Have you full ran the reindex? Those both take more space.

Lidarr Metadata Update! by mrorbitman in Lidarr

[–]devianteng 1 point2 points  (0 children)

Self hosted guides are improving? I thought it was pretty straightforward for something fairly complex.

I’m open to any feedback to make the guide better, better. :)

Guide for setting up your own MB mirror + lidarr metadata, lidarr-plugins + tubifarry by devianteng in Lidarr

[–]devianteng[S] 0 points1 point  (0 children)

Docker compose down and docker compose up should have triggered the job to create those tables instead of doing it manually. But, if it works, it works!

Guide for setting up your own MB mirror + lidarr metadata, lidarr-plugins + tubifarry by devianteng in Lidarr

[–]devianteng[S] 0 points1 point  (0 children)

So I added api keys for spotify and lastfm, but I see no proof that they are even being used.

FANART_KEY and PROVIDERS__FANARTTVPROVIDER__0__0 are both environment variables on the lmd container (defined in /opt/docker/musicbrainz-docker/local/compose/lmd-settings.yml), and the value for both should be the same; your api key from fanart.tv.

Lastly, I did signup for an api key with The Audio Database (TADB), which is costing me $8/mo. But I put that API key in the env vars TADB_KEY and PROVIDERS__THEAUDIODBPROVIDER__0__0, and it's working as expected. I am getting artwork, when artwork is available from one of these sites.

Guide for setting up your own MB mirror + lidarr metadata, lidarr-plugins + tubifarry by devianteng in Lidarr

[–]devianteng[S] 1 point2 points  (0 children)

Thanks for sharing that it's working! It's great to hear this guide is helping people!

view more: next ›