SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : C-Cube
CUBE 36.51+0.2%3:51 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: DiViT who wrote (40397)5/4/1999 6:47:00 PM
From: William T. Katz  Read Replies (1) of 50808
 
RE: How the other chips faired

Been fairly busy, but I'll type out blurbs on each of the other two chips.

Philips SAA6755

"The Philips MPEG-2 encoder falls short of current technology; images generated and viewed using the SAA6755 lack that certain "sparkle" which is found in broadcast-quality video.

So while the basic concept behind the Philips product appears to be good, the output video quality falls far short of what is acceptable even in a consumer marketplace now due to a video bit-rate that is far too low to yield good, quality images."

Matsushita and Partners

"The history here is that Conopus had been looking for an affordable MPEG-2 chip set over a considerable length of time and could not find one until they tested and evaluated this Matsushita product. The Matsushita chip was the only one they found that offered a near broadcast-quality output. Likewise, matsushita Corporation had been looking for a video hardware manufacturer to both utilize their chip set and perhaps write suitable "microcode" for controlling the chip's performance. I'd say this has turned out to be an ideal marriage of technologies...

And for my taste, only one of these new chips, the Matsushita MN85560, proved to be acceptable for professional-looking MPEG-2 encoding."

There you have it. 3 chips reviewed and Matsushita > Philips > Cube from how I read it.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext