![[b11]](./images/smilies/b11.gif){kind=small}
Good news!With the latest version of WinAmp - v2.79, I can use MAD with WinAmp's built-in "CrossFading DirectSound" output plugin. Both 24-bits and 32-bits can be used for playback.
24-bits playback in Winamp using MAD plugin
版主: DearHoney
*** No need to use "Warped Wave Wrapper Driver" for Winamp 2.79!!!
<!-- BBCode Quote Start --><FONT COLOR=GREEN>
Good news!
With the latest version of WinAmp - v2.79, I can use MAD with WinAmp's built-in "CrossFading DirectSound" output plugin. Both 24-bits and 32-bits can be used for playback.
</FONT><!-- BBCode Quote End -->
<!-- BBCode Quote Start --><FONT COLOR=GREEN>
Good news!With the latest version of WinAmp - v2.79, I can use MAD with WinAmp's built-in "CrossFading DirectSound" output plugin. Both 24-bits and 32-bits can be used for playback.
</FONT><!-- BBCode Quote End -->
-
justthinking
- 神人
- 文章: 1366
- 註冊時間: 2001-01-04 08:00
- 來自: 敗家者天堂
- 聯繫:
<!-- BBCode Quote Start --><FONT COLOR=GREEN>
Good news!
With the latest version of WinAmp - v2.79, I can use MAD with WinAmp's built-in "CrossFading DirectSound" output plugin. Both 24-bits and 32-bits can be used for playback.
</FONT><!-- BBCode Quote End -->
I am sorry pal, not meant to burst your bubble...
but the method you described of MAD using 24bits,
even 32bits mode actually has NO BENIFIT in sound
quality what so ever.
As matter of fact, I would say the sound quality
might actually decrease compare to flat out uses
16bits mode with wave output.
The reason is that when you uses direct sound mode
and uses 24bits even 32bits, you are actually make
the unnecessary mix/wrap of sound..and since there
is not a soundcard present that's capable of handle
the actual 24bits/32bits processing, you might just
been filling 0 during the process, so there is no
benefit to sound quality compare to 16bits mode.
Second, all the unnecessary converting/wrapping might
result in worse sound quality than original result.
SOUND BLASTER AUDIGY's 24bits function has no actual
processing capability, it can only send out digital
signals at 24bits, not internally process the signals
at 24bits..
Good news!With the latest version of WinAmp - v2.79, I can use MAD with WinAmp's built-in "CrossFading DirectSound" output plugin. Both 24-bits and 32-bits can be used for playback.
</FONT><!-- BBCode Quote End -->
I am sorry pal, not meant to burst your bubble...
but the method you described of MAD using 24bits,
even 32bits mode actually has NO BENIFIT in sound
quality what so ever.
As matter of fact, I would say the sound quality
might actually decrease compare to flat out uses
16bits mode with wave output.
The reason is that when you uses direct sound mode
and uses 24bits even 32bits, you are actually make
the unnecessary mix/wrap of sound..and since there
is not a soundcard present that's capable of handle
the actual 24bits/32bits processing, you might just
been filling 0 during the process, so there is no
benefit to sound quality compare to 16bits mode.
Second, all the unnecessary converting/wrapping might
result in worse sound quality than original result.
SOUND BLASTER AUDIGY's 24bits function has no actual
processing capability, it can only send out digital
signals at 24bits, not internally process the signals
at 24bits..
-
justthinking
- 神人
- 文章: 1366
- 註冊時間: 2001-01-04 08:00
- 來自: 敗家者天堂
- 聯繫:
Have you try MAD in Winamp? I can hear the difference between MAD and the Winamp built-in MP3 decoder.
Your explanations is just one of the points founf in hte internet.
My personal feelings:-
with MAD - solid output, clearer sound and no distortion at high frequency
Why not have a try of MAD? If you don't like it than you can keep using Winamp built-in decoder.
![[b14]](./images/smilies/b14.gif)
Your explanations is just one of the points founf in hte internet.
My personal feelings:-
with MAD - solid output, clearer sound and no distortion at high frequency
Why not have a try of MAD? If you don't like it than you can keep using Winamp built-in decoder.
-
justthinking
- 神人
- 文章: 1366
- 註冊時間: 2001-01-04 08:00
- 來自: 敗家者天堂
- 聯繫:
Dude, you have to read my post a lot more closely..
you are getting all the points wrong..and let us get
the facts straight..
OF COURSE I KNOW ABOUT MAD, AND OF COURSE I AM USING IT.
AND OF COURSE I KNOW IT'S MUCH BETTER THAN THE DEFAULT
DECODER BUILDIN WINAMP.
I AM JUST MAKING A POINT THAT IT'S USELESS FOR YOU TO SET
MAD TO 24BITS OR 32BITS B/C YOU DON'T HAVE THE HARDWARE
THAT SUPPORT TRUE 24BITS OR 32BITS DECODING.
When I said it's better to just uses 16bits mode, I am
referring to using MAD's 16bit mode like default. B/C as
I explained, you gain nothing using 24bits or 32bits mode
other than get bunch of zeros filled up and might lose
sound quality b/c all the unnecessary processing.
It is very alarming whenever false information been passed
upon internet and one of the principle here in this forum
is to minimize this type of situation as hard as we can.
I understand your intentions were good, but I also arge you
to study more, to get more facts, and to understand more
about the entire process, which in this case related to the
decoding process of MAD plugin, before you post any quote
on quote "findings".
you are getting all the points wrong..and let us get
the facts straight..
OF COURSE I KNOW ABOUT MAD, AND OF COURSE I AM USING IT.
AND OF COURSE I KNOW IT'S MUCH BETTER THAN THE DEFAULT
DECODER BUILDIN WINAMP.
I AM JUST MAKING A POINT THAT IT'S USELESS FOR YOU TO SET
MAD TO 24BITS OR 32BITS B/C YOU DON'T HAVE THE HARDWARE
THAT SUPPORT TRUE 24BITS OR 32BITS DECODING.
When I said it's better to just uses 16bits mode, I am
referring to using MAD's 16bit mode like default. B/C as
I explained, you gain nothing using 24bits or 32bits mode
other than get bunch of zeros filled up and might lose
sound quality b/c all the unnecessary processing.
It is very alarming whenever false information been passed
upon internet and one of the principle here in this forum
is to minimize this type of situation as hard as we can.
I understand your intentions were good, but I also arge you
to study more, to get more facts, and to understand more
about the entire process, which in this case related to the
decoding process of MAD plugin, before you post any quote
on quote "findings".
-
justthinking
- 神人
- 文章: 1366
- 註冊時間: 2001-01-04 08:00
- 來自: 敗家者天堂
- 聯繫:
Also, my explanation is not just MY POINT OF VIEW.
my explanation is to set the FACTS straight and to
point out the errors in your post.
Just think about it, when a soundcard like SB Live!
can use 24bits even 32bits decoding in MAD, and we
all know it is just a 16bit processing unit, don't
you see the antinomy there? Don't you think it is
more important to find out why and how this setting
works? and to find out if indeed this setting is
24bits or fake 24bits??
my explanation is to set the FACTS straight and to
point out the errors in your post.
Just think about it, when a soundcard like SB Live!
can use 24bits even 32bits decoding in MAD, and we
all know it is just a 16bit processing unit, don't
you see the antinomy there? Don't you think it is
more important to find out why and how this setting
works? and to find out if indeed this setting is
24bits or fake 24bits??
愛國心是惡黨們發表不負責任言論的藉口
I will stop posting new message on this topic as there is no ending.
The following is captured from MAD web site and David J M Robinson web site:-
From MAD:-
Because MAD provides full 24-bit PCM output, applications using MAD are able to produce high quality audio. Even when the output device supports only 16-bit PCM, applications can use the extra resolution to increase the audible dynamic range through the use of dithering or noise shaping.
From David J M Robinson:-
My mp3s are made from 16-bit CDs - why use a 24-bit decoder?
As you probably know, when you encode a CD to mp3 format, you don't store an exact copy of the original signal. When an mp3 is decoded, you don't get those original 16-bits back, but an approximation that should sound similar. When the decoder puts together all the elements held in the mp3 file, the arithmetical result can be very accurate in numerical terms, even if it's not exactly what was on the original CD. If you round it to 16-bits, you add a small amount of extra distortion to this reconstructed signal, getting even further away from what was on the original CD. If you round it to 24-bits, you're still adding distortion, but it's 256 times quieter than that added by rounding to 16-bits.
I only have a 16-bit sound card - what use could a 24-bit decoder be?
If you calculate the result to 24-bit accuracy, and then round it to 16-bits, you gain nothing - the result will match all the standard 16-bit decoders. However, if you dither the result from 24-bits down to 16-bits, you can avoid all the distortion generated by rounding to 16-bits, and the result may sound better. Please read this article "http://www.mtsu.edu/~dsmitche/rim420/re ... ither.html" about dither for a fuller explanation of this.
![[b04]](./images/smilies/b04.gif)
The following is captured from MAD web site and David J M Robinson web site:-
From MAD:-
Because MAD provides full 24-bit PCM output, applications using MAD are able to produce high quality audio. Even when the output device supports only 16-bit PCM, applications can use the extra resolution to increase the audible dynamic range through the use of dithering or noise shaping.
From David J M Robinson:-
My mp3s are made from 16-bit CDs - why use a 24-bit decoder?
As you probably know, when you encode a CD to mp3 format, you don't store an exact copy of the original signal. When an mp3 is decoded, you don't get those original 16-bits back, but an approximation that should sound similar. When the decoder puts together all the elements held in the mp3 file, the arithmetical result can be very accurate in numerical terms, even if it's not exactly what was on the original CD. If you round it to 16-bits, you add a small amount of extra distortion to this reconstructed signal, getting even further away from what was on the original CD. If you round it to 24-bits, you're still adding distortion, but it's 256 times quieter than that added by rounding to 16-bits.
I only have a 16-bit sound card - what use could a 24-bit decoder be?
If you calculate the result to 24-bit accuracy, and then round it to 16-bits, you gain nothing - the result will match all the standard 16-bit decoders. However, if you dither the result from 24-bits down to 16-bits, you can avoid all the distortion generated by rounding to 16-bits, and the result may sound better. Please read this article "http://www.mtsu.edu/~dsmitche/rim420/re ... ither.html" about dither for a fuller explanation of this.
-
justthinking
- 神人
- 文章: 1366
- 註冊時間: 2001-01-04 08:00
- 來自: 敗家者天堂
- 聯繫:
To James Lee,
I think I know where your confusion came from. I believe
the problem is related to the function of the resolution
adjustments feature inside MAD plug-in.
Please beware that the resolution adjustments from 8bits
to 32bits is for OUTPUT only. Which has direct connection
with what your soundcard is capable of handling. It has
nothing to do with MAD's internal decoding, b/c MAD always
uses 24bits internal decoding regardless.
As far as MAD and 24bit processing, it is a fact that MAD
uses 24bit processing to DECODE, and if the output device
is like CardDeluxe, then there will be no need to DITHER,
so the output rate is indeed 24bits. However, when output
device is a 16bit soundcard, then MAD will DITHER PCM back
to 16bits. So it would be best to just set the resolution
to 16bit b/c that's what your soundcard can handle.
When you said you set the RESOLUTION to 24bits and 32bits,
and choose DirectSound as your output devices. You actually
are telling MAD to pass on the 24bit already decoded PCM to
DirectSound. In mose cases, the OS and SoundCard Driver WILL
NOT dither PCM from 24bits back to 16bits, and since your
soundcard can only perform 16bits output, you actually will
loses 8 bits of signals, which totaly violated the original
meaning of MAD using 24bits processing to decode. B/C you
now have lost 8bits of signals b/c no dithering was performed,
and this will result in poorer sound quality.
So, you should understand that regardless what you do, the
output wave you heard is still 16bits, and it's better to let
MAD do the ditering.
I think I know where your confusion came from. I believe
the problem is related to the function of the resolution
adjustments feature inside MAD plug-in.
Please beware that the resolution adjustments from 8bits
to 32bits is for OUTPUT only. Which has direct connection
with what your soundcard is capable of handling. It has
nothing to do with MAD's internal decoding, b/c MAD always
uses 24bits internal decoding regardless.
As far as MAD and 24bit processing, it is a fact that MAD
uses 24bit processing to DECODE, and if the output device
is like CardDeluxe, then there will be no need to DITHER,
so the output rate is indeed 24bits. However, when output
device is a 16bit soundcard, then MAD will DITHER PCM back
to 16bits. So it would be best to just set the resolution
to 16bit b/c that's what your soundcard can handle.
When you said you set the RESOLUTION to 24bits and 32bits,
and choose DirectSound as your output devices. You actually
are telling MAD to pass on the 24bit already decoded PCM to
DirectSound. In mose cases, the OS and SoundCard Driver WILL
NOT dither PCM from 24bits back to 16bits, and since your
soundcard can only perform 16bits output, you actually will
loses 8 bits of signals, which totaly violated the original
meaning of MAD using 24bits processing to decode. B/C you
now have lost 8bits of signals b/c no dithering was performed,
and this will result in poorer sound quality.
So, you should understand that regardless what you do, the
output wave you heard is still 16bits, and it's better to let
MAD do the ditering.
愛國心是惡黨們發表不負責任言論的藉口