Look inside the XML - cachRec ?

[Craig Seeman]

I'd thought some might want to see what's in the XML from the source.

<?xml version="1.0" encoding="UTF-8"?>
<NonRealTimeMeta xmlns="urn:schemas-professionalDisc:nonRealTimeMeta:ver.1.20" xmlns:lib="urn:schemas-professionalDisc:lib:ver.1.20" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lastUpdate="2007-12-19T23:42:57-05:00">
<TargetMaterial umidRef="060A2B340101010501010D4313000000BA234032544405C50800460202280328"/>
<Duration value="521"/>
<LtcChangeTable tcFps="30" halfStep="false">
<LtcChange frameCount="0" value="12010000" status="increment"/>
<LtcChange frameCount="520" value="22180000" status="end"/>
</LtcChangeTable>
<CreationDate value="2007-12-19T23:42:39-05:00"/>
<TypicalUbit value="0000000000000000"/>
<BodyUmidBasicChangeTable>
<BodyUmidBasicChange frameCount="0" value="060A2B340101010501010D4313000000BA234032544405C50800460202280328" status="start"/>
</BodyUmidBasicChangeTable>
<KlvPacketTable>
<KlvPacket key="060E2B34010101050301020A02000000" frameCount="0" lengthValue="095F5265635374617274" status="spot"/>
</KlvPacketTable>
<VideoFormat>
<VideoRecPort port="DIRECT"/>
<VideoFrame videoCodec="MPEG2HD35_1920_1080_MP@HL" captureFps="29.97p" recFps="29.97" formatFps="29.97p"/>
<VideoLayout pixel="1920" numOfVerticalLine="1080" aspectRatio="16:9"/>
</VideoFormat>
<AudioFormat numOfChannel="2">
<AudioRecPort port="DIRECT" audioCodec="LPCM16" trackDst="CH1"/>
<AudioRecPort port="DIRECT" audioCodec="LPCM16" trackDst="CH2"/>
</AudioFormat>
<Device manufacturer="Sony" modelName="PMW-EX1" serialNo="0100808">
</Device>
<Lens modelName="XT14X5.8"/>
<RecordingMode type="normal" cacheRec="false"/>
</NonRealTimeMeta>

[Craig Seeman]

<?xml version="1.0" encoding="UTF-8"?>
<NonRealTimeMeta xmlns="urn:schemas-professionalDisc:nonRealTimeMeta:ver.1.20" xmlns:lib="urn:schemas-professionalDisc:lib:ver.1.20" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lastUpdate="2007-12-20T01:23:13-05:00">
<TargetMaterial umidRef="060A2B340101010501010D4313000000749F1344544405DC0800460202280328"/>
<Duration value="16"/>
<LtcChangeTable tcFps="30" halfStep="false">
<LtcChange frameCount="0" value="15570000" status="increment"/>
<LtcChange frameCount="15" value="00580000" status="end"/>
</LtcChangeTable>
<CreationDate value="2007-12-20T01:22:55-05:00"/>
<TypicalUbit value="0000000020120720"/>
<BodyUmidBasicChangeTable>
<BodyUmidBasicChange frameCount="0" value="060A2B340101010501010D4313000000749F1344544405DC0800460202280328" status="start"/>
</BodyUmidBasicChangeTable>
<KlvPacketTable>
<KlvPacket key="060E2B34010101050301020A02000000" frameCount="0" lengthValue="095F5265635374617274" status="spot"/>
</KlvPacketTable>
<VideoFormat>
<VideoRecPort port="DIRECT"/>
<VideoFrame videoCodec="MPEG2HD35_1920_1080_MP@HL" captureFps="01.00p" recFps="29.97" formatFps="29.97p"/>
<VideoLayout pixel="1920" numOfVerticalLine="1080" aspectRatio="16:9"/>
</VideoFormat>
<AudioFormat numOfChannel="2">
<AudioRecPort port="OTHERS" audioCodec="LPCM16" trackDst="CH1"/>
<AudioRecPort port="OTHERS" audioCodec="LPCM16" trackDst="CH2"/>
</AudioFormat>
<Device manufacturer="Sony" modelName="PMW-EX1" serialNo="0100808">
</Device>
<Lens modelName="XT14X5.8"/>
<RecordingMode type="slowAndQuickMotion" cacheRec="false"/>
</NonRealTimeMeta>

[Craig Seeman]

The first is from 1080p30.
<VideoFrame videoCodec="MPEG2HD35_1920_1080_MP@HL" captureFps="29.97p" recFps="29.97" formatFps="29.97p"/>
<RecordingMode type="normal" cacheRec="false"/>

The second is from 1080 at 1fps slow and quick mode.
<VideoFrame videoCodec="MPEG2HD35_1920_1080_MP@HL" captureFps="01.00p" recFps="29.97" formatFps="29.97p"/>
<RecordingMode type="slowAndQuickMotion" cacheRec="false"/>

The interesting thing is there seems to be an allusion to cacheRec which is set to false.
Makes you wonder.

[Jiri Bakala]

Fascinating read... :-)


No, for real, and what are we looking at here?

[Craig Seeman]

XML file which describes the clip inside the BPAV folder. Each clip (.MP4) has an associated .SMI, .PPN, .BIM, XML file. The XML files has all sorts of info describing the clip. Data.

I'm wondering what that cacheRec really is. Nothing I've tried yet changes it from false to true.

I have a fantasy that Sony was/is looking at a cache record function that will buffer video before one hits record. I could be mistaken though. I'm wondering if anyone has found something that enables the setting (meaning it's something other than what I'm thinking).

Originally Posted by Jiri Bakala

Fascinating read... :-)


No, for real, and what are we looking at here?

[Jason Bodnar]

Craig, That would be killer if they can enable this feature with an upcoming firmware update.

[Greg Boston]

Originally Posted by Craig Seeman

XML file which describes the clip inside the BPAV folder. Each clip (.MP4) has an associated .SMI, .PPN, .BIM, XML file. The XML files has all sorts of info describing the clip. Data.

I'm wondering what that cacheRec really is. Nothing I've tried yet changes it from false to true.

I have a fantasy that Sony was/is looking at a cache record function that will buffer video before one hits record. I could be mistaken though. I'm wondering if anyone has found something that enables the setting (meaning it's something other than what I'm thinking).

That's what it is. The XDCAM HD cameras didn't have it with the early firmware, but it was added later. The XDCAM SD cameras have it also.

So you may get it later on in a firmware update.

-gb-

[Craig Seeman]

Thanks Greg. A while back a few Sony reps were saying cache recording would be enabled in a firmware update but later they (ones that I talked to) said they wouldn't promise such a feature would be implemented. It made me think that they ran into an issue. The early comments said it would be two seconds. I still hope for it though.

[Greg Boston]

Originally Posted by Craig Seeman

Thanks Greg. A while back a few Sony reps were saying cache recording would be enabled in a firmware update but later they (ones that I talked to) said they wouldn't promise such a feature would be implemented. It made me think that they ran into an issue. The early comments said it would be two seconds. I still hope for it though.

I think what happens is after the product release, the programmers keep looking at ways to optimize the code, thus allowing more functionality to be added without breaking everything else in the process. Just like with graphics cards, the first run of the drivers are usually followed by more optimized drivers later on, translating into better performance.

They are still planning more firmware updates to the F350, but the timeline isn't cast in stone.

-gb-