Frank, your are missing a third option:
PROJECT_MAINTAINER_DOES_NOT_CARE_AND DOES_NOT_WANT_THIS_CODE_IN_LAME
The display is updated every 50 frames. It is simple
and works well enough.
I want this type of code kept to an absolute minimum since this kind
of stuff really belongs in the front end. Most GUIs which use LAME
already do their own status display. I dont want to see even more
timing code in lame.c.
Mark
> X-Authentication-Warning: geek.rcc.se: majordom set sender to
>[EMAIL PROTECTED] using -f
> >Received: (from pfk@localhost)
> by fuchs.offl.uni-jena.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id UAA04980
> for [EMAIL PROTECTED]; Tue, 12 Sep 2000 20:14:41 +0200
> Date: Tue, 12 Sep 2000 20:14:41 +0200
> From: Frank Klemm <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
> Sender: [EMAIL PROTECTED]
> Precedence: bulk
> Reply-To: [EMAIL PROTECTED]
>
> There are two possiblities for display update frequency:
>
>
> 1st)
> #define I_HAVE_NEVER_SEEN_LAME_ON_A_486_100_OR_A_ATHLON_1000
>
> and display updates every 50 frames (MPEG-1) or 100 frames (MPEG-2)
> (Why this differences?)
>
>
> 2nd)
> Do not define I_HAVE_NEVER_SEEN_LAME_ON_A_486_100_OR_A_ATHLON_1000
>
> You can also define MY_PREFERED_UPDATE_STEP by values like
> 1, 2, 5, 10, 20, 50, 100 (default is 1).
>
> Update interval is 2 seconds (if not modified by -disptime xxx) time
> + needed for display (so no lockup is possible),
> additional frame number steps can be rounded to multiples
> of MY_PREFERED_UPDATE_STEP.
>
> But the display will not more often than every 2 seconds updated
> (if not modified by -disptime xxx).
>
> The standard value of 2 seconds is also debatable. It's a float,
> so personal preferences can be satisfied very accurately ;-)
>
> This also prevents lame from update frequencies in the range of 50...60 Hz
> (resulting in additional hum!) on Athlon 1000 systems coding mono, low
> quality MPEG-2 files. Sounds worse.
>
>
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
