Is the movie db tv scraper borked as of right now? I just changed over from the TVDB about 2 weeks ago when it allegedly died.
No manual update for the add on available.
I think TVDB should work again.
That takes a fair while to redo all my TV tho. Is the movie dB dead or just having a temporary tiz?
Ask in the developers thread for the tmdb scraper on the Kodi forum maybe? We donāt keep up with the day to day function status of random add-ons.
Isnāt this a default more or less baked in part of it all working? Itās not some weird emulator or anything.
Itās a Kodi addon, not specific to OSMC.
But where is your media located? Unable to connect to remote server sounds more like Kodi canāt reach the media. Logs would be immensely useful in verifying itās accessibility.
You do not have to rescrape your content. When you do the āset contentā and change the scraping source you just need to say NO when it asks if you want to refresh the information.
Ahh ok, thatās very helpful. I assumed it would double up on everything.
Seems the movie TV dB is back.
I just had the tvdb go out on me again. Didnāt pick up Pennyworth or an episode of Preacher. So I put it back on to the moviedb TV and got it again.
Itās just weird because Iāve never had a scraping issue before and now in the last few weeks itās been a bit back and forth and Iām pretty sure itās not me.
While it may be a 3rd party add on, it is a core function of Kodi. I dare say that if for some reason it didnāt work under osmc then youād sell less units.
Iāve read that TVDB has been acting a bit funny today as well.
Noted. Honestly ā if it was something I could fix, Iād be all over it.
I do believe that there are alternative scrapers that can be used in the interim however. Consistency is certainly better though.
I guess Iām a bit sore on it because a sub driver that took 10 weeks to get to me wasnāt properly bonded to the basket so I had to fix that. Then one of my 3tb drives packed in. Then chuck in 2 faulty work laptops the last thing you want is your media player screwing around.
I guess you would be all over it now you mention it.
I would suggest broadening your view a bit. You did not purchase Kodi, you purchased a box that runs it. As with any large open source project there are going issues that come up and you often will not get the same expedant fixes that you might from a company that is actually getting paid to write software. Issues with scrapers have popped up in years past and they always got dealt with. We should all be thanking TheMovieDB, and not wagging our fingers at TVDB (or anyone else). Kodi is flexible enough that one could move to external scrapers and keep going. The issues lately are a little annoying, but they are easy enough to get around, and a far cry from making anyones hardware unusable.
I know what I purchased, if it didnāt run Kodi it wouldnāt be much use for it would there?
I havenāt had problems with scrapers before, itās new to me so I understand itās an add on, but itās still a major draw to the purchasing boxes that run Kodi. Thereās more fixes that come out of here than major manufacturers, Nvidia shield TV is one example.
I donāt see a problem with wagging fingers either. Iām sure it wasnāt designed to āsort of workā And Iāll bet whoever is responsible for it is likely hard at it, but again if I donāt know and no one else is reporting on it Iām not going to sit and wonder.
I didnāt say it was unsuable either I said the scrapers were a big part of Kodi and likely the sale of the boxes.
Iām aware of the issues with TVDB and hope this will stabilise.
If they donāt ā we have some ideas on how to mitigate this
Cheers
Sam
1 Like
Thanks Sam, thatās helpful.
Here are two much more appropriate locations to do your finger wagging that might actually be seen by the parties responsible.
1 Like
I dunno, I think this is a good location since users of the Vero are likely to come here if something isnāt right with it and then they can look at the info and see there are currently some scraper issues over the last short while.
If you applied that logic to all the other bugs/issues i see people posting about that arent specific to the Vero hardware, theyād be sent to all corners of the internet.
The most important people for such an issue are not looking into our forum though. It might make other OSMC users aware of an issue and its possible cause, yes. But it doesnāt help fixing the root cause as much as it would to ping the actual devs/maintainers of the DB.
I get that completely, however Vero4k is a business at the end of the day. If Kodi (the driving force behind Vero) has a major borked component then users are going to show up here - again, look at the amount of posts that arenāt hardware specific and out of OSMCās hands.
Iād also wager that the devs here would be taken a lot more seriously by the kodi people than x amount of random guys from the internet reporting on stuff that may or may not be a bit flaky.
My whole topic was a case of āhey, whatās going on with this?ā and then get polar opposite reactions - but the most helpful ones where along the lines of ākodiās a bit flaky, sometimes it does this and we have plans if itās a persistent issueā
Thatās what your userbase wants to hear on this forum, and why itās so popular because of people like @sam_nazarko already go out of their way to do little cunning tweaks that help even the lowest percentile of Vero users, that is a major draw of this box over others.
This is the biggest flaw in your logic. The more random ppl reporting the issue actually confirm the problem for those devs who maintain a function or feature that may have a hiccup. Itās also important for those devs to be able to gather diagnostic info from the affected users.
Secondly, the OSMC team is small and working uncompensated in our free time. Itās more beneficial for you that we focus our limited resources on the ācunning tweaksā.