Re: xvid_encraw: AVI output >2 GB?

The code you're looking for can be found at http://members.optusnet.com.au/=
squid_80/sources/Specifically the xvid_encraw_src.zip contains the matroska=
 writing source code and AviWriter_src.zip contains source code (taken from=
 virtualdub) for an AVI writing library designed to be a drop-in replacemen=
t for AVIFile that can handle >2GB output.

> To: [email protected]
> Date: Thu, 9 Jul 2015 09:56:20 +0200
> From: [email protected]
> Subject: Re: [Xvid-devel] xvid_encraw: AVI output >2 GB?
> =

> App level threading may not help MeGUI development much either. The  =

> segments would have to be concatenated afterwards, which is not as trivia=
l  =

> in many cases as one may wish. And selecting the segment borders may not  =

> take scene changes (as sensible candidates for GOP starts) into account, =
I  =

> fear...
> =

> I was just looking for MKV support in xvid_encraw and found that, when a  =

> symbol "XVID_MKV_OUTPUT" is defined, a file "matroska.cpp" would have to  =

> be included. But it seems that it does not exist. So it was probably neve=
r  =

> programmed yet?
> =

> And even if it were available, I wonder if you would use either the VfW  =

> compatible video stream tagging (like VirtualDubMod does) or the native  =

> one. This might be important for AviMux-GUI support as well.
> =

> The more we discuss this topic, the less important MPEG4-ASP and AVI will=
  =

> get (HEVC development is currently a bit more interesting) ... ;) -- But  =

> legacy players will persist for a while. Xvid is not yet dead, just about=
  =

> to retire.
> =

> -- =

> =

> Fun and success!
> Mario *LigH* Rohkr=E4mer
> mailto:[email protected]
>  =

> _______________________________________________
> Xvid-devel mailing list
> [email protected]
> http://list.xvid.org/mailman/listinfo/xvid-devel
 		 	   		  =