Frank Klemm wrote:
>
> The following outputs have the following meanings:
>
> [ ] p = 0.00%, never used
> [%..] 0.00% < p < 0.01%
> [%.0] 0.01% < p < 0.05%
> [%.1] 0.05% <= p < 0.15%
> [%.2] 0.15% <= p < 0.25%
> ...
> [%.9]
> May be too difficult for end users, but nice for development.
I don't think that it may be annoying for end users.
> Another question would be, what is best:
>
> * Showing the percentage relative to the number of already coded frames
I would personnaly vote for this one.
Regards,
--
G
> 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?)
This difference is probably because in mpeg-1 th
| Another question:
| What is ETA? A basque terror organization? I don't found it in any
printed
| dictionary, also not in the big webster I bought in England. But you find
| nearly all C keywords in it ;-)
|
|
| eta: the 7th letter of the Greek alphabet -- H or n
|
Frank Klemm wrote:
>
> :: ETA - Estimated time of arrival.
> ::
> Why this time changes continuously?
> Is the estimation so bad?
>
> I think it's not the estimated time of arrival, but the remaining
> time until arrival. RTUA?
>
Welcome to the english language. RTUA would be logical but ETA
On Mit, 13 Sep 2000, you wrote:
>:: ETA - Estimated time of arrival.
>Why this time changes continuously?
>Is the estimation so bad?
:-)
>I think it's not the estimated time of arrival, but the remaining
>time until arrival. RTUA?
Actually I think it's Estimated time _to_ arrival. Ofs and tos
On 12 Sep 2000, Frank Klemm wrote:
>RPC support, SMP support and distributed computing would be a very nice
>thing for LAME and would be an outstanding feature.
>Are there are plans and interests to support this? Not this year, but
>starting with this things in spring next year, not earlier.
>The
On 12 Sep 2000, Frank Klemm wrote:
>Please do not remove it. Note:
>Wer const-Attribute entfernt oder verstümmelt, oder entfernte
>oder verstümmelte const-Attribute in Umlauf bringt, wird nicht
>mit Debuggen unter 2 Jahren bestraft.
>Is there someone who can translate this into *good
:: ETA - Estimated time of arrival.
::
Why this time changes continuously?
Is the estimation so bad?
I think it's not the estimated time of arrival, but the remaining
time until arrival. RTUA?
--
Mit freundlichen Grüßen
Frank Klemm
eMail | [EMAIL PROTECTED] home: [EMAIL PROTECTED]
ph
I have added a lot of 'const' attributes to constant tables.
Please do not remove it. Note:
Wer const-Attribute entfernt oder verstümmelt, oder entfernte
oder verstümmelte const-Attribute in Umlauf bringt, wird nicht
mit Debuggen unter 2 Jahren bestraft.
Is there someone who can t
ETA - Estimated time of arrival.
kind of obscure :)
mark stephens
- Original Message -
From: "Frank Klemm" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 12, 2000 4:00 PM
Subject: Re: [MP3 ENCODER] min bitrate and bit reservoir (was: MS switching)
>
> Another que
The following outputs have the following meanings:
[ ] p = 0.00%, never used
[%..] 0.00% < p < 0.01%
[%.0] 0.01% < p < 0.05%
[%.1] 0.05% <= p < 0.15%
[%.2] 0.15% <= p < 0.25%
...
[%.9] 0.85% <= p < 0.95%
[ 1%] 0.
On Tue, Sep 12, 2000 at 12:25:46PM +0200, Gabriel Bouvigne wrote:
>
> In both cases I think ( I didn't really calculate) the size increase should
> be something around 5%.
>
Wrong. For the slight increase ca. 0.1%, for the more harder ca. 1%.
> Yes, it's tolerable, but I personnaly don't think
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
- Original Message -
From:
Gabriel
Bouvigne
To: [EMAIL PROTECTED]
Sent: Tuesday, September 12, 2000 10:10
AM
Subject: Re: [MP3 ENCODER] --voice
Could someone satisfy my curiosity about this
option (descibed as 'experimenatl' in the docs for ver
- Original Message -
From:
Gabriel
Bouvigne
To: [EMAIL PROTECTED]
Sent: Tuesday, September 12, 2000 10:10
AM
Subject: Re: [MP3 ENCODER] --voice
Could someone satisfy my curiosity about this
option (descibed as 'experimenatl' in the docs for ver
RPC support, SMP support and distributed computing would be a very nice
thing for LAME and would be an outstanding feature.
Are there are plans and interests to support this? Not this year, but
starting with this things in spring next year, not earlier.
The core of lame is less or not effected,
I'm monitoring the encoding of material originally recorded in the 30's (now on CD).
When I look at the MDCT and scale band info:
Left and Mid Channels closely match.
Right Channel shows very little energy.
Side Channel shows very little energy.
In CoolEdit L&R "appear" to be almost identical(m
Could someone satisfy my curiosity about this
option (descibed as 'experimenatl' in the docs for ver 3.85, but I see
that it is available in RazorLame) ?
Does it have fixed default parameters like the
--preset voice option, and if so what are they ?
What is the thinking
> The 4 examples I brought were POSSIBLE information you have after coding a
> PCM file. These are possible scenarios after you have coding files.
> You've tried to do your very best and you see after coding it wasn't.
>
> Real world examples and exercises:
>
> After coding with -V0 you got:
--s
20 matches
Mail list logo
