Re: H.264 and VC-1 Interface

Tech-Archive recommends: Fix windows errors by optimizing your registry

"David" wrote:

> My understanding is that COM is deprecated for .Net.

They are different things. MS is phasing out COM in some
areas because .NET is better suited for some jobs, but COM
is not going anywhere for a long time.

> Is
> there or will there be a standard interface for h.264 or
> VC-1 for .Net?

I doubt it. Generally speaking, .NET is not efficient enough
for multimedia.

Beside that, there hasn't ever been a standard configuration
interface for video codecs and it is unlikely there will be
one in the near future, for .NET or otherwise. MS doesn't
even support H.264. Maybe codec vendors may come up with an
industry standard, but it doesn't seem likely.

> Also, understanding the h.264 and VC-1 are standards to
> follow and each implementation of this standard will
> taunt faster encoding rates, higher compression ratios or

That should hold true at least for H.264.

> . . I would assume each would have similar type
> interfaces to control the quality of the image.

The H.264 (actually, MPEG-4 AVC) and VC-1 standards specify
the bitstream syntax from the point of view of the decoder.
Implementation of the encoder is completely up to the
vendor. Different encoders for the same video format have
very different configuration parameters that are related to
the features and inner workings of the implementation. H.264
and VC-1 are not even the same format.

> Are there
> any other features / controls that I should look for that
> makes a codec stand out from the others?

There is no general rule.

--
// Alessandro Angeli
// MVP :: DigitalMedia
// a dot angeli at psynet dot net


.

Relevant Pages

  • Re: 20 Years of JPEG Celebrated With Software Launch
    ... Does well for large images, ... "Guido" is a bad visual standard. ... PSNR, however, can *also* tell a story, namely whether the overall codec design is sane, as there are a couple of interesting theoretical results on it. ... You failed to provide *objective* reasons. ...
    (comp.compression)
  • Re: "Mastering C Pointers"....
    ... I'm not talking about your pointer response, which was generally good, as I ... Together they will help you understand pointers. ... >> Maybe for understanding the C standard. ... > principles laid out in the Standard is vital. ...
    (comp.lang.c)
  • Re: "Mastering C Pointers"....
    ... >> standard that defines the language you are using. ... The real question was about pointers. ... > wonder why you're being such a pedant. ... > Maybe for understanding the C standard. ...
    (comp.lang.c)
  • Re: my future telephones [telecom]
    ... G.711 is a high bit rate (64 Kbps) ITU standard codec. ... native language of the modern digital telephone network. ...
    (comp.dcom.telecom)
  • Re: Enumerations in fortran 2003
    ... >>> that the OP is asking if F2003 enumerators are to be the same ... In particular, the sizeof ... That doesn't match my understanding of the C standard. ...
    (comp.lang.fortran)