Mixing 2 different Devices with 2 Different Software Applications … you will run into compatabilty issues
Disregard my Alaska theme … it use’s xml metadata
The one thing i’m thinking though as a possible solution …
Thumbgen and Hub/SMP created xml metadata has the opening and closing tags inside
eg.
<?xml version=“1.0” encoding=“UTF-8”?>
<details>
… info here…
</details>
now… i have tested this on the Live Hub … it will read metadata created by XBMC after renaming NFO to XML
but … metadata has different opening and closing tags inside which the Live Hub will display
eg.
<?xml version=“1.0” encoding=“UTF-8” standalone=“yes” ?>
<movie>
… info here…
</movie>
So, what i’m saying is … if your Mediabrowser 3 is strict with the open/close tags (and doesent recognise the opening tag) you may be able to Batch replace the Tags with something Mediabrowser 3 Will accept … and hopefully the WDTV will accept it as well (since the above worked… the WD may recognise MB3 tags)
textrep can batch replace tags in seconds (for 1000’s of xmls) example of usage here
http://community.wd.com/t5/WD-TV-Live-Streaming/Remove-Fan-Art/m-p/559353/highlight/true#M20098
Can you please post the Metadata text created by Mediabrowser 3 so i can further test this theory
