This may have been due to exiting while the program was still scanning folders when the media library was still enabled, but it's stupid Java, so who knows. One time so far the javaw.exe process stayed stuck in memory on exit, consuming over a GB of RAM. And it doesn't mention that the server has to be restarted to recognize this change.
I had to disable transcoding of mp4 and others, because it was transcoding most files even though my WDTVLive device supports them directly just fine. I disabled and forego the media library to avoid this. Only caveats I've found: - The database size it creates for a modest media library it rather large, and takes forever to scan. But the program is nicely configurable, and does work rather well. In the Settings > System > Developer > Media transcoding developer options page, set the Override transcoding defaults toggle to on and then set the Enable. If this setting is enabled, media transcoding might occur in the backgroundfor apps other than the one you're developing. Well, it's still a thing made with yucky Java, but at least now it includes its own runtime of it, so there's no ancient security risk, system polluting, full Java install required anymore! Of course, being Java, it's a RAM, CPU, and disk space hog. In the Settings > System > Developer > Media transcoding developer options page, set the Override transcoding defaults toggle to on and then set the Enable transcoding toggle to on or off.
0 kommentar(er)
