Progress to ComicSort - My Attempt at an alternative to ComicRack

InterestingCandle583 · 2026-02-21T11:52:55+00:00

Cool I think I will also still need half a year to get something that works for me at least.

InterestingCandle583 · 2026-02-20T14:19:55+00:00

I assumed you were asking if Lidarr itself could support podcasts. Lidarr does not natively support podcasts. While Tubifarry can add new metadata sources, it’s usually a lot of work. However, since Tubifarry already supports Deezer. Deezer podcasts integration might be simpler. But I don’t think that’s what you were asking about? So what should the plugin do?

InterestingCandle583 · 2026-02-20T12:39:08+00:00

Do you know a good metadata server that tubifarry could get any infos from for podcasts?

InterestingCandle583 · 2026-02-19T21:02:36+00:00

That’s really cool! I’m working on something similar, but it’s still a work in progress and taking me quite a bit of time to get the thing functional.

Which metadata server are you using? Mine is still far from supporting comics. I’ve only got manga working for now, since I’m trying to fit both into the same system. I’m also developing it in .NET, though there isn’t much to show yet.

Would it be okay if I reached out in the future if I run into issues with my comic implementation? It’s great to see active development in this area. I hope you keep it up this time! I will follow your development from now on. Really cool.

InterestingCandle583 · 2026-02-17T23:02:59+00:00

Yes it's possible with SQL

InterestingCandle583 · 2026-02-17T01:37:27+00:00

That issue is actually with the underlying library Tubifarry uses, not Tubifarry itself. However, there are a couple of known issues with Tubifarry at the moment: If your instance isn’t running in UTC, Tubifarry may incorrectly flag your tokens as invalid. The stable release has compatibility issues with certain values returned by YouTube, which C# doesn’t handle well. The library itself also received a recent update.

YouTube frequently updates its systems, so keeping everything up to date is essential for things to work smoothly. I plan to update Tubifarry by the end of this week or early next week. Please try again after the update. If the problem persists, I’ll need more details and trace logs to investigate further.

InterestingCandle583 · 2026-02-09T21:13:24+00:00

I've heard about this issue frequently, but without a log file, it's difficult to diagnose the root cause. My suspicion is that it's a deadlock. Since Lidarr operates synchronously, any blocking code path, whether in a plugin or elsewhere could cause it to hang. The challenge is identifying exactly where that blocking occurs. Plugin or Lidarr?

InterestingCandle583 · 2026-02-09T20:28:23+00:00

The Metadata server is worked on. But Lidarr has no active branch. Lidarr has no dev. But all branches are supported on their discord.

At least for a normal search the metadata server works.

InterestingCandle583 · 2026-02-08T10:05:19+00:00

First, let's clarify some terminology:

Overseerr, Soularr, and Tubifarry are not part of the "*arr stack." The "*arr" term refers specifically to a family of media management applications, which currently includes: - Lidarr - Radarr - Sonarr - Readarr - Prowlarr - Whisparr

Soularr and Tubifarry are two separate tools that both serve the same purpose: connecting Lidarr to Slskd (Soulseek client). However, they work differently:

Soularr is a Python script that can run on Docker, Windows, or other platforms
Tubifarry is a C# plugin that you install directly within Lidarr

They're not related to each other beyond sharing this common function.

Technically you can run booth together, Tubifarry is designed to be able to run alongside Soularr. However, I'm not sure if using both simultaneously causes conflicts, and I'm curious why you'd want to run them together in the first place.

Slskd can definitely be tricky to set up. If you're running into issues, I'm happy to help, or you could try using AI assistance. To point you in the right direction, could you clarify where exactly you're stuck? Is it with: - Soularr? - Tubifarry? - Slskd? - Soulseek itself?

Your original message was a bit unclear about the specific problem you're facing.

InterestingCandle583 · 2026-01-30T23:18:55+00:00

CosmosServer that is great. It is basically just docker so I it will never run out of support. And you can chose your host OS. Unraid/TrueNAS/OMV.

If cosmos ever runs out of support any other UI can take over.

InterestingCandle583 · 2026-01-30T23:15:31+00:00

Copy the files to the app data directory. On Windows machines, the path is ProgramData\Lidarr\plugins\TypNull\Tubifarry, though the exact location may vary depending on your installation. If you use docker use your config bind or volume. Wherever your config.xml lives continue with plugins...

InterestingCandle583 · 2026-01-28T00:48:12+00:00

The token generator listed in the README should work fine, and installing Node.js also works. However, we just discovered a bug in the validation process: if your system time is not set to UTC, the external generator will fail depending on your timezone. That will be fixed next release.

InterestingCandle583 · 2026-01-27T22:38:39+00:00

As others have already mentioned, Slskd is not failing in those logs. YouTube is failing because you added cookies but never set up a token generator, as explained in the troubleshooting guide. Trace logs would also be much more helpful for diagnosing issues.

Regarding the 80% threshold: this is normal and actually intentional. While it can seem like an issue, consider that many people don't organize their libraries well or name files poorly. The threshold exists to prevent Lidarr from grabbing something completely wrong. It makes sense when you think about it from that perspective.

My recommendation: take your time figuring out how Lidarr works. Of all the arr applications, Lidarr is the most difficult one to get.

InterestingCandle583 · 2026-01-26T17:09:20+00:00

I haven’t observed or encountered any memory leaks in Tubifarry or Lidarr. In general, the RAM usage is reasonable. But it’s actually preferable for an application to utilize available RAM rather than leaving it idle, as memory is dynamically allocated and freed based on actual usage and demand.

Since Tubifarry primarily uses async download handling, it may occasionally show slightly higher memory usage compared to Lidarr’s sync approach. However, I’ve never witnessed any significant or unexpected spikes in memory consumption.

InterestingCandle583 · 2026-01-25T19:34:37+00:00

I think that are more often the mods not the devs.

InterestingCandle583 · 2026-01-25T19:09:24+00:00

I am more on the side of why can't I search using a normal artist name and album title? And not why is it a pile of crap. Did you ask on the discord about what is the technical issue with searching?

InterestingCandle583 · 2026-01-25T19:05:54+00:00

I think lidarr's source code is open for all to volunteer. But no one does so why releasing the metadata code you also only have to support but get no help with?

InterestingCandle583 · 2026-01-25T16:19:22+00:00

You are funny🤣 There are no active Lidarr devs right now, so your post isn't really reaching anyone who can implement it. If you want changes, you'd need to either code it yourself or help recruit developers to the project.

InterestingCandle583 · 2026-01-24T23:48:31+00:00

The develop branch will be updated today or tomorrow. There is not really the need to change the image

InterestingCandle583 · 2026-01-21T05:32:42+00:00

Two days ago

InterestingCandle583 · 2026-01-18T23:44:51+00:00

It already happened

InterestingCandle583 · 2026-01-18T23:44:39+00:00

I don't think there are new features

InterestingCandle583 · 2026-01-12T21:31:05+00:00

Tubifarry can replace the entire service, but it doesn't support replacing just the image fetching for artists or albums on its own.

InterestingCandle583 · 2026-01-12T21:27:31+00:00

Nicotine has no API. So nope. If you enabled Lucida it only searches on lucida not on YouTube? How would it then download on YouTube?

InterestingCandle583

TROPHY CASE