There are user defined options for cache, metadata, trans-coding temp folder, I don't see any difference.
Put it with the other metadata or at the very list have a configurable setting in the plugin so for example I could make a new folder called d:/rokubifs and store them all there.
It does not make sense to store this data with media.
What if I decided after 1 year to switch to AppleTV then I have all the BIF data polluting my media library
Hey, I am with you. More options to get closer to making 100% of users happy is a good thing. I tried to please 100% with blue neon hence all the options. The new app will hopefully try to get there too (or at least open source the code so others can take it there.. wink wink)
Now as for the plugin thing, this is the constructive side of it, explain why. Your mention that very shortly the roku may be abandoned as a platform on your server is compelling. This does indeed satisfy my argument that these are the same as trailers, etc. Clearly in this case, they are not. It should allow saving in with media or a custom path as an option.
The plugin is open sourced, shows on github, can be forked and pull requests made. Not sure how the java api is built or id try my hand at this. Anyone else have the time and inclination?
Edited by speechles, 20 March 2017 - 07:38 PM.