I’m working in Wavelab Pro 9 and with some files, I noticed a r64m chunk in several BWF file that I recorded. I understand there are options to automatically turn a standard BWF into an RF64 if the file reaches 2GB (even though standard BWF can go up to 4GB). The client I’m working with does not want RF64 files so I unchecked that option that I mentioned.
I opened up some of the files that I produced in our metadata editing program (BWFMetaedit) and noticed an “r64m” chunk in the file - even though it is not an RF64 file.
To me, it seems like some extra data that’s embedded in case you do intend to automatically turn it into a RF64? Maybe it’s a bug?
The client does not want any extraneous data in their files so if there’s a way to remove that information, or if there’s some setting that I could change so that it doesn’t generate an r64m chunk, that’d be great. Also, I realize I’m working with an old version - has anyone noticed this if you’re working with a newer version?
I just tried something with some test audio and found something interesting. And I had the RF64 option unchecked the whole time.
I pulled this sample audio into BWFMetaedit (open source / free metadata editor) and it did not show the r64m chunk. Then, I opened this file in Wavelab and saved it with a marker. Looks like the marker data is saved in the “cue” chunk. But when I opened the file in BFWMetaedit again (with the new marker data) it shows the r64m. Maybe there’s some connection between the data in the cue chunk and this r64m chunk?