Announcing OpenCORE 2.02 release

by GregS » Sun, 15 Mar 2009 11:43:21 GMT


Sponsored Links
 OpenCORE 2.02 has been released and is now available on the master
branch.  There is a git tag "v2.02" marking the version.  Below is a
summary
of the changes since the previous release (OpenCORE 2.1 = 2.01 in the
new nomenclature described below).  The same information is also now
included in the ChangeLog file in the top-level directory of the
OpenCORE code.

********
   There is minor version number nomenclature change where the
   minor version is now two digits.  So the previous releases
   in the new nomenclature are 2.00 (2.0) and 2.01 (2.1).  The
   new release is 2.02, which is a minor version increment beyond
   the previous release.
********

New Features
- AMR-WB support added to the OMX encoder node so that it can utilize
  an OMX AMR-WB encoder component if it is part of the OMX core.
- Buffer allocator mechanism allowing the Media I/O components to
  supply buffers to the OMX decoders.  This method is especially
useful
  as an alternative way to allocate video buffers.  Details can be
  found in the new document "Guide to Supplying Decoder Buffers from
  the MIO Component" in the file
mio_decoder_buffer_allocation_guide.pdf
  in the top-level doc directory.

Improvements
- Resolution of Valgrind and static analysis warnings in player and
author
- Improvements in support for .mov files in MP4 FF Parser(relaxed some
checks).
- Modified OMX encoder node to allow setting the AMR bitrate
  based on an extension interface value.
- Fix inconsistencies in OSCL find method related to inclusion of the
  directory name with the filename.
- Improvement in PVMFInfoErrorHandlingComplete in the player datapath
- Refactor of the Protocol Engine node to support a plugin
architecture.
  This improves extensibility of the module for new features in the
future.
- Introduce QueryInterfaceSync in PVMFNodeInterface and "all" metadata
key
- AMR NB and WB have conflicting meaning for frame_type and mode
elements
- Change the default settings related to caching for Oscl_File when
  using PVFile within the fileformat parsers.
- Replace test.mp4 with interop clip
- Update of tests for support for progressive download of AMR
- OMX Khronos header files (Omx_Core.h, Omx_Component.h)
capitalization
  changed to match that from the Khronos (previously they were all
lowercase).
- Updated MIO Developer's Guide in the top-level doc directory.

Bugs Fixed
- Memory leak when running GCF TC212 (2way-related)
- MediaClockConverter divided by zero caused by timescale 0
- MP4 composer node destructor memory corruption fixed.
- Fix for intermittent crash in player engine TC 105
- OMX dec node did not reset all the internal state during
  Reset processing.



--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. strange LVL calback errors

I have added email of my device in "Test accounts" and testing LVL by
setting values in Test response box in Developer Console.

Sometimes in LicenseValidator.verify(PublicKey publicKey, int
responseCode, String signedData, String signature) I get signedData ==
null and signature == null.

In Logcat I see:
10-13 01:41:03.758: ERROR/vending(4738):
com.android.vending.AsynchRequestRunner$1.runRequestRetryingFailure():
Got ApiException from async request: Got unexpected HTTP status code:
503

And sometimes I see "Check timed out" in logcat and application don't
allow me to use it. It is ResultListener.mOnTimeout runnable launched
by service. When I press Retry (i.e. call checkAccess(...) again)
several times (and sometimes - many times!) , it finally works (calls
allow()).

It seems that server sometimes is out of service. And not all
developers have implemented LVL calls in their apps for now. What will
be next - it will be continuosly out of service?

Currently we have tons of letters from customers keep saying "won't
download!!!". Yes, it's because of market server is out of service.
But of course we're to blame - from customer's point of view. So I
suppose once we add LVL in our apps we'll have tons of letters from
saying "won't let me to launch!!!" :) Am I right?

Google guys, can you please explane such problems with LVL? I just
can't decide - should I add LVL check or leave all things as is...

-- 

2. wpa_cli not found

I'm running an Android 2.2 emulator and want to play with wifi stuff
but there is no /system/bin/wpa_cli. Do I need to install something
else to get it?

Ted

-- 

3. Open Max Test App documents

4. Buffering problem while reading an h264 video (using HTTP protocol)

5. PCMDMAMISSED 3

6. SurfaceView problem

7. Enumerating certificates