BWF offset broken when consolidating track on certain project (v7.25)

[axeman]

Hi,

I do a lot of work with a band mate who mixes in Pro Tools and we are always sending consolidated and renders tracks back and forth. I've been performing my consolidation/rendering based on time selection for years--choosing WAV files and keeping the default "Write BWF (bext) chunk" option selected. I've never had an issue with the resulting offset, but recently recorded drum tracks for two of our new songs and consolidating every newly recorded track--on both projects--with the resulting timing offset for the files showing 0 instead of their correct offset positions. Here's an example BWF header from the Source properties of one of these tracks when imported back into REAPER:

BWF tags:
Originator: REAPER
TimeReference: 0

Oddly, when I loaded up an older project and did a similar track consolidation, it worked. Example of the BWF tags in this one for your reference:

BWF tags:
Originator: REAPER
TimeReference: 4160001

This seems really odd, as older projects seem to consolidate in REAPER 7.25 OK (and this new issue initially showed up before 7.25 was released, though I can't remember the exact recent version I used then).

I tried searching for information that might help, but came up blank. As such, I'm assuming this is likely a bug--and one that may have been recently introduced (though I can't tell why some old projects consolidate with the proper BWF offset header and some change them to 0 when they're supposed to be higher). Any help would be greatly appreciated. Thanks a lot. -Alan

[axeman]

Hi again,

I just consolidated four tracks to WAVE files with the default "Write BWF (bext) chunk" selected, in REAPER v7.33, and experienced the exact same problem with two of the files erroneously containing an offset value of 0. (All were consolidated at the same time in the exact same time range and the other two resulting WAVE files had the correct offset value.)

I really hope that someone can find and fix the bug here.

Thanks and best wishes,


Alan

[schwa]

Are you able to provide a very small project that demonstrates the problem? Specifically, a track that does not generate a consolidated file with the correct BWF offset?

[axeman]

Originally Posted by schwa

Are you able to provide a very small project that demonstrates the problem? Specifically, a track that does not generate a consolidated file with the correct BWF offset?

Thanks very much for your help. Let me try saving a new instance of the same project that has all tracks aside from these four deleted and see if the issue can be reproduced there. If so, may I please ask how to submit the corresponding REAPER project folder?

Best wishes and thanks again for your help,


Alan

[schwa]

You can email to support at cockos, thanks. We would need the associated media as well, not just the .rpp file. The smaller the project, the better, so it's helpful if you can remove all FX as well.

[axeman]

Originally Posted by schwa

You can email to support at cockos, thanks. We would need the associated media as well, not just the .rpp file. The smaller the project, the better, so it's helpful if you can remove all FX as well.

After I'm sure that the reduced instance of the project (which I'll save to a new folder with media copied) is reproducing the problem, I'll ZIP up that new folder and send it along as per your guidance. Thanks again. -Alan

[axeman]

Hi again Schwa,

I was able to delete all other tracks in the existing project and crop every take of the four percussion tracks I consolidated yesterday--then cleaning the project folder of all remaining media and removing the only effect I had (on the master) as well. I performed the exact same consolidation process on the four tracks in question and, just as occurred yesterday, the two shaker tracks ended up without a proper "offset" value in the BWF header (defaulting to 0) while the two cajon tracks consolidated with the correct "offset" value. The consolidation was done in one single action, using time selection, selected tracks, and keeping the default "Write BWF (bext) chunk" option selected.

The resulting folder (including a subfolder labeled "consolidated" with the consolidated tracks) ended up at 51 MB in size so I had to send it via WeTransfer. I hope this helps and, again, really appreciate your assistance in finding (and, hopefully, remedying) this issue.

Best wishes and thanks again for your help. -Alan

[schwa]

OK, thanks for sending the project. This should be fixed in the next pre-release build.

[axeman]

Originally Posted by schwa

OK, thanks for sending the project. This should be fixed in the next pre-release build.

Great, thanks a lot! I'm happy to hear that you were able to see the issue and have it in queue for a fix. (We use this workflow a lot in my band, Advent, so it will be great to have everything working properly once again.)

Cheers,


Alan