Mark Taylor schrieb am Die, 25 Jul 2000:
> -X: picks which of 7 algorithms will be used to determine if
> one noise 'signature' sounds better than another.
well, 0...7, seem to be 8 different ones ;-)
> -X should now be considered a permanent option. -Y and -Z change
> >from release to r
Hi.
On Tue, 25 Jul 2000, Mark Taylor wrote:
>> >Thanks for finding this. This was a subtle & rare bug in CBR,
>> >triggered by the -k option.
>> Can you tell me when this bug was introduced? I listened to some of my recent
>> encodings and found this blip in about every 20th track.
>Were they al
Hello Mark,
MT> I would guess it was introduced in 3.85: it requires a combination of
MT> scalefac_scale (defaulted in 3.85, before that enabled with -Y ), and
MT> not using enough low pass filtering for the amount of compression.
If I believe the history log and my own tests, scalefac_scale was
>
> >(-k, by the way, is *always* a bad idea. It overrides LAME's
> >default lowpass filters. It will cause ringing and twinking
> >at 128kbs)
>
> Are there examples for this? When I did some listening tests I noticed the
> missing frequencies but nothing else. Does the FhG encoder still do th
>
> Hi Mark,
>
> On Mon, 24 Jul 2000, Mark Taylor wrote:
> >Thanks for finding this. This was a subtle & rare bug in CBR,
> >triggered by the -k option.
>
> Can you tell me when this bug was introduced? I listened to some of my recent
> encodings and found this blip in about every 20th track.
Just a quick question, when cdex refers to "high
quality" that "may produce pinging" they are not using
the -k option are they? Also this bug only applies to
VBR right?
Regards,
Abe Corrie
--- Arne Zellentin <[EMAIL PROTECTED]> wrote:
> Hi Mark,
>
> On Mon, 24 Jul 2000, Mark Taylor wrote:
> >Th
Hi Mark,
On Mon, 24 Jul 2000, Mark Taylor wrote:
>Thanks for finding this. This was a subtle & rare bug in CBR,
>triggered by the -k option.
Can you tell me when this bug was introduced? I listened to some of my recent
encodings and found this blip in about every 20th track.
>(-k, by the way,
Hi Arne,
Thanks for finding this. This was a subtle & rare bug in CBR,
triggered by the -k option.
(-k, by the way, is *always* a bad idea. It overrides LAME's
default lowpass filters. It will cause ringing and twinking
at 128kbs)
Note to developers and -X6 fans:
The problem is in frame 232
