This thread is an example of one that really got off topic. I never really did get any comments on my original question relating to the format of meta-data within NBTV wave files to allow identification of the actual NBTV format the audio represents.
With the advent of new formats, e.g. time-multiplexed colour, 128-line
![Wink ;-)](./images/smilies/icon_wink.gif)
, etc, I think it is becoming even more important to decide on a standard.
Even if you only use mechanical monitors that have no use or knowledge of this meta-data, in a few years time, when you come to browse through your library of NBTV video on your PC you may regret not being able to easily determine what video format they are in.
Those of you who have played around with my OmniNBTV utility may have noticed that it can automatically recognise the format of the items it creates, whereas, items imported from an external source result in it having to ask the user to specify the format. The app recognises it's own material because it adds in an "nbtv" RIFF chunk (for those who are interested but don't know what the hell I am writing about, I recommend at least a quick look at the BWF document I have a link to in my original post).
The format of this chunk is:
<chunk>
<chunk>
<nbtv>
<reserved>
where,
<chunk> = 'n','b','t','v'
<chunk> = 8
<nbtv> = a 32 bit number representing a format (1 = NBTVA standard)
<reserved> a 32 bit number for future proofing. i.e. it can extend the size of the chunk to include extra data.
Keep in mind that wave files are RIFF files, and RIFF files were designed for this kind of use so adding this data will have no detrimental effect on any applications that use wave files - it is industry standard - those applications that don't use this information simply ignore it.
Note also that chunks may be added to the end of RIFF files so existing items can be easily modified to include this chunk if necessary.
I have added this chunk as an interim measure in the absence of other suggestions but it is, of course, restricted to items OmniNBTV has created only so it is not too late to completely change the format, or move the information into a BWF chunk for even further industry standardisation (i.e. many wave editors allow the inspection of BWF data). Now is the time for input.
I really believe that the addition of this information will eventually be of great use in the exchange of NBTV material via wave files between interested parties and I especially recommend that members creating formats and software applications at least have a look at this method and how they might incorporate it into their own designs.