Nvivo videos will not import or import without any sound

In much the same way that humans rely on the environment for air, water, food and shelter – Nvivo relies on its software environment (otherwise known as Microsoft Windows) for support. Now to make your Windows computer run faster, Microsoft has chosen to include as part of its software environment only those software resources that are commonly needed. When it comes to audio and video most people using Windows get by with the Codecs that Microsoft has included[1] and even more people never even need consider the word Codec.[2]

But successfully importing even familiar video formats such as .AVI and .MOV into Nvivo is hit and miss unless you take the time to install an extra Codec pack such as the Media Player Codec Pack[3]. It is not enough to rely on the list of supported formats that QSR advertise for Nvivo. As QSR themselves clarify on the Nvivo 10 Help website: “If the required codec is not installed on your computer, you will not be able to import or play the file, even if it is in a supported format.” [4]


  1. Microsoft. The default codecs that are included with Windows Media Player 9 and with Windows Media Player 10  Retrieved 31 January, 2013, from http://support.microsoft.com/kb/899113
  2. Wikipedia. (2013). Codec  Retrieved 31 January, 2013, from http://en.wikipedia.org/wiki/Code
  3. cnet download.com. (2013). Media Player Codec Pack  Retrieved 31 January, 2013, from http://download.cnet.com/Media-Player-Codec-Pack/3000-13632_4-10749065.html?tag=mncol;2
  4. QSR International. Media file formats supported by NVivo 10  Retrieved 31 January, 2013, from http://help-nv10-en.qsrinternational.com/nv10_help.htm

The xml file you selected to import does not conform to the EndNote X2, X3, X4 or X5 XML schema.

If you are reading this post, it is just possible that you are using Nvivo from QSR and trying to work out why you can’t import your references after receiving this error:

Nvivo 10 EndNote XML Import Error
The xml file you selected to import does not conform to the EndNote X2, X3, X4 or X5 XML schema.

For me this unhelpful error message was easily fixed. And the answer is not to do with an incompatibility between EndNote X6 and Nvivo 10 as I had originally thought (X6 xml works just as well as X5 with Nvivo 10). The answer is simply that not all references created with EndNote are equal. Just 1 of my 70 references was corrupt and causing Nvivo spit back the above error message at me.

So this is how I fixed my problem. First I exported just 1 of 70 references to an XML file from my EndNote library and tried to import it with Nvivo. Success!
Then I exported 35 of 70 to another xml file and attempted to import it – and so forth in increasing numbers until I hit my 1 bad EndNote reference. EndNote it seems was rejecting my 1 bad reference because it contained crazy cut-and-paste badness. See the whacky character in my cut and paste abstract (below)? Yep! That was the problem. Frustrating problem but simply fixed in the end by removing this bad character (doing this in EndNote didn’t work for me – so I needed to edit the XML file with a text editor).

So, if this post has helped you (I couldn’t find a good answer anywhere!) please take a moment to link back to this post or just comment and say thanks!

Bad Characters in EndNote reference can trip up Nvivo when imported as XML
Bad characters in EndNote reference can trip up Nvivo when imported as XML