[x264-devel] Re: VUI timing info issue

[shauli.rozen at gmail.com]

I also tried the vlc player , and it seems to work the same way that
x264 works. Do you know what lib there are using for the h264 decoding?


On 1/18/06, shauli.rozen at gmail.com <shauli.rozen at gmail.com> wrote:
>
> I did not know the all moonlight - elecard - Mainconsept history. It is
> good to know , as I see it
> we should be compliant with the standard ( i.e - lose support of the old
> moonlight codec ) since I think newer codecs will do so.
>
> In general I think that this is not a huge issue since the bit stream will
> almost always be muxed
> into a file format , and the display time for each frame will be taken
> from the container.
>
> when I muxed the x264 bit stream to a 3gpp file and played it in the apple
> quick time player
> I got a correct bit rate.
>
>
>  On 1/18/06, Måns Rullgård <mru at inprovide.com> wrote:
> >
> >
> > shauli.rozen at gmail.com said:
> > > I first tried the moonlight codec and it worked fine. Just recently I
> > tried
> > > elecard , which apparently follows the standard and thus resulting in
> > half the
> > > frame rate.
> >
> > OK.  For the record, the Moonlight codec was developed by
> > Elecard.  Moonlight
> > no longer exists, and Elecard has been taken over by Mainconcept.  The
> > codec
> > from Mainconcept labeled version 2 is the same Elecard codec under a new
> > name,
> > and shares nothing with earlier Mainconcept codecs.  The old Moonlight
> > codec
> > uses the VUI timing info the same way as x264 does currently ( i.e.
> > incorrectly),
> > which is why I originally wrote it like that in x264.  The new
> > Moonlight/Elecard/Mainconcept codec appears to follow the spec.
> >
> > Does anyone have info about other current codecs (Nero, Ateme, Apple,
> > ...)?
> > I'd like to get this fixed once and for all.
> >
> > --
> > Måns Rullgård
> > mru at inprovide.com
> >
> > --
> > This is the x264-devel mailing-list
> > To unsubscribe, go to: http://developers.videolan.org/lists.html
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.videolan.org/pipermail/x264-devel/attachments/20060118/23997fc8/attachment.htm