2009-06-12, 02:58
mfsav2 Wrote:is it for sure r282 64bit and EMM_Extras_07_x64
I even created a separated folder and installed them.
.... snip ....
So, like an idiot, i've been just creating the nfos by hand based on what you've posted..... and they worked fine. Just now I did what I should have in the first place and copy/pasted exactly what you had in the post. The problem, as ridiculous as it name seem, is the capital "M" in "<Movies>". That causes the serializer to freak out and fail because XML is case sensitive. Whatever program you're using to create these nfo files is creating them incorrectly.
So, I've done 2 things.... first added error catching to the extra serializers so it won't screw up anything else if it does cause an error, and wrote a little function to replace all elements with lower case. So, hopefully, it's fixed for you..... this could potentially cause problems with other xml files, but I don't think that would ever be the case with anyone using Ember because the nfo files it's looking for are relatively standardized.... and if not, it will just not load that file. lol
vism Wrote:No that would be me. The studio browser thing is great and very useful for me. Thanks for taking my suggestions. I'm sure those that use the Aeon studio flags will find it useful. This is my new favorite media manager!
About the studio flags... I know it's hard to keep track of all these studios and check for each match case. I was wondering if you wanted to bother with fixing those kind of things. For example, DC Comics will flag match to any studio with the word Broadcasting. ITI will match many studios that have 'iti' in it.
Ah, sorry about the "mistaken identity". If you didn't know, everything is stored in an XML file called "Studios.xml" located in "\Images\Studios" so you can edit that however you like. If you do make some fixes, we would all be very appreciative if you shared.