Lidarr Import Settings Not Being Respected By Mixarr

Jan 18, 2026 by Editorial Team 53 views

Hey guys! 👋 Having some trouble getting your Lidarr import settings to play nice with Mixarr? You're not alone! This article dives deep into a bug where the settings configured in your Lidarr connection within Mixarr aren't being applied when you add a new artist. We'll walk through the issue, how to reproduce it, what you'd expect to happen, and some potential workarounds. Plus, we'll sprinkle in a little feature request action, because, why not?

The Bug: Settings MIA 🕵️‍♀️

So, the deal is this: you've got your Mixarr setup, linked it to Lidarr, and configured those sweet import settings – things like quality profiles and monitoring options. You figure, "Awesome! When I add a new artist through Mixarr, those settings should automatically apply in Lidarr, right?" Wrong! 😩 It seems that the import settings configured within Mixarr aren't being respected when you add a new artist. This means you might end up with artists in Lidarr that aren't using your desired quality profile or aren't being monitored the way you want them to be. Talk about a buzzkill!

This issue was brought to light by a user, and they've kindly provided all the deets so we can understand the problem. The user has done some digging and found that after adding an artist via Mixarr, the settings on that artist within Lidarr don't match the settings configured in the Mixarr connection. They've double-checked things like the quality profile and monitoring options, confirming that the settings are indeed being ignored. Yikes!

The implications of this bug are pretty significant. It means you'll have to manually configure each new artist in Lidarr to match your desired settings. That's a huge time-suck, especially if you're adding a bunch of new artists. Imagine having to go back and manually adjust the quality profiles and monitoring settings for every single one! Nobody wants to spend their time doing that. This bug can lead to a less efficient and more frustrating experience, because it can prevent users from fully automating their music library management. The key to automation is making sure things like import settings are automatically applied. Without this functionality, you'll have a fragmented and not-fully-automated experience.

Now, let's get into the specifics of how to reproduce this bug.

Quality Profile Confusion

One of the most noticeable areas where this issue surfaces is with Quality Profiles. You've probably spent time setting up custom quality profiles in Lidarr to ensure you get the best possible audio quality. When you add a new artist through Mixarr and this bug is present, the artist might end up with the default quality profile instead of the one you carefully selected. This means you could be missing out on higher-quality versions of your favorite tracks. This also means you have to be extra vigilant and constantly double-check the quality profiles, which is obviously less than ideal, and potentially can create a messy library. A simple and easy-to-use experience is what every user wants.

Monitoring Madness

The other main area of concern is monitoring options. Do you want to automatically monitor new releases for every artist you add? Or do you prefer to manually manage which artists are monitored? Whatever your preference, you set it up in your Lidarr import settings in Mixarr. But, when this bug is active, the monitoring settings aren't being carried over. You might add an artist and then realize they aren't being monitored, meaning you won't be notified of new releases. This can lead to missing out on new music from your favorite artists, something every music lover dreads!

As you can see, the impact of this bug extends beyond mere inconvenience. It can affect your music library's overall quality and management. Ensuring your import settings are correctly applied is a core functionality that helps users set up a seamless music library management experience. Let's dig in and figure out how to reproduce the bug so you can try it on your own.

How to Reproduce the Issue: A Step-by-Step Guide 🚶

Alright, let's break down the steps to reproduce this bug. Follow these, and you should be able to see the same behavior yourself. Remember, this assumes you have both Mixarr and Lidarr set up and connected. Here's the drill:

Add a Lidarr Connection: First things first, make sure you've got a connection to your Lidarr instance set up in Mixarr. This is the foundation upon which everything else is built. If you haven't already, head over to Mixarr's settings and add your Lidarr connection. Make sure the connection is confirmed and working properly. You should be able to see the Lidarr import settings once the connection is established.
Configure Lidarr Import Settings: Now, here's where the magic (or the lack thereof) happens. Once your Lidarr connection is set up, you'll see a section for "Lidarr Import Settings." This is where you configure things like your desired quality profile, the monitoring option (e.g., "Monitor" or "Do not monitor"), and any other settings that you want to apply to new artists added through Mixarr. Important: Set any of these settings to something other than the default values. For instance, pick a specific quality profile that's different from the default one. Or, change the monitoring option to something other than the default value.
Search and Add a New Artist: Now, it's time to test things out. Go ahead and search for a new artist in Mixarr that you want to add to your library. When you find them, add them to your collection. This is the moment of truth!
Check the Artist's Settings in Lidarr: Switch over to Lidarr (or open it in a new tab/window). Find the artist you just added through Mixarr. Check the artist's settings in Lidarr. Does the quality profile match the one you selected in Mixarr's Lidarr import settings? Is the monitoring option set the way you configured it in Mixarr? If the answer to either of those questions is "no," then you've successfully reproduced the bug! The settings are not being applied as expected. You'll likely see that the artist has the default settings instead.

By following these steps, you should be able to replicate the issue and confirm that the Lidarr import settings aren't being applied when adding new artists through Mixarr. The whole goal is to allow users to automate their music library management, and this bug is a roadblock to that goal.

The Expected Behavior: What Should Happen 🤩

Okay, so what should happen? What's the ideal scenario here? Simple: When you add a new artist through Mixarr, the settings for that artist in Lidarr should match the settings you configured in the Lidarr connection within Mixarr.

Specifically, this means:

Quality Profile: If you selected a specific quality profile in Mixarr's Lidarr import settings, the new artist in Lidarr should automatically be assigned that quality profile.
Monitoring Option: If you chose to monitor new releases for the artist in Mixarr, the artist in Lidarr should be set to "Monitored." If you chose not to monitor, the artist should be set to "Unmonitored."
Other Settings: Any other settings you've configured in Mixarr's Lidarr import settings (e.g., root folder, metadata profile, etc.) should also be applied to the new artist in Lidarr.

In essence, adding a new artist via Mixarr should be a seamless process, where all your desired settings are automatically applied, saving you the hassle of manual configuration. The whole purpose of having these integrations is to allow for easier, faster, and more automated music library management. The current bug completely undermines the intended workflow and creates unnecessary manual steps, which kind of defeats the point of using these apps together.

Screenshots: Visual Proof 📸

The original bug report includes helpful screenshots to illustrate the issue. The screenshots show the Lidarr settings in Mixarr, highlighting the configured import settings. The screenshots then go on to show the artist's settings in Lidarr after being added through Mixarr, revealing that the settings do not match. This visual evidence clearly demonstrates that the import settings are not being respected.

Additional Comments and Feature Request 🎁

Beyond the bug report, the user also mentioned a potential feature request: the ability to set the metadata profile within Mixarr's Lidarr import settings. This would be a welcome addition, as it would provide even more control over how new artists are managed in Lidarr. Being able to specify a metadata profile when adding an artist would ensure consistent metadata across your entire library, streamlining the organization and management of your music collection. This is a small addition, but it would have a huge impact on the user experience.

Debugging and Finding a Solution 🛠️

Unfortunately, as an end-user, it's difficult to propose a definitive fix without having access to the source code of both Mixarr and Lidarr. However, here are some troubleshooting steps and general areas where the problem could be rooted:

Check Mixarr Logs: The first step is to check Mixarr's logs for any error messages or warnings related to the Lidarr connection or artist imports. The logs might provide clues about why the settings aren't being applied. If you're lucky, there might be an obvious error. If there are any logs, that information can be useful for developers to understand the issue.
Verify API Communication: It's crucial to ensure that Mixarr is correctly communicating with the Lidarr API. Verify that Mixarr is sending the correct data to Lidarr when adding a new artist and that the data includes the import settings.
Inspect Data Payload: If possible, inspect the data payload that Mixarr sends to Lidarr when adding a new artist. This will allow you to see exactly what information is being transmitted and whether the import settings are included.
Lidarr API Documentation: Cross-reference the Lidarr API documentation to ensure that Mixarr is using the correct API endpoints and parameters for setting import settings.
Mixarr Updates: Keep your Mixarr installation up to date. The bug might be a known issue that has already been fixed in a newer version. Check to see if there are any updates, and update when possible.
Lidarr Version: Make sure that the Lidarr version is supported by the version of Mixarr you're using. Compatibility issues can sometimes cause unexpected behavior.
Community Forums/GitHub: Reach out to the Mixarr community or check the Mixarr GitHub repository for any existing bug reports or discussions related to this issue. It's possible that someone else has already encountered the same problem and found a workaround. You might be able to discover the solution in these communities!

Conclusion: Seeking a Fix and Hoping for a Solution 🙏

So there you have it, guys. The Lidarr import settings aren't playing nice with Mixarr. This bug is causing frustration for many users who want a seamless and automated music library management experience. It is disrupting the ideal workflow. The good news is that the community is aware of the issue and that the solution is possible. The most important step is reporting the issue, and hopefully, it gets addressed in a future update. We're keeping our fingers crossed for a fix soon, so we can get back to enjoying our music without any manual headaches! Stay tuned for updates, and let's hope for a speedy resolution! 🎶