From: Shawn O'Connor on
The only thing I know for sure is how to use Google ; )

"Max Arwood" <maxarwood(a)sbcglobal.net> wrote in message
news:XllIh.8706$re4.5696(a)newssvr12.news.prodigy.net...
> How do you know all this stuff???? And where were you the other day when
we
> needed you?
> OK well thanks for the info.
> Thanks,
> Max Arwood
>
> "Shawn O'Connor" <SO(a)comcast.net> wrote in message
> news:7c6dnUk11vQSqGzYnZ2dnUVZ_t2tnZ2d(a)comcast.com...
> >
> > "kitekrazy" <kitekrazy(a)sbcglobal.net.nospam> wrote in message
> > news:CTLHh.6805$jx3.1071(a)newssvr25.news.prodigy.net...
> >> polymod wrote:
> >> > "Sue Morton" <867-5309(a)domain.invalid> wrote in message
> >> > news:NdiHh.5360$M65.5339(a)newssvr21.news.prodigy.net...
> >> >> I've never used WinAmp so I don't know how that one compares.
> >> >
> >> > I've said it above, and I'll say it again.
> >> > I've been using Winamp for years. It opens ALL my 24 bit files.
> >> >
> >> > There....I said it again<g>
> >> >
> >> > Poly
> >> >
> >> >
> >> One more time.....
> >>
> >> I agree with you there.
> >
> > This might help.....
> >
> > Legacy HD Audio Filter - Many audio processing applications still
produce
> > high-definition audio such as 24bit/96kHz in a legacy WAV format. By
> > default
> > DirectShow players (such as Media Player) won't be able to play these
> > files
> > as the Audio Renderer refuses to accept this legacy type even though it
is
> > perfectly capable of playing it. This filter registers itself as being
> > able
> > to handle this legacy format, and at the same time converts to a format
> > the
> > DirectShow Audio Renderer will accept (WAVEFORMATEXTENSIBLE). This is
done
> > without altering the audio data in any way.
> >
> > http://www.chrisnet.net/msdn/AudioTypeConvert.zip
> >
> > Download it, Unzip it, and place the AudioTypeConvert.ax file in your
> > System32 folder.
> > Then open a Command Prompt and register it with this:
> >
> > regsvr32 c:\windows\system32\AudioTypeConvert.ax
> >
> > If you want to remove it at anytime just unregister it with:
> >
> > regsvr32 /U c:\windows\system32\AudioTypeConvert.ax
> >
> >
>
>


From: Noel Borthwick on
Interesting. I've known about the WMP incompatibility with 24 bit audio
files, but didn't know someone wrote a filter to circumvent this. A long
time ago my machine somehow started playing 24 bit wave files from SONAR -
most likely I acquired a filter like this through some application I
installed. I spoke to someone from MS once and he was very puzzled by how
my version of WMP played these 24 bit audio files and his didn't :-)

Some background about 24 bit audio and this format to explains the history
of this infamous problem. Years ago (90's) when audio editors like
SoundForge first started supporting 24 bit audio these files were written
with the classic WAVEFORMATEX header with the bit depth set to 24 bits. For
some reason Microsoft has stubbornly failed to acknowledge this a valid wave
format and prefers the file to be authored with a WAVEFORMATEXTENSIBLE
header. A few years ago when we were adding surround support (which requires
a WAVEFORMATEXTENSIBLE header), out of curiosity I changed the way SONAR
wrote 24 bit audio to write it in the MS blessed way. Unfortunately all hell
broke loose since only SONAR and a couple of applications were able to read
these files. It turned out that WAVEFORMATEXTENSIBLE was very poorly
supported by most DAW's and audio editors. They would either barf on the
file or read it as an incorrect format. So I switched back to writing them
in classic WAVEFORMATEX. I'd much rather other apps read these files than
MediaPlayer thank you <g>

Its pretty strange that Microsoft has stubbornly refused to support these
files despite the fact that the entire audio industry writes them this way.

Noel

"Shawn O'Connor" <SO(a)comcast.net> wrote in message
news:7c6dnUk11vQSqGzYnZ2dnUVZ_t2tnZ2d(a)comcast.com...
> This might help.....
>
> Legacy HD Audio Filter - Many audio processing applications still produce
> high-definition audio such as 24bit/96kHz in a legacy WAV format. By
> default
> DirectShow players (such as Media Player) won't be able to play these
> files
> as the Audio Renderer refuses to accept this legacy type even though it is
> perfectly capable of playing it. This filter registers itself as being
> able
> to handle this legacy format, and at the same time converts to a format
> the
> DirectShow Audio Renderer will accept (WAVEFORMATEXTENSIBLE). This is done
> without altering the audio data in any way.
>
> http://www.chrisnet.net/msdn/AudioTypeConvert.zip
>
> Download it, Unzip it, and place the AudioTypeConvert.ax file in your
> System32 folder.
> Then open a Command Prompt and register it with this:
>
> regsvr32 c:\windows\system32\AudioTypeConvert.ax
>
> If you want to remove it at anytime just unregister it with:
>
> regsvr32 /U c:\windows\system32\AudioTypeConvert.ax
>
>


From: Gerry Peters on
Thanks for filling in the blanks for this weird mystery. Now it all
makes sense. You would think that MS would at minimum have that filter
as part of XP. Another great example of why it's bad for MS to have
pretty much a monopoly on OS systems.

Gerry Peters

On Sun, 11 Mar 2007 15:57:29 -0400, "Noel Borthwick"
<nospam(a)cakewalk.com> wrote:

>Interesting. I've known about the WMP incompatibility with 24 bit audio
>files, but didn't know someone wrote a filter to circumvent this. A long
>time ago my machine somehow started playing 24 bit wave files from SONAR -
>most likely I acquired a filter like this through some application I
>installed. I spoke to someone from MS once and he was very puzzled by how
>my version of WMP played these 24 bit audio files and his didn't :-)
>
>Some background about 24 bit audio and this format to explains the history
>of this infamous problem. Years ago (90's) when audio editors like
>SoundForge first started supporting 24 bit audio these files were written
>with the classic WAVEFORMATEX header with the bit depth set to 24 bits. For
>some reason Microsoft has stubbornly failed to acknowledge this a valid wave
>format and prefers the file to be authored with a WAVEFORMATEXTENSIBLE
>header. A few years ago when we were adding surround support (which requires
>a WAVEFORMATEXTENSIBLE header), out of curiosity I changed the way SONAR
>wrote 24 bit audio to write it in the MS blessed way. Unfortunately all hell
>broke loose since only SONAR and a couple of applications were able to read
>these files. It turned out that WAVEFORMATEXTENSIBLE was very poorly
>supported by most DAW's and audio editors. They would either barf on the
>file or read it as an incorrect format. So I switched back to writing them
>in classic WAVEFORMATEX. I'd much rather other apps read these files than
>MediaPlayer thank you <g>
>
>Its pretty strange that Microsoft has stubbornly refused to support these
>files despite the fact that the entire audio industry writes them this way.
>
>Noel
>
>"Shawn O'Connor" <SO(a)comcast.net> wrote in message
>news:7c6dnUk11vQSqGzYnZ2dnUVZ_t2tnZ2d(a)comcast.com...
>> This might help.....
>>
>> Legacy HD Audio Filter - Many audio processing applications still produce
>> high-definition audio such as 24bit/96kHz in a legacy WAV format. By
>> default
>> DirectShow players (such as Media Player) won't be able to play these
>> files
>> as the Audio Renderer refuses to accept this legacy type even though it is
>> perfectly capable of playing it. This filter registers itself as being
>> able
>> to handle this legacy format, and at the same time converts to a format
>> the
>> DirectShow Audio Renderer will accept (WAVEFORMATEXTENSIBLE). This is done
>> without altering the audio data in any way.
>>
>> http://www.chrisnet.net/msdn/AudioTypeConvert.zip
>>
>> Download it, Unzip it, and place the AudioTypeConvert.ax file in your
>> System32 folder.
>> Then open a Command Prompt and register it with this:
>>
>> regsvr32 c:\windows\system32\AudioTypeConvert.ax
>>
>> If you want to remove it at anytime just unregister it with:
>>
>> regsvr32 /U c:\windows\system32\AudioTypeConvert.ax
>>
>>
>
From: Michael on
Thanks tons for this info, Noel. Very odd that M$ apparently doesn't want
its own driver models (hence its own apps) to properly recognize a file
format they created and used to fully support. :-\

http://msdn2.microsoft.com/en-us/library/ms789667.aspx
The subset of WAVEFORMATEX PCM formats that KMixer supports differs between
Windows releases, as shown in the following table.
Windows Release Packed Sample Sizes Number of Channels
Windows 98 "Gold" 8, 16, 24, and 32 bits Multichannel
Windows 98 SE 8 and 16 bits only Mono and stereo only
Windows 98 SE + hotfix 8, 16, 24, and 32 bits Mono and stereo only
Windows 2000 8 and 16 bits only Mono and stereo only
Windows Me 8, 16, 24, and 32 bits Mono and stereo only
Windows XP and later 8 and 16 bits only Mono and stereo only

I liked especially the bit about the M$ rep who admitted not understanding
such a basic failure in the OS he's supposed to support. :-)

Noel Borthwick wrote:

> Interesting. I've known about the WMP incompatibility with 24 bit audio
> files, but didn't know someone wrote a filter to circumvent this. A long
> time ago my machine somehow started playing 24 bit wave files from SONAR -
> most likely I acquired a filter like this through some application I
> installed. I spoke to someone from MS once and he was very puzzled by how
> my version of WMP played these 24 bit audio files and his didn't :-)
>
> Some background about 24 bit audio and this format to explains the history
> of this infamous problem. Years ago (90's) when audio editors like
> SoundForge first started supporting 24 bit audio these files were written
> with the classic WAVEFORMATEX header with the bit depth set to 24 bits.
> For some reason Microsoft has stubbornly failed to acknowledge this a
> valid wave format and prefers the file to be authored with a
> WAVEFORMATEXTENSIBLE header. A few years ago when we were adding surround
> support (which requires a WAVEFORMATEXTENSIBLE header), out of curiosity
> I changed the way SONAR wrote 24 bit audio to write it in the MS blessed
> way. Unfortunately all hell broke loose since only SONAR and a couple of
> applications were able to read these files. It turned out that
> WAVEFORMATEXTENSIBLE was very poorly supported by most DAW's and audio
> editors. They would either barf on the file or read it as an incorrect
> format. So I switched back to writing them in classic WAVEFORMATEX. I'd
> much rather other apps read these files than MediaPlayer thank you <g>
>
> Its pretty strange that Microsoft has stubbornly refused to support these
> files despite the fact that the entire audio industry writes them this
> way.
> Noel
>
> "Shawn O'Connor" <SO(a)comcast.net> wrote in message
> news:7c6dnUk11vQSqGzYnZ2dnUVZ_t2tnZ2d(a)comcast.com...
>> This might help.....
>>
>> Legacy HD Audio Filter - Many audio processing applications still produce
>> high-definition audio such as 24bit/96kHz in a legacy WAV format. By
>> default
>> DirectShow players (such as Media Player) won't be able to play these
>> files
>> as the Audio Renderer refuses to accept this legacy type even though it
>> is perfectly capable of playing it. This filter registers itself as being
>> able
>> to handle this legacy format, and at the same time converts to a format
>> the
>> DirectShow Audio Renderer will accept (WAVEFORMATEXTENSIBLE). This is
>> done without altering the audio data in any way.
>>
>> http://www.chrisnet.net/msdn/AudioTypeConvert.zip
>>
>> Download it, Unzip it, and place the AudioTypeConvert.ax file in your
>> System32 folder.
>> Then open a Command Prompt and register it with this:
>>
>> regsvr32 c:\windows\system32\AudioTypeConvert.ax
>>
>> If you want to remove it at anytime just unregister it with:
>>
>> regsvr32 /U c:\windows\system32\AudioTypeConvert.ax


From: Noel Borthwick on
Actually in their defence, they claim that 24 bits is not an appropriate
format to describe using WAVEFORMATEX. That doesn't justify not supporting
millions of files already in the field, but..

http://msdn2.microsoft.com/en-us/library/ms713497.aspx

"Formats that support more than two channels or sample sizes of more than 16
bits can be described in a WAVEFORMATEXTENSIBLE structure, which includes
the WAVEFORMAT structure."



"Michael" <muirhead(a)haidagwaii.net> wrote in message
news:fvedndK_mp9N62nYnZ2dnUVZ_smonZ2d(a)qcislands.net...
> Thanks tons for this info, Noel. Very odd that M$ apparently doesn't
> want its own driver models (hence its own apps) to properly recognize a
> file format they created and used to fully support. :-\
>
> http://msdn2.microsoft.com/en-us/library/ms789667.aspx
> The subset of WAVEFORMATEX PCM formats that KMixer supports differs
> between Windows releases, as shown in the following table.
> Windows Release Packed Sample Sizes Number of Channels
> Windows 98 "Gold" 8, 16, 24, and 32 bits Multichannel
> Windows 98 SE 8 and 16 bits only Mono and stereo only
> Windows 98 SE + hotfix 8, 16, 24, and 32 bits Mono and stereo only
> Windows 2000 8 and 16 bits only Mono and stereo only
> Windows Me 8, 16, 24, and 32 bits Mono and stereo only
> Windows XP and later 8 and 16 bits only Mono and stereo only
>
> I liked especially the bit about the M$ rep who admitted not understanding
> such a basic failure in the OS he's supposed to support. :-)
>
> Noel Borthwick wrote:
>
>> Interesting. I've known about the WMP incompatibility with 24 bit audio
>> files, but didn't know someone wrote a filter to circumvent this. A long
>> time ago my machine somehow started playing 24 bit wave files from
>> SONAR -
>> most likely I acquired a filter like this through some application I
>> installed. I spoke to someone from MS once and he was very puzzled by
>> how
>> my version of WMP played these 24 bit audio files and his didn't :-)
>>
>> Some background about 24 bit audio and this format to explains the
>> history
>> of this infamous problem. Years ago (90's) when audio editors like
>> SoundForge first started supporting 24 bit audio these files were written
>> with the classic WAVEFORMATEX header with the bit depth set to 24 bits.
>> For some reason Microsoft has stubbornly failed to acknowledge this a
>> valid wave format and prefers the file to be authored with a
>> WAVEFORMATEXTENSIBLE header. A few years ago when we were adding surround
>> support (which requires a WAVEFORMATEXTENSIBLE header), out of curiosity
>> I changed the way SONAR wrote 24 bit audio to write it in the MS blessed
>> way. Unfortunately all hell broke loose since only SONAR and a couple of
>> applications were able to read these files. It turned out that
>> WAVEFORMATEXTENSIBLE was very poorly supported by most DAW's and audio
>> editors. They would either barf on the file or read it as an incorrect
>> format. So I switched back to writing them in classic WAVEFORMATEX. I'd
>> much rather other apps read these files than MediaPlayer thank you <g>
>>
>> Its pretty strange that Microsoft has stubbornly refused to support these
>> files despite the fact that the entire audio industry writes them this
>> way.
>> Noel
>>
>> "Shawn O'Connor" <SO(a)comcast.net> wrote in message
>> news:7c6dnUk11vQSqGzYnZ2dnUVZ_t2tnZ2d(a)comcast.com...
>>> This might help.....
>>>
>>> Legacy HD Audio Filter - Many audio processing applications still
>>> produce
>>> high-definition audio such as 24bit/96kHz in a legacy WAV format. By
>>> default
>>> DirectShow players (such as Media Player) won't be able to play these
>>> files
>>> as the Audio Renderer refuses to accept this legacy type even though it
>>> is perfectly capable of playing it. This filter registers itself as
>>> being
>>> able
>>> to handle this legacy format, and at the same time converts to a format
>>> the
>>> DirectShow Audio Renderer will accept (WAVEFORMATEXTENSIBLE). This is
>>> done without altering the audio data in any way.
>>>
>>> http://www.chrisnet.net/msdn/AudioTypeConvert.zip
>>>
>>> Download it, Unzip it, and place the AudioTypeConvert.ax file in your
>>> System32 folder.
>>> Then open a Command Prompt and register it with this:
>>>
>>> regsvr32 c:\windows\system32\AudioTypeConvert.ax
>>>
>>> If you want to remove it at anytime just unregister it with:
>>>
>>> regsvr32 /U c:\windows\system32\AudioTypeConvert.ax
>
>


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13
Prev: Please help
Next: Midi Latency -Recording only