library update - check for new only

It would be ideal if there was an option to disable the updating of existing files in the library update and only check for new files. is this possible?

[zip]

http://bitbucket.org/xnejp03/serviio/is ... r-new-only

I take it this didn't make into 0.4.1?

[zip]

No, I'm still wondering if it's making sense in terms of it breaking everything

gotcha. is it possible to perhaps initiate an update programmatically? For example, i use XBMC as well, and i use their web api to initiate a library refresh only when a new file is downloaded.

[zip]

Serviio is using Corba, so it's possible if you can implement it.

What about just specifying individual shared directories to update? If some people are like me and have specified 5 or 6 different folders, but only added new files to one of them. Being able to only update that specific directory would be a huge benefit. Even if it went through all the current files, it would still be better than what we have now in terms of saving time.

This causes me a lot of headache too. Invoking ffmpeg so often causes a lot of (CPU) time and is just unnecessary.
Isn't it possible to make use of inotify? There's gotta be a java binding for this, and I'm sure something like that exists in win32 too.

edit:
I started a scan through the console about 3h ago. It's still "refreshing" the media library. I've added maybe a dozen files since the last rescan.

[zip]

Invoking ffmpeg so often causes a lot of (CPU) time and is just unnecessary.

FFmpeg is only invoked on new video files. Checking for updates doesn't do it (unless a file has been updated).

THere is inotify for Linux and Win, but not for OSX.

Well, does it try to use ffmpeg again on files where it has failed previously?
Anyway, I need to update to 0.4.1 and see if it still happens then.

Funny how OSX is a *IX system and doesn't support inotify.

[zip]

Funny how OSX is a *IX system and doesn't support inotify.

I think I found something, will try to get it into 0.5