Unitiserve not support Broadcast WAV

How about converting them to flac?  Much easier to tag them, and you can have the uServe transcode them back to wav for playback if you desire.

Slightly  confused by your posting, Naim can read WAV files, albeit it can't recognize   any of the embedded  metadata chunks in the files, but it can't read BWF files.

So you can convert your BWF (broadcast wave files) to WAV (wave) files, Naim can then see them but not see the embedded WAV file metadata, or convert to FLAC as suggested above where Naim can see the metadata.

Simon

BWF wave files tend to be mp2 encoded files with a wave header.

Problem Solved: I found a program that edits the metadata in a BWF:

http://sourceforge.net/projects/bwfmetaedit/

No converting at all, woo hoo!

I only needed to remove the originator "Sound Devices: 722 S#471007317018"

Now the files show up in the Unitiserve

This topic is closed with solved!

Interesting you post prompted me to look into this  - yes of course Naim use extended header WAV (to support hidef etc) and so there is no difference between WAV and BWF files apart from BWF has some specific extra chunks in the file - namely

• Original Bext chunk (Broadcast Extension - 'bext')
• iXML chunk ('iXML')
• Quality chunk ('qlty')
• MPEG audio extension chunk ('mext')
• Peak Envelope chunk ('levl')
• link chunk ('link')
• axml chunk ('axml')

https://tech.ebu.ch/docs/tech/tech3285.pdf

Theoretically if the BWF file has a .WAV extension then Naim should be able to read the file.

Clearly it didn't with you, so Naim must have tripped up on reading one of the chunks the and reading your description it looks like it was the Bext chunk .,, which according to the original WAV standard should have been skipped if not understood.. unless of course there was another error that your file editor fixed.

Quite interesting..

Simon

For you Simon: I took screen shots of the external HDD plugged into my laptop. Then I took screen shots of the Naim Desktop Client with the HDD plugged in the serve. These are all with unedited BWF's.

This is what happened when I tried to click "Unknown"

Thanks, unfortunately this doesn't conclusively show us which chunk Naim is tripping up over, but I still suspect the Bext chunk.

Simon

The screen shot shows the tag "originator" being the culprit.

I guess Simon the "chunks" you talk about I don't understand at all.

Hi, chunk is the term used in a RIFF structure. RIFF or Resource Interchange File Format is the file structure used in WAV and AIFF files amongst others. The RIFF consists of segments of data consisting of an identifier followed by a length of the payload followed by the payload itself - these segments are called chunks. The idea, similar to that used in many higher level data network protocols, allows the parser inspect the identifier, if it doesn't recognize it, it then simply fast forwards by the length to the next chunk. Therefore an unrecognised chunk can be skipped and the remaining chunks can then be examined In turn.

This technique aids interoperability and allows for private extensions with out impeding the parser to interpret the essential chunks.

However with your BWF files, parsing and skipping the BWF Bext  chunk clearly didn't work with your Naim parser for what ever reason. The Originator is a defined char string within the Bext chunk structure payload.

Simon