Re: Let's go for it then...
"Aitor Garay" <[email protected]> Fri, 11 Jul 2003 10:48:33 +0200
| Newsgroups | gmane.comp.video.h264.devel |
|---|---|
| Message-ID | <001401c34789$3696f3e0$bcb31fac@HAJC0062> |
Sorry guys, i will be very busy for a few days (including the weekend), hope that we
can discuss all of this next week!
But anyway, about the encoding/decoding thing. I think that it could be a good idea
to split the development of the encoder and the decoder. Both of them share a lot of
code, mainly all the "core" processes like transform, quantize, deblocking, intra prediction...
May be the best think is somehow start both parts simultaneously but focusing mainly on the
common parts at first.
/AITOR
----- Original Message -----
From: "Yves Dhondt" <[email protected]>
To: <[email protected]>
Sent: Thursday, July 10, 2003 11:35 PM
Subject: Re: [Hdot264-devel] Let's go for it then...
>
> ----- Original Message -----
> From: "Oztan Harmanci" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, July 10, 2003 9:06 PM
> Subject: Re: [Hdot264-devel] Let's go for it then...
>
>
> > > Then is easy, just fill in the gaps... ;-) As i commented long ago
> > IMHO the
> > > best first milestone must be to have a compliant intra coder
> >
> > Yes, I remember you saying that but I partially agree: I agree
> > with the only INTRA frame approach, but I find it easier to
> > write the decoder first(since it is the decoder the standard specifies).
> > Especially with the help of the trace files generated by the reference
> > software it becomes even easier to debug.
> >
> > Maybe we can write the encoder and decoder in parallel but I dont think
> > we can manage that(can we?). I prefer starting with the decoder unless
> > people really want the encoder first. I'd like to hear from others too.
> >
> > Oztan
> >
>
> My 'assignment' is mostly directed towards the encoding part so I'm planning
> to spent most of my time on that part. However, I don't think you can see
> them both seperatly. Ideas for one side can just as well be used for the
> other side. Parallel developing just seems the best way to go if you ask
> me. Maybe we should split up in 2 parts for the developing purpose but
> still keep an eye on the other part.
>
> Yves
>
> BTW next week I'm on holiday.
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Hdot264-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hdot264-devel
>
>
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1