Wrong movie

Hi there. I'm new to Serviio so I'd really appreciate your patience as I ask some newbie questions.

First off, Serviio is running on a Synology 1511+ (x86) NAS. The problem is that some of the movies are not being scraped accurately. I'm also an XBMC user so all my folders are setup properly (see screenshots). Is there a way I can manually correct the name Serviio scrapes? If not, I read on this board that I can have XBMC manage my library? How exactly can I accomplish that?

Thanks in advance.

[slyguy42o]

you can use xbmc and a few other formats, check out the metadata tab of your serviio console for meta options.

So there's no way to manually fix an incorrect match???

You can switch to use XBMC nfo files. Then you're in full control. Otherwise, no, you can't fix an incorrect match.

This seems like a very simple but important feature missing.

Also, after almost a day, why are ffmpeg and java still using so much of my resources?

[moltra]

are you using any online sources? If so it might be getting the new information for the feeds.

[zip]

all the java processes - it looks weird. try to restart.

What OS are you on?

I restarted already and the same thing. I'm running this on my Synology 1511+ NAS running Linux (x86).

[zip]

Maybe ask in the NAS forum, they might be able to help.

Does the flowplayer watermark disappear when I purchase a pro license?

[zip]

No, but I'll try to remove it in future.

Can someone please explain why Serviio is confusing these two movies and how I can fix it? It's times like these that you REALLY need a manual way of fixing movies. Please please PLEASE put this in your next version release!

No, but I'll try to remove it in future.

Would really appreciate that. Thanks very much.

[zip]

Do you have online metadata of XBMC on?

No, I do not.

[patters]

1. Usually you can get the movie to identify properly by appending the year onto the filename.
2. As for the multiple Java processes - this seems to only occur on Intel Synology products, and happens with CrashPlan too. I'm unsure why since it definitely doesn't do this on ARM. The version of glibc is older on their Intel Linux distro so that could be responsible for some weirdness.