FLAC is lossless compression. FLAC itself is compatible with the bit depth and sample rates of your studio masters. However, those listening won't always have sound hardware that are compatible with that bit depth and sample rate. (This problem has nothing to do with FLAC itself.)
If you want guaranteed compatibility, distribute FLAC at 44.1kHz 16-bit, ...
I haven't got around to creating IRs with 7 yet, but the IRs I created with 6 (with pictures) transferred just fine. Essentially, you just put pictures in a folder with the IRs:
"---|" = Folder
---| My IR
------ My IR.jpg
------| My IR Audio
--------- My IR Stereo.sd2
--------- My IR Mono.sd2
Structuring your IRs/images in folders like this should ...
I think for sound design elements (very basic things like a low thud, tool clutter, cork pop) it is good to give files a rudimentary searchable name. For finished sound effects with many elements you might want to add terms to the name or give it tags. Personally I would love to be independent of metadata. My library is still a work in progress. The most ...
Use ffmpeg and the metadata framework. Documentation can be found at: http://ffmpeg.org/ffmpeg-formats.html#Metadata-1
There is also a node package available for manipulation of metadata:
Although it seems that it doesn't solve the OP issue, there's a thread on Kid3 discussion forum that is titled :
Tagging of WAV issue - Music players are unable to read the tags of WAV
Here's an excerpt :
Support for RIFF INFO chunks in WAV files seems to be more common than ID3v2 tags, so you should try if RIFF INFO works with your
player. Such ...
I'm not familiar with the applications you mention, but the standard way to add metadata is to add a BWF header and keep the .WAV file extension. Applications that understand BWF will use the header; those that don't will ignore it.
There's no reason you couldn't add a JUNK header or any other defined section or perhaps link it to a separate database by ...