Sonar exported Broadcast wav has incompatible bcst header

I'm trying to export a wav as type broadcast from the latest sonar version (Jamican Plain I believe).  When I move to my Mackie HDR, it complains that it can't import it.  When I look at the .wav file, I see there is a bcst tag section which has a header size that doesn't match the spec here (  According to the spec, the size should be 602.  This also matches the wav bst tag header section size when you export from the Mackie HDR.  Exporting from Sonar shows a size of 858, which is 256 bytes over.  Looking that section in a hex editor I see this it begins with this info.
 
41 3D 50 43 4D 2C ..A=PCM,
46 3D 34 38 30 30 30 2C F=48000,
57 3D 32 34 2C 4D 3D 6D W=24,M=m
6F 6E 6F 2C 54 3D 53 4F ono,T=SO
4E 41 52 20 50 6C 61 74 NAR Plat
69 6E 75 6D 20 4A 61 6D inum Jam
61 69 63 61 20 50 6C 61 aica Pla
69 6E 00 00 00 00 00 00 in.
 
Is this a newer version of bcst that you are using or is it a bug?
 
Given the Mackie HDR won't be updated, is there a way to make it write the old style header?
 
Thanks,
Paul

It appears the broadcast wave chunk has a variable sized text field at the end of it listing the track settings (which is what you are showing above).  So i don't think the size has anything to do with the compatibility, but that might not help you.  You may need to do some sort of conversion.

I determined 4 differences:

1. bext has extra Coding History with variable length
2. Fmt header size is 18, instead of 16 for Mackie
3. Mackie uses colons ":" to separate date, but Sonar uses dashes "-"
4. Sonar includes Junk section.

I was able to test and found out that only #1 and #2 above are significant.  When I manually edit the file and fix the Fmt header size (Sonar adds 2 00 bytes at the end), and then remove the Coding History, it works and can be imported.
 
@John, I don't think I'm exporting 64 bit BWF.  I choose Broadcast Wave from the dropdown, and I don't see another option form the export page.  Do you think it's possible to have Sonar revert it's behavior?  Or will I have to take @Matt's advice and build a tool to convert the file?
 
Paul