I have a trio a midi files which, when imported to NWC 1.52 consistently produce a GPF. They play on the windows media player perfectly well. Can any one give a plausibel reason for this?
Give us the URL where you got the midi files, and we can try it ourselves. All three crash?
Thanks for your interest. The URL's are http://midiworld.com/mid/byrd/wbfan1.mid and wbfan2, wbfan3 respectively
I just went three-for-three on these files. I downloaded them, and then one by one imported them into the 32-bit edition of NWC version 1.52 without incident. Perhaps you can be more specific about
- what options are set,
- where the GPF occurs,
- your system configuration (perhaps you do not have enough memory, for example),
- where in the import process the GPF takes place (do you go through the wizard interface, for example).
I am using the 16 bit version running under windows 3.11. I use the import wizard. In each file the import bar "stalls" at the first staff reporting a GPF in module NWC.EXE at 0024:5CBA on each of the three files each time I attempt to import. I have not seen anything similar on any other imported midi file (yet)!
Just to confirm,
I tried loading this midi file on 16 bit NWC and also got the same GPF
Richard
We confirm that the GPF occurs when running in the 16-bit version. We will diagnose the issue and correct it in the next release.
We do not yet know the reason why, but you can work around this problem by disabling the "Detect Compound Time" option during the import operation. Once unchecked, the files should import normally.
OK. We have diagnosed the problem (it does have to do with the compound time techniques in the 16-bit edition of NWC). It is fixed for the next maintenance release (we are currently on version 1.52).
This is fixed in version 1.52a, available now.