News Stories

Sony to release Full HD 3D Handycam

1.18.2011

Sony has announced the HDR-TD10, a 3D Handycam that can take full high-definition 3D video. This model is for release in April 2011.

This 3D Handycam has two wide-angle G-Lenses with a focal length of 29.8 mm, two backside-illuminated Exmor R CMOS sensors, and two of Sony’s BIONZ image processing engines. This enables it to capture full high-definition video for each eye.

“There’s now a good range of 3D content, including movies and games. So we’d like to make 3D personal content more accessible as well, and expand the 3D world through 3D Handycams along with TVs. In that sense, this is an ambitious, forward-looking product.”

Captured video is previewed on a 3.5-inch LCD that supports naked-eye 3D, so you can see the 3D effect while shooting. The 3D signal system uses the frame packing HDMI format, which can send two full HD signals, at 1920 x 1080 pixels, for each eye. This provides higher 3D picture quality than the conventional side-by side format.

“We think this camera will be used by typical Handycam users; for example, families with a new baby, or people who enjoy shooting scenery. What’s good about 3D is that it really brings back memories, which makes it ideal for personal content. When you look at 3D pictures, all the joy and impact of the experience comes back to you, and this is something unique to personal content.”

This model is available in silver only, and it’s recommended retail price is about 150,000 yen. (Approximately $1,800US)

Original post: http://www.diginfo.tv/2011/01/17/11-0005-r-en.php

< PREVIOUS ARTICLES NEXT ARTICLES >

Specification for Naming VFX Image Sequences Released

ETC’s VFX Working Group has published a specification for best practices naming image sequences such as plates and comps. File naming is an essential tool for organizing the multitude of frames that are inputs and outputs from the VFX process. Prior to the publication of this specification, each organization had its own naming scheme, requiring custom processes for each partner, which often resulted in confusion and miscommunication.

The new ETC@USC specification focuses primarily on sequences of individual images. The initial use case was VFX plates, typically delivered as OpenEXR or DPX files. However, the team soon realized that the same naming conventions can apply to virtually any image sequence. Consequently, the specification was written to handle a wide array of assets and use cases.

To ensure all requirements are represented, the working group included over 2 dozen participants representing studios, VFX houses, tool creators, creatives and others.  The ETC@USC also worked closely with MovieLabs to ensure that the specification could be integrated as part of their 2030 Vision.

A key design criteria for this specification is compatibility with existing practices.  Chair of the VFX working group, Horst Sarubin of Universal Pictures, said: “Our studio is committed to being at the forefront of designing best industry practices to modernize and simplify workflows, and we believe this white paper succeeded in building a new foundation for tools to transfer files in the most efficient manner.”

This specification is compatible with other initiatives such as the Visual Effects Society (VES) Transfer Specifications. “We wanted to make it as seamless as possible for everyone to adopt this specification,” said working group co-chair and ETC@USC’s Erik Weaver. “To ensure all perspectives were represented we created a team of industry experts familiar with the handling of these materials and collaborated with a number of industry groups.”

“Collaboration between MovieLabs and important industry groups like the ETC is critical to implementing the 2030 Vision,” said Craig Seidel, SVP of MovieLabs. “This specification is a key step in defining the foundations for better software-defined workflows. We look forward to continued partnership with the ETC on implementing other critical elements of the 2030 Vision.”

The specification is available online for anyone to use.

Oops, something went wrong.