POV-Ray : Newsgroups : povray.general : What we really need, CMPEG in C source` Server Time
9 Aug 2024 03:18:30 EDT (-0400)
  What we really need, CMPEG in C source` (Message 1 to 6 of 6)  
From: Matt Giwer
Subject: What we really need, CMPEG in C source`
Date: 4 Sep 2000 02:29:36
Message: <39B34159.407AA035@ij.net>
I have looked and found nothing. Anyone know where to find it if
available? This is for a linux version of it. 

	I have read the Berkeley version mpeg which will not run on linux
despite the protestations to the contrary. The entire cmpeg DOS
executable is smaller than the Berkeley credits fer chrissakes. 

-- 
Giwer's Rule: Aps expand to consume every available
increase leaving a net zero increase in content. 
	-- The Iron Webmaster, 71


Post a reply to this message

From: Warp
Subject: Re: What we really need, CMPEG in C source`
Date: 4 Sep 2000 06:20:28
Message: <39b3776b@news.povray.org>
You should note that mpeg_encode is about 10 times faster than cmpeg.

  No joking.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/


Post a reply to this message

From: John VanSickle
Subject: Re: What we really need, CMPEG in C source`
Date: 4 Sep 2000 15:00:18
Message: <39B3F1FA.493DB9CC@erols.com>
Warp wrote:
> 
>   You should note that mpeg_encode is about 10 times faster than
> cmpeg.

The docs for CMPEG say that it's written to run on an 8086 ("no '386 or
Windows required", say the docs).  That probably accounts for the
difference.

The IRTC, and the re-write of my mesh modeller, take up the bulk of
my free time, or else I'd work on a more modern version of CMPEG.

Regards,
John
-- 
ICQ: 46085459


Post a reply to this message

From: Matt Giwer
Subject: Re: What we really need, CMPEG in C source`
Date: 4 Sep 2000 18:25:16
Message: <39B42154.46E12EDB@ij.net>
Warp wrote:
> 
>   You should note that mpeg_encode is about 10 times faster than cmpeg.
> 
>   No joking.

	So far the best I have gotten are core dumps. If there is a secret to
making it run, I'd love to know it.


Post a reply to this message

From: Dick Balaska
Subject: Re: What we really need, CMPEG in C source`
Date: 5 Sep 2000 04:35:28
Message: <39B4AFF4.C5879298@buckosoft.com>
Matt Giwer wrote:
> 
> Warp wrote:
> >
> >   You should note that mpeg_encode is about 10 times faster than cmpeg.
> >
> >   No joking.
> 
>         So far the best I have gotten are core dumps. If there is a secret to
> making it run, I'd love to know it.

Well with zero data, like a stack trace or seeing the control file you feed it,
the best advise i can give is "Don't do that".

I've been using mpeg_encode for 4 years and have not had one core dump,
on NT or Unix.

dik


Post a reply to this message

From: Matt Giwer
Subject: Re: What we really need, CMPEG in C source`
Date: 5 Sep 2000 12:45:44
Message: <39B5233D.B9D9F39E@ij.net>
Dick Balaska wrote:
> 
> Matt Giwer wrote:
> >
> > Warp wrote:
> > >
> > >   You should note that mpeg_encode is about 10 times faster than cmpeg.
> > >
> > >   No joking.
> >
> >         So far the best I have gotten are core dumps. If there is a secret to
> > making it run, I'd love to know it.
> 
> Well with zero data, like a stack trace or seeing the control file you feed it,
> the best advise i can give is "Don't do that".
> 
> I've been using mpeg_encode for 4 years and have not had one core dump,
> on NT or Unix.

	A bit of an apology here. 

	Here is the situation. I went to
http://bmrc.berkeley.edu/ftp/pub/multimedia/mpeg/encode/ 
	and download the linux tar.gz extract and I get 'cannot execute binary
file'. No source, only an executable and a man page. The modes are +x.
So I'm dead in the water. 

	The core dump is not what I should have mentioned because I don't
remember precisely what I did after getting the source from the above.
It will not compile as found. But I don't remember at all what I did to
get it to compile which obviates my who comment on core dump. 

	The problem with compiling is in libpnmrw.c at line 364 warning item
might be uninitialized. I got around that somehow -- obviously the wrong
way. 

	Whatever I did, it executes the .param file then dumps. So I was making
some progress. 

	So to go back to the basics, I can't even get the linux binary to
execute much less consider the .param file.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.