Ove Kaaven wrote:
>
> On Mon, 5 Jun 2000, Bradley Baetz wrote:
>
> > Also, the msacm/msacm32 dll pair is used for the audio compression
> > manager. In order to do conversions the builtin versions have to be
> > used.
>
> Are you sure that's what it says? The documentation is quite ambiguous at
> that point.
This is from discussions with Eric earlier this year.
I think its ambiguous because its confusing :) That file is no longer
really a status file, and should probably be split up a bit.
>
> > Hows this for some text, paraphrased from the docs:
>
> That text apparently applies to msacm.drv, and in my interpretation says
> that built-in msacm.drv only works if you also use built-in msacm and
> msacm32.
That's probably right, although I haven't tested that. If that is the
case, then is it possible for the three files to be linked with
[DllTriplet], or a pair of dllpair entries in whatever file those have
moved to? Does the code handle entries appearing twice?
>
> The section below that says native of all three also seems to work ok.
Native of all three work, but you need builtin (of all three) to use
native codecs. Not sure why though. I think it has something to do with
the way the OSS sound driver is constructed.
In order to use native ACM drivers to play non PCM files, you must use
-dll msacm,msacm32,msacm.drv=b. Note that this code is not complete
yet, and may cause problems. sndrec32 and mplayer from Win95 appear
to
work reasonably well though.
is the paragraph from 1.6.1 of the documentation file, which I
paraphrased.
Its just a minor issue, but it did confuse me, which is why I suggested
adding in a few sentences. I wasn't expecting native codecs to require
builtin dlls in order to work.
Bradley
