vidalvanbergen / ViMediaManager

Media Manager for Mac OS X
http://vidalvanbergen.github.com/ViMediaManager/
93 stars 7 forks source link

NilObjectException #42

Closed LTLNEMO closed 2 years ago

LTLNEMO commented 6 years ago

I keep getting this error and the app shuts down. The only thing that has changed was that I added tags to .nfo files. I have also done a complete reset of the app following your instructions

screen shot 2018-04-24 at 11 09 30 pm

vidalvanbergen commented 6 years ago

What were you doing just before the error popped up?

LTLNEMO commented 6 years ago

Updating List (movies)

vidalvanbergen commented 6 years ago

Do you know which movie it gives the error on? if so can you send the .nfo file of it?

LTLNEMO commented 6 years ago

I have no idea which movie it gives the error on because it doesn't necessarily go in order. I might just delete all the .nfo files I have and start over

LTLNEMO commented 6 years ago

I'm currently going through each .nfo file to see which one was giving VMM the error. However, one thing that I noticed is that updating the metadata overwrites my tags. Is there a way to not overwrite info that doesn't follow the .nfo formatting rules of VMM or create a way to add an outline for movie sets

vidalvanbergen commented 6 years ago

If you have previously existing metadata, rather then clicking the button for 'fetch metadata' or 'manual search' you should be able to save your custom tags by using the 'update metadata' button instead.

And if you manage to scrape data for them all by going over them one by one without raising further errors, than maybe ViMM was trying to fetch too much data or failed to write it quickly enough, do you have your media on networked attached drives?

LTLNEMO commented 6 years ago

I did use Update Metadata but when I do it rewrites and removes "<set through </set". If I'm adding a set tag, through manual editing of the .nfo, does it need to go after a certain tag for it not to get overwritten?

I couldn't find the culprit last night. I'm gonna try again today.

My media is on a Synology NAS

vidalvanbergen commented 6 years ago

That might be the cause then, it seems that ViMM has a problem doing a batch download of information to network attached storage devices.

If there's a way for you to connect directly to the device you might be able to get it working correctly.