Hi,
I’m having a few problems with V2 and would like a download link for V1 if possible.
I’ll explain the problem but honestly I think the best move is to move back to V1 or Sickbeard until the features are back.
Without the XBMC nfo file being written XEM scraper seems useless, not sure if TVDB one would be ok. here is a pastebin of an recent episode of Dexter (8x5) http://pastebin.com/H451E7HF
I have setup XBMC Notifications, but I don’t see any options for it to update the library when a file is downloaded.
Cant match a tv show (M * A * S * H) to a folder as i assume *'s are a wildcard, the search doesn’t work.
Love the program, just concerned about some features that used to be rock solid not being around anymore.
MAS*H is currently a problem because the info is coming from trackt and it does not like special characters in the name:
It is on trackt’s list of things to do so just a matter of waiting on them at the moment.
There is an option in notifications for xbmc and to update on download.
Thanks for your help mspec, it looks like i overlooked that setting.
Hope to hear back about anyones experience with nfo files and if anyone had a similar problem to mine (more of an xbmc problem, will post over there soon)
If you’re using the Xem scraper in XBMC you shouldn’t be, its a hack of an implementation (from the folks that made Xem) and as well NzbDrone does the translation for you.
Its true, metadata isn’t yet available in v2, but we will be adding it in and making it better while we do it. If there is anything else missing, please let us know. There are a number of things already requested on Trello as well as things we want to add.
Markus101 while I have your attention, you may want to scan through and see if you left a hardlink to your m:\ build folder in the source. I got an error referencing it, i assume an error handle or similar had it hardcoded instead of variable.
Would have taken a screeny of the error (in the debug console on boot) but I ended up nuking it sorry.
@gatehead the errors show the build folder due to that being the path that was used when the application was compiled, this is standard for all .net applications, its nothing to be worry about (its just where the file that threw the error was when the app was built).