#1 Bugs in TapeDescriptor object

[David Bertrand]

These bugs were noticed while importing an EDL2AAF
built AAF file.

BigBob.aaf included.

When reading a TapeDescriptor, the following functions
returns flunky results:

GetTapeLength() returns 3435973836
GetSignalType() returns -858993460
GetTapeFormat() returns -858993460
GetTapeManufacturer() returns 'YYYYYYYYYYY'...
GetTapeModel() returns 'YYYYYYYYYYY'...

No error are returned but buffer/value are filled with
junk. Please take note that GetTapeManufacturerLen &
GetTapeModelLen give the correct length and could be
used to prevent this situation but a normal behavior
should throw an error or returns an empty buffer.

You should also note that EDL2AAF does not call
their 'Set' conterparts.

David Bertrand, software developer
Post Impressions

[David Bertrand]

AAF Sample

[Brad Gilmer]

Logged In: YES
user_id=197466

David,
I am going to ask Simon Carter to look into this. Brad

[Phil Tudor]

Logged In: YES
user_id=162067

This was resolved at this Barcelona DevCon - it's not a bug.

For _optional_ properties that are not present (such as
this case), the GetX method of the SDK returns HRESULT
AAFRESULT_PROP_NOT_PRESENT and leaves the argument
unchanged.

Thanks to Oliver & James for tracking this down.

Phil