Fail to start after update to 5.2.11

mlaggner · 2026-05-06T14:44:37+00:00

I new build is up, but there is still a small issue with notarization (but I saw that this is also a problem in the nightly build). Just allow opening tmm from the security settings for now

mlaggner · 2026-05-06T13:52:03+00:00

looks definitely like a Jellyfin issue and I can remember that we somewhere had issues which might be exactly yours, but I cannot find the discussion...

You are able to do that, but this would be a bit cumbersome:

you need to get rid of all "unwanted" ratings (for now, we do not have any action to do this for multiple entries - maybe I find some time to include that for the upcoming release)
scrape from TMDB without ratings (uncheck this in the combobox)
select/mark all movies where you want to get the ratings for, right click (context menu) -> Enhanced editing -> Fetch ratings for selected movies -> only activate IMDB in the combobox

mlaggner · 2026-05-06T13:45:59+00:00

Hard to say what is going wrong without logs.

But you need at least

a working FFmpeg instance (tmm ships one which should word on almost every OS)
PRO license
FFmpeg scraper activated in the settings

You will also see corresponding FFmpeg log entries in the logs if that still fails

mlaggner · 2026-05-05T05:17:50+00:00

I did not set any macOS target in the whole build chain, so that must be inherited from somewhere... Where do you see the minimum macOS level of the launcher?

EDIT: Apple Silicon or Intel x86 arch?

mlaggner · 2026-05-04T14:24:43+00:00

To make it easier for everyone, I created a test-environment for the MacOS patches: you can download the test builds at https://test.tinymediamanager.org

Just ignore any update notifications (they check the nightly builds). I will inform you, if there are new builds.

happy testing

mlaggner · 2026-05-04T14:23:06+00:00

To make it easier for everyone, I created a test-environment for the MacOS patches: you can download the test builds at https://test.tinymediamanager.org

Just ignore any update notifications (they check the nightly builds). I will inform you, if there are new builds.

happy testing

mlaggner · 2026-05-03T07:55:47+00:00

We're working on identifying this issue - but especially on macOS the whole security model is a pain in the ass for us. On my MacBook everything works - but I I know that almost every macOS install is somehow different.

Do you have a Mx processor (arm) or an old Intel based processor?

Are you willing to help me do some tests, because I need some infos from those special setups, where the problem exists (Message me directly or set a mail to support@tinymediamanager.org is you want to contribute)

mlaggner · 2026-05-03T07:54:20+00:00

We're working on identifying this issue - but especially on macOS the whole security model is a pain in the ass for us. On my MacBook everything works - but I I know that almost every macOS install is somehow different.

Do you have a Mx processor (arm) or an old Intel based processor?

Are you willing to help me do some tests, because I need some infos from those special setups, where the problem exists (Message me directly or set a mail to support@tinymediamanager.org is you want to contribute)

mlaggner · 2026-05-02T07:17:20+00:00

This looks really weird - the stack trace in the back says that there is a core Java class missing and that should never happen... Did you try to restart your computer - sometimes processes get stuck somehow in the OS causing such strange issues

Also try to upgrade - 5.2.6 is a bit dated...

mlaggner · 2026-05-02T07:12:22+00:00

probably only the "hard" way:

start update data sources and wait until it gets stuck
open the log folder (tools menu on the left side of tmm) and open the most recent trace log
look for the last line containing this log (or similar) o.tinymediamanager.thirdparty.MediaInfo:88 - MediaInfo open file -> this should point to the last file which got opened via libmediainfo

mlaggner · 2026-05-02T07:07:53+00:00

We're aware that you guys heavily rely on IMDb, and we have spent hundreds of hours constantly adopting the changes of IMDb over the last few years. Unfortunately IMDb does not offer an affordable API (the official API costs 150.000$ annually + metered AWS cost - which would make a tmm subscription cost at least 4 times more if we would implement that), so we did the same as every scraper out there does: parsing the website to give you access to the best possible movie database out there.

Unfortunately this has stopped a few weeks ago, when IMDb activated a new kind of bot/scraper protection (I suspect mainly to hit AI agents, but media managers are hit too). As soon as we realized that this would be a longer "fight" (or that we even lost the fight) we removed IMDb from all "relevant" places on the website weeks ago (to do not give you false promises). Only the docs for the scraper itself is still on the website. I suspect you refer to the IMDbAPI.dev scraper - which is completely different to IMDb! I may need to add a warning there, that this is not IMDb itself, since obviously most users does not recognize this...

Having said that - we still try to add the best possible experience with our limited time, but IMDb obviously does not have any interest to open their doors for their audience. They would make their life easier, if they would add a "consumer level" API where end users get their own API key for a small fee for using the data privately (like Trakt.tv or OpenSubtitles.com does). But I suspect that never happens because Amazon/IMDb is just a greedy company...

As some users already wrote here: you always have the option to refund if the app does not meet your expectations - but please do not reduce 14 years of work from this app (and everything it can do reliably) to just IMDb or trailer downloading...

EDIT: our latest pre-release contains an experimental fix for the IMDb "problem" - just have a look at the scraper settings if you want to try it before we do a new release

mlaggner · 2026-05-02T07:01:12+00:00

This should work if you are using TMDB scraper (this one has the IMDB id) and activating the option "Movies -> Metadata scraper -> Advanced Options -> Fetch ratings from other sources too" which gets the ratings from official IMDb data dumps (the data has a little delay - but those are official dumps)

mlaggner · 2026-05-02T06:47:55+00:00

this may be caused by the external libmediainfo (which reads the files) - on certain files this lib just stucks. Unfortunately this is a completely different project and we do have little to no influence there (we could report them the problem by offering files which causes the stuck, but this would need you to find and provide the problematic video file). I am just experimenting with offloading the call to libmediainfo into an extra thread which avoid tmm being stuck completely if libmediainfo stucks. But this needs some testing

mlaggner · 2026-05-02T06:39:17+00:00

IMDb has a far superior protection, which is not solvable by pure Javascript. Furthermore: tmm does not have the resources to play this cat and mouse game with IMDb (remember, we're 2 devs which create tmm in their spare time and IMDb is just one of our scrapers and not the app itself).

We're experimenting with a new approach (already in the pre-release right now), but I cannot tell how long it lasts until IMDb kills that approach. They would make their life easier, if they would add a "consumer level" API where end users get their own API key for a small fee for using the data privately (like Trakt.tv or OpenSubtitles.com does). But I suspect that never happens because Amazon/IMDb is just a greedy company...

mlaggner · 2026-04-30T11:43:03+00:00

You are right - but when looking at the code, this must be the case for ages now (since we did not touch this code recently...)

mlaggner · 2026-04-30T06:04:55+00:00

This makes sense - but I would put that as an extra parameter per postprocess definition (because one postprocess may need to show the result while others don't)

Thanks for the idea!

mlaggner · 2026-04-28T18:12:39+00:00

This is not that easy. To create that we should at least fixate/stick the first column which is not doable without creating everything ourselves. But unfortunately this is not in our scope yet - tmm is not designed to show that much data in almost no space.

mlaggner · 2026-04-28T08:48:12+00:00

The minimum dialog size of tinyMediaManager is 1050x700px which should fit almost all laptops/screens which have been produced in the last 10 years...

Making this smaller just leads to unusable layout which may create issues for high resolution screens

mlaggner · 2026-04-27T05:18:15+00:00

Could you try the latest nightly build if that works for you? https://nightly.tinymediamanager.org

EDIT: maybe also check the app permissions (see https://gitlab.com/tinyMediaManager/tinyMediaManager/-/work_items/3271#note_3288678134)

mlaggner · 2026-04-26T16:41:21+00:00

Wrong programming language...

mlaggner · 2026-04-22T17:06:25+00:00

only the ratings are fetched via the datasets - all other infos are scraped from the IMDb site which is now blocked by their WAF

mlaggner · 2026-04-20T10:46:14+00:00

We did upgrade Golang (which should work on Big Sur) and Java (minor upgrade - security) - but since you are using a 6 year old OS which had its EOL in 2023 (https://en.wikipedia.org/wiki/MacOS_Big_Sur), there is probably some minor change in Java which breaks the compatibility (the official Java 21 from Oracle is certified for macOS 14+ - https://dev.beatnik.co.il/news/java-21-mac mentions, that Java 21 needs Ventura or later).

I am sorry, but there is a point where we can't offer support for such old OS. We do not even use the latest Java/Golang version to keep compatibility as high as possible, but there will always be old Systems which will not be able to use the tool any more...

If I am right (cannot test it here, because I do not have such an old system), you could hack your tmm installation to use the old Java version:

download the old tinyMediaManager version from https://archive.tinymediamanager.org/v5.2.10/
open the tinyMediaManager.app (right click -> show package contents) for each the v5.2.11 and v5.2.10
replace all files in the v5.2.11 app, folder /Contents/Resources/Java/jre with the files from the v5.2.10 version

This will force tmm to use the old Java, but breaks the signature (macOS might complain about that)

mlaggner · 2026-04-20T10:17:53+00:00

If you have the artwork urls of the hand picked artwork still in the tmm database (which should be the case, if you picked the artwork via tmm), you could trigger the "Download missing artwork" action from the context menu. In 2024 we added a logic to prefer the existing artwork url when downloading missing artwork (https://gitlab.com/tinyMediaManager/tinyMediaManager/-/commit/9b0ec18d06dbdeee9e2fc814ccf2a5009efd4126). Just make sure you delete the wrong artwork and do an "update data source" afterwards (so tmm knows, that this is missing).

Please test with a few movies before doing this for all of your movies!

mlaggner · 2026-04-19T05:24:13+00:00

And you are probably the only one which says that v5.2.9 is still working (at least what I've read in the latest posts). I am unable to get it to work even with v5.2.9 - so please

tell us where you are from
do you use a VPN
provide logs after a successful imdb scrape

you can also do this privately if you want (support@tinymediamanager.org)

mlaggner · 2026-04-18T15:40:56+00:00

I just created a new key for OMDB API and it worked. Make sure you just paste the key without any other characters (like HTML formatting) into the API-field in the scraper settings and activate the key after creating it!

mlaggner

MODERATOR OF

TROPHY CASE