2013-01-27, 00:19
I submitted a pull request to start utilizing a setting that's not exposed named VideoTSParent. Is anyone using this setting? I'm curious as to it's history. So far it seems safe to expand on it.
If accepted, the VideoTSParent setting in Settings.xml can be set to true and then the user's specification of fanart.jpg as opposed to <movie>-fanart.jpg will be utilized and saved to the parent folder of the BDMV or VIDEO_TS folder. i.e. C:\Movies\Avatar\ for a C:\Movies\Avatar\BDMV\ structure.
Until this change I could use the VideoTSParent setting, but it would always save <movie>-fanart.jpg in my movie's main folder which, despite my interpretation of the frodo naming conventions, doesn't seem to be utilized by the latest xbmc. This would occur even if I had fanart.jpg selected in settings.
Thoughts/concerns welcome. Thought I'd bring it up in case someone else wasn't watching the commits and pull requests, or had any input.
If accepted, the VideoTSParent setting in Settings.xml can be set to true and then the user's specification of fanart.jpg as opposed to <movie>-fanart.jpg will be utilized and saved to the parent folder of the BDMV or VIDEO_TS folder. i.e. C:\Movies\Avatar\ for a C:\Movies\Avatar\BDMV\ structure.
Until this change I could use the VideoTSParent setting, but it would always save <movie>-fanart.jpg in my movie's main folder which, despite my interpretation of the frodo naming conventions, doesn't seem to be utilized by the latest xbmc. This would occur even if I had fanart.jpg selected in settings.
Thoughts/concerns welcome. Thought I'd bring it up in case someone else wasn't watching the commits and pull requests, or had any input.