Monday, November 28, 2011

Performance and Complexity Comparison between H.265/HEVC and H.264

HEVC Test Model under Consideration (TMuC) serves as a starting point for definition of the new video coding standard. The current version is HM-4.1-dev.

An article "Towards high efficiency video coding: Subjective evaluation of potential coding technologies" pointed out:

"The TMuC has similarities to the H.264/MPEG-4 AVC standard, including block-based intra / inter prediction, block transform and entropy coding. New features include increased prediction flexibility, more sophisticated interpolation filters, a wider range of block sizes and new entropy coding schemes. Twice the compression efficiency of H.264/MPEG-4 AVC is expected to be achieved, at the expense of a considerable increase in computational complexity. The performance of the coding algorithm resulting from this integration step will be analyzed by means of formal subjective quality assessment in a next subjective test campaign."

The article "High Performance, Low Complexity Video Coding and the Emerging HEVC Standard" describes a low complexity video codec with high coding efficiency. It was proposed to the high efficiency video coding (HEVC) standardization effort of moving picture experts group and video coding experts group, and has been partially adopted into the initial HEVC test model under consideration design. The proposal utilizes a quadtree-based coding structure with support for macroblocks of size 64 × 64, 32 × 32, and 16 × 16 pixels.
  • Entropy coding is performed using a low complexity variable length coding scheme with improved context adaptation compared to the context adaptive variable length coding design in H.264/AVC. 
  • The proposal's interpolation and deblocking filter designs improve coding efficiency, yet have low complexity. 
  • Average interpolation complexity is less than that of H.264/AVC due to the 1-D directional interpolation filters. 
  • Memory bandwidth for motion compensation is lower than H.264/AVC. This is because motion partitions smaller than 8 × 8 are not used. 
  • Interpolation complexity for B pictures is significantly lower in the proposal than in H.264/AVC, as the SKIP and DIRECT modes use integer motion vectors. Using motion vectors with integer pixel accuracy implies that reconstruction of a SKIP/DIRECT block can be done by copying pixels from one location in memory to another location, instead of applying the 6-tap interpolation filter. 
  • The deblocking filter has significantly lower computational complexity. This is mainly because a much lower number of block edges are filtered, and the filter has simpler logic for enabling/disabling the filter on an edge. In addition, filtering can be performed in parallel first for each of the vertical edges and then for each of the horizontal edges, which is not possible for H.264/AVC. 
  • VLC (de)coding of coefficients is simpler than H.264/AVC CAVLC coefficient (de)coding. In particular, CAVLC relies on decoding a large number of syntax elements (e.g., coeff−token, trailing−ones−sign−flag, level−prefix, level−suffix, total−zeros, and run−before). Also, the VLC decoding uses significantly fewer syntax elements, and requires less conditional branches (run/level/sign in run mode, and level/sign in level mode). 
Samuelsson at el. proposed a method to for "Simplification of Intra Prediction Mode" for HEVC. The result shows that this processing is adaptive to the content of the video, and results in a reduction in the computational complexity of the prediction process by approximately 50%.

Using NDK to Call C code from Android Apps

Android NDK (Native Development Kit) allows working with native C code using a shared C library. It includes the entire toolchain needed to build for your target platform (ARM). Native C code accessible via JNI still runs inside the Dalvik VM, and as such is subject to the same life-cycle rules that any Android application lives by. The advantage of writing parts of your app code in native language is presumably speed in certain cases.



See more at Marko Gargenta's article.

Monday, November 21, 2011

DM8168 EVM for $999


 
Spectrum Digital is now shipping the DM816x/C6A816x/AM389x Standalone EVM Baseboard. This is the processor board which makes up part of the full development kit offered by TI. This CPU module allows developers to get additional platforms in a cost effective manner for software developers.This module, # 702391, is being offered in North America at a quantity one price of $999.00. 

Friday, November 18, 2011

DM6467 ARM9 Trouble Writing Memory Block at 0x1c40900


When connecting to DM6467 from CCS (3.3.82.13), using XDS510PP Plus (Rev A) and the DM6467t Gel file from Spectrumdigital, we may see

"Trouble Writing Memory Block at 0x1c40900 on Page 0 of Length 0x4: Error 0x80002002/..."

The problem is due to "It is possible that when PLL is being programmed you loose RTCK while PLL is switching over.  The RTCK will also become much slower as it is slaved to the device core clock. It may only work if you are using an external adaptive clocking adapter to deal the RTCK issue. Aside of this, you will need to configure the PP+ via SdConfig(Ex) to uncheck disable polling and set the port speed to 100.  This will force the emulator to poll for emulator command completion and the 100 is the max retry loop count. " The fix is as follows.


Thursday, November 17, 2011

Qualcomm to Lose HTC to Nvidia Tegra 3?

Like in recently announced Eee Pad Transformer Prime, the first tablet to feature Nvidia's new Tegra 3 quad-core processor, has attracted attention, Tegra 3 quad-core processor seems that it will be adapted by more phones and tablet. Desire Athow wrote:

HTC will apparently break the exclusivity of Qualcomm by adopting the penta-core Nvidia Tegra 3 chipset to power a new handset, the Edge, that is set to be launched next year at MWC.

According to Monica Chen and Joseph Tsai from Digitimes, the phone will launch either in March or April and will come with Nvidia's chipset, which would be a blow to Qualcomm who may lose both HTC and Sony Ericsson as exclusive partners in a single year. 

In addition, Microsoft has also confirmed that ST-Ericsson will also start producing chips for Windows Phone handsets ,heralding the end of the monopoly Qualcomm had on the platform.
Samsung Electronics, Motorola and LG have also adopted the Tegra 3 for their handsets and Asus has already shipped the first tablet based on the chipset , the Transformer Prime.
The new Tegra 3 adopts a similar strategy as ARM's big.LITTLE or TI's OMAP4, with smaller CPU(s) taking over from big ones for mundane and light tasks.
Nvidia says that the system on chip has three times the graphics performance of its predecessor - thanks to 12 GPU cores - while consuming almost two thirds less power than the Tegra 2.


Read more: http://www.itproportal.com/2011/11/14/qualcomm-lose-htc-nvidia-tegra-3/#ixzz1dyIrkEa3

Wednesday, November 16, 2011

Eee Pad Transformer TF101 Android 3.2.1 Root and adb shell

  1. Download Asus Transformer NVFlash Stock 3.2 Recovery Roms from tabletroms.com; The latest version is the 3.2 Build of 8.6.5.13 which is the same as the one in Asus website;
  2. NV flash the ROM with following the instruction in tabletroms.com;
  3. Download Universal root toolkit v7.1 from xda-developers.com;
  4. Backup and root it;
  5. If "adb devices" returns nothing, you may unplug the USB cable and try to update the device driver using the USB driver in the transformer 3.1 rootkit.  If sometime SU can't not be installed due to ADB path problem, may also try the transformer 3.1 rootkit. However, if your adb path is set in the Windows environment, you may also need to delete the adb.exe in the tool kit;
  6. Use Root Check Pro to check if the transformer is rooted.

Sunday, November 13, 2011

HTML5 and Adobe Flash's Failures

Since Apple refused to accept Flash and Windows 8 Phone and tablet will not support Flash, and Adobe want to focus on HTML5 development, Adobe abandons mobile Flash development.

Adobe Flash logo
Flash Video is a container file format used to deliver video over the Internet using Adobe Flash Player versions 6–11. Flash Video content may also be embedded within SWF files. There are two different video file formats known as Flash Video: FLV and F4V. The audio and video data within FLV files are encoded in the same way as they are within SWF files. Flash Video FLV files usually contain material encoded with codecs following VP6 video compression formats. The most recent public releases of Flash Player also support H.264 video and HE-AAC audio.

Today David Murphy reported "Who's to Blame for Adobe Flash's Failures?" in pcmag.com. In his report, he referred to Cera Technology CEO Michael Mace's words "The root causes of the Flash failure should blame to a fundamental misreading of the mobile market, and to short-term revenue goals that were more important than long-term strategy at both Macromedia and Adobe. The full Flash player had been designed for PCs; it was too fat to run well on a smartphone." ...

Currently HTML5 Video Player is an opt-in trial for YouTube. It supports browsers that support both the video tag in HTML5 and either the h.264 video codec or the WebM format (with VP8 codec).

Followers

About Me

My photo
HD Multimedia Technology player