Ideas from FADGI meeting from Karl (NEDCC)

[knfleck]

Hello! Enjoyed the meeting. I'll write out my thoughts here:

1. My hope is to find a way to remove/rework unsupported chunks. In my case, Wavelab switches files to RF64's if they're longer than an hour in duration (2 gigs?) - even though it doesn't have to. I'm wondering if there's a way to nullify the RF64 data and, instead, replace it with blank space-keeping values in the file. (Is that how it works?) So we could replace the RF64 info with blank info - rather than removing that chunk entirely and risking damage/reordering of the file. (Please forgive me if I'm saying something wrong - I'm not great at computer-y stuff.)

2. My other thought was if there could be a bulk-populate the Origination Date and Origination Time fields in the core metadata from the file's timestamp. Right now, I have to right click on each individual file and select the "Set origination Date and Time to file creation timestamp" option. Like, if there was a way to do "Set origination Date and Time to file creation timestamp for all open files", that'd be cool. Or, maybe it could be automatically populated like the Date Created field in the technical metadata? Is that pulling from the timestamp, too?

Thanks!!!

[g-maxime]

1. The ds64 chunk (part of rf64) is specifically excluded from --delete-chunks as it’s considered an important chunk.
   For this specific use case, we could add an option to check if RF64 is required, and revert to RIFF otherwise.

2 . Currently, this is possible in the table view by selecting the entire OriginationDate or Time column, right-clicking, then "Set to file creation timestamp" However, this option isn’t available in the "PerFile" view.
A menu option and/or configuration setting for this would definitely be a good improvement.