Gregorio,

I forget to say that parameter variables need to be uppercase. The 
example you supplied would be written thus:

<?xml version="1.0" encoding="UTF-8"?>
<conformance_point_document>
<File name="CUL-OR01-Gerhard-000101-pres.wav">
<Core>
<CodingHistory>A=ANALOGUE,M=mono,T=Studer810; Sn1234; 15 ips; open reel 
tape&#x0d;&#x0a;A=PCM,F=96000,W=24,M=mono,T=MytekADC96; 
Sn1234&#x0d;&#x0a;A=PCM,F=96000,W=24,M=mono,T=Wavelab; 
Sn1234&#x0d;&#x0a;</CodingHistory>
</Core>
</File>
</conformance_point_document>

with command line:

bwfmetaedit --in-core=CUL-OR01-Gerhard-000101-pres.xml 
CUL-OR01-Gerhard-000101-pres.wav


Best Wishes

Mike

On 25/01/2012 16:26, Mike Hirst wrote:
> CodingHistory is over-written other tags are unchanged
>
> On 25/01/2012 15:45, Gregorio Garcia Karman wrote:
>> Thanks Michael. Will that merge CodingHistory with existing<bext>
>> metadata?
>>
>> On 25.01.2012, at 14:21, Mike Hirst wrote:
>>
>>> It might be easier to put the data into XML before importing the data.
>>>
>>> Data from the file test.xml:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <conformance_point_document>
>>> <File name="test.wav">
>>> <Core>
>>> <CodingHistory>
>>> a=analog,m=mono,t=Studer810; Sn1234; 15 ips; open reel
>>> tape&#x0d;&#x0a;a=PCM,f=96000,W=24,m=mono,t=MytekADC96;
>>> Sn1234&#x0d;&#x0a;a=PCM,f=96000,W=24,m=mono,t=Wavelab;
>>> Sn1234</CodingHistory>
>>> </Core>
>>> </File>
>>> </conformance_point_document>
>>>
>>> imported into the file test.wav using the command:
>>>
>>> bwfmetaedit --in-core=test.xml test.wav
>>>
>>> gives results in accoradnce with EBU R98 1999
>>> (http://tech.ebu.ch/docs/r/r098.pdf)
>>>
>>> The same data can be imported from a plain text file via GUI.
>>>
>>>
>>> On 25/01/2012 12:15, Gregorio Garcia Karman wrote:
>>>> ...like this I meant:
>>>>
>>>> bwfmetaedit --History="a=analog,m=mono,t=Studer810; Sn1234; 15 ips;
>>>> open reel tape<br />a=PCM,f=96000,W=24,m=mono,t=MytekADC96;
>>>> Sn1234<br />a=PCM,f=96000,W=24,m=mono,t=Wavelab; Sn1234"
>>>> CUL-OR01-Gerhard-000101-pres.wav
>>>>
>>>>
>>>> On 25.01.2012, at 10:51, Gregorio Garcia Karman wrote:
>>>>
>>>>> Dear list,
>>>>>
>>>>> ...thanks for the useful and hilarious responses!
>>>>>
>>>>> Here a more technical question regarding bwfmetaedit. I am trying
>>>>> to automate the writing of metadata to a set preservation master
>>>>> files using FADGI BWF metaedit's command line interface. This works
>>>>> well, but I am having difficulties writing a multiline content to
>>>>> the<bext> field<CodingHistory>. I am trying to do something like this:
>>>>>
>>>>>
>>>>> but the<br /> does not get interpreted correctly. Until now I have
>>>>> tried a number of alternatives from OSX's bash with no sucess.
>>>>> Suggestions?
>>>>>
>>>>>
>>>>> Gregorio Garcia Karman
>>>>> +44 (0) 7532 127 645
>>>>> [log in to unmask]
>>>>
>>>
>>> --
>>> Mike Hirst
>>> Managing Director
>>> DAS-360°
>>> 16 Ocean View
>>> Whitley Bay
>>> Tyne& Wear
>>> NE26 1AL
>>>
>>> tel: 0191 289 3186
>>> email: [log in to unmask]
>>> web: http://www.das360.net
>>
>

-- 
Mike Hirst
Managing Director
DAS-360°
16 Ocean View
Whitley Bay
Tyne & Wear
NE26 1AL

tel: 0191 289 3186
email: [log in to unmask]
web: http://www.das360.net