(03-09-2020, 04:02 AM)Zubersoft Wrote: I've added code to strip the BOMs from UTF-8 or UTF-16 files. My code already handled those encodings correctly, but didn't handle the BOM which messed up the identification of the columns in the first line. The Windows 10 manual is up-to-date as far as the allowable fields.That's great!! Thanks! I'm sure we've saved someone else a miserable and unproductive Saturday! Is there any MSP field other than Tempo that can accept only a specific data type (.e.g. numeric in the case of Tempo is the only one I see in the manual). I tried to use that field for a combination of numeric (e.g., 120) and text (e.g., Slowly), shoving them together with a | [bar] separator. MSP rejected all data in that field, including the 000 I had inserted to the left of the bar for songs that did not have a numeric tempo specified.
Thanks,
Mike
P.S. For future readers, I presume you meant UTF-8 or UTF-16.