On Tue, 2007-03-20 at 15:12 -0700, Steven M. Schultz wrote:
> RC2 is when the problem happened - so if you have that you've got
> the problem :(
>
Looks like both CVS versions I have are RC2. :( Guess I'll have to use
a 1.8.0 tarball.
> > the x86_64 bit distro for processing video
On Tue, 20 Mar 2007, Stan Gammons wrote:
> No. I've seen several messages about aspect ratio, but I haven't
> followed it that closely.
Ah, you want the _other_ topic of recent discussion ;)
> Maybe I still have an older CVS on the 32 bit machine (I went back to
RC2 is when th
On Tue, 2007-03-20 at 14:27 -0700, Steven M. Schultz wrote:
> Have you noticed the discussions on the mailing lists about a
> nasty bug in mpeg2enc's rate control logic?
>
No. I've seen several messages about aspect ratio, but I haven't
followed it that closely.
> I think the
On Tue, 20 Mar 2007, Stan Gammons wrote:
> I encoded a DV capture today using the CVS version of mjpeg tools from
> last night. I noticed the length of the m2v file is MUCH smaller than
> one of a comparable run time (roughly 25 minutes) that I encoded a week
> or two ago. In the past the m2v fil
Hi all,
I encoded a DV capture today using the CVS version of mjpeg tools from
last night. I noticed the length of the m2v file is MUCH smaller than
one of a comparable run time (roughly 25 minutes) that I encoded a week
or two ago. In the past the m2v files were roughly 1.3 Gigabytes. Now
they ar
Hi Christian,
As far as I know, mjpegtools do not have a problem with AMD-CPUs and mmx.
My cpu is also an Athlon64. I'm using a cvs version of mjpegtools.
Gert
[EMAIL PROTECTED] wrote:
> Hello Gert,
>
> I am glad to hea that you do not have the memoryacesserror.
> I have also already tryed wi
Hello Gert,
I am glad to hea that you do not have the memoryacesserror.
I have also already tryed without any -O infer parameter since CAP is default
but I still get the same problem. :(
Maybe the problem only shows up because I use an AMD-Athlon64-3200+-Prozessor
and I have heared that mjpegtoo
