now reads/writes 3-partition files

[asdcplib.git] / README

diff --git a/README b/README
index 6b248f041e98ddad5db62204484e5424d5a61786..dbd73fd3236fc239a8b45a7a7cb580e3f6a15710 100755 (executable)
--- a/README
+++ b/README
@@ -8,7 +8,7 @@ group DC-28.20.
 
 This work was originally funded by Digital Cinema
 Initiatives, LLC. Subsequent efforts have been funded by
-Deluxe Laboratories, Doremi Labs, and others.
+Deluxe Laboratories, Doremi Labs, CineCert, LLC. and others.
 
 **The asdcplib project is housed on SourceForge. The project
 home page is at http://sourceforge.net/projects/asdcplib.
@@ -20,9 +20,9 @@ The project used to depend upon the mxflib project. Because
 of the focus on covering the whole of the MXF spscifications,
 mxflib is considerably larger and more complex that what I
 require for this application. For this reason I have created
-a dedicated MXF interface that is now part of this library.
-Special thanks to Matt Beard and Oliver Morgan for their great
-work and support.
+a dedicated MXF implementation that is now part of this
+library. Special thanks to Matt Beard and Oliver Morgan for
+their great work and support.
 
 Thanks also to the members of the SMPTE DC-28.20 packaging
 ad-hoc group and the members of the MXF Interop Initiative
@@ -66,8 +66,7 @@ packages may or may not work depending upon the availability
 of standard POSIX shell commands. You will need gcc to rebuild
 the dep.make file.
 
-OpenSSL is required if you want to read and write encrypted
-AS-DCP files. See http://www.openssl.org
+OpenSSL is also required. See http://www.openssl.org
 
 If you are building on win32 or a unix with no OpenSSL library
 support, you will have to also obtain and build OpenSSL (I'm
@@ -84,26 +83,6 @@ I have tested this build on win32, Linux and Darwin platforms.
 Others may work as well.
 
 
-Build Versions
-
-There are two flavors of build: the default build and the
-"SMPTE_LABELS" build. Unless you are specifically  working on
-emerging SMPTE standards for D-Cinema content, you will certainly
-want the default build. If you are developing support for the MXF
-Interop Initiative standards, the default build is for you!
-
-If you are not aiming for MXF Interop and if you are working
-on developing support for the very latest versions of the SMPTE
-draft standards, then you want the SMPTE_LABELS build:
-
-  make SMPTE_LABELS=1
-
-NOTE: If you choose the SMPTE_LABELS build, you will be creating
-files that may not work on MXF Interop systems. In the case of
-encryption, incompatibility with MXF Interop is guaranteed! You
-have been warned!
-
-
 Documentation
 
 Currently, the documentation is mostly in AS_DCP.h. Read
@@ -113,8 +92,18 @@ examples. More detailed documentation will be written RSN.
 
 
 Change History
-2006.01.04 - full read-write
+2006.03.16 - bug fixes plus
+ o Removed SMPTE_LABELS compile-time option. The reader will now
+   silently accept either SMPTE or MXF Interop labels, the writer
+   can be instructed which to use at runtime. Default is Interop.
+ o Added an AIFF reader. Support is preliminary, it works with the
+   AIFF files I have on hand.
+ o More code refactoring. More to come.
+
+
+2006.03.09 - full read-write
  o Removed ASDCP_WITHOUT_OPENSSL compile-time option.
+ o Full read/write now working on new MXF library
 
 
 2005.00.00 - A New Hope