Some songs that won't import

[nuttapillar]

Hi, I've come across a few songs that won't import, despite the album, artist, and title all perfectly matching. The songs appear in Jellyfin.

[AlexLArmstrong]

Hi @nuttapillar first of all, thank you very much to bring this to our attention!

Could you clarify where the screenshot with the json is from? Is it possible for you to also provide some excerpts from the logs?

Make sure to turn on verbose logging of the extension :)

Thanks!

[Viperinius]

I guess the json is from a "missing tracks" file that the plugin generated.

But yes, some debug logs would help. Also, what is configured in the section Playlist Track Matching on the plugin config page?

[nuttapillar]

Isn't it standard practice to use the missing tracks Json when using this plugin? I just click the Json that appears in the plugin settings page when I run the scheduled task.

[nuttapillar]

I will get the other info for you later when I'm not at work

[nuttapillar]

I've got it set to ignore case + punctuation. How can I find the log for this plugin?

[Viperinius]

• Follow the steps from the Troubleshooting section of the readme to enable debug logging
• Run the import task of the plugin in Jellyfin
• Go to the Logs section in the Jellyfin admin settings menu and click on the most recent log file

The plugin logs into the normal Jellyfin logs so make sure to only paste excerpts which start with Viperinius.Plugin.SpotifyImport (to avoid including any potential sensitive info from Jellyfin)

[nuttapillar]

I don't know where the troubleshooting or readme is, but I am seeing stuff from this plugin in the log anyway, so I have pasted here what I can see: https://pastebin.com/DkCzj8zZ

[Viperinius]

Sorry, forgot the link, I'm speaking about this readme.

[nuttapillar]

This is getting pretty confusing. I already had verbose logging turned on, so im trying the second option. The guide wants me to use '--configdir' But when I enter that in my server shell, it says 'zsh: command not found'

[Viperinius]

In order to find the config dir, you can also look into the admin dashboard. For example for me (in Docker) my data dir is /config:

This means, my config dir is /config/config. In that folder, you should see either a file logging.json or logging.default.json. When you find that, you should be able to follow the guide again (or just ask ;))

[nuttapillar]

Mine doesn't show the config/cache path. And I don't even know how to open those paths/entries. clicking them does nothing. I always only access the files on my server via my media shares on Windows file explorer.

[Viperinius]

Ok, earlier you already tried to get the config dir via your server shell. Let's try that again then: First, how are you running Jellyfin? Docker, something like Synology, directly on Linux/Mac,...? Depending on that, we might need to check if your Jellyfin starts with some flag --configdir.

Can you check on your server what the content of this variable is JELLYFIN_CONFIG_DIR?

echo $JELLYFIN_CONFIG_DIR

Otherwise, check in /config if it contains another subfolder called config which looks something like

/config/
└── config/
    ├── dlna
    ├── encoding.xml
    ├── logging.default.json
    └── ...

This is what we're looking for.

[Viperinius]

Closing this due to inactivity, please reopen if needed.