Skip to content

W
wine-winehq
Commit 4acad25f authored by Eric Pouech's avatar Eric Pouech Committed by Alexandre Julliard
Browse files
Options

Documentation updates.

parent 036bb85b
Hide whitespace changes
Inline Side-by-side
Showing with 68 additions and 76 deletions
documentation/multimedia.sgml
View file @ 4acad25f
...@@ -30,8 +30,8 @@ ...@@ -30,8 +30,8 @@
</para> </para>
<para> <para>
There are two specific low level drivers (one for wave input/output, There are two specific low level drivers (msacm.drv for wave input/output,
another one for MIDI output only), whose role is: midimap.drv for MIDI output only), whose role is:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
...@@ -40,7 +40,9 @@ ...@@ -40,7 +40,9 @@
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
add the possibility to convert streams (ie ADPCM =&gt; PCM) add the possibility to convert streams (ie ADPCM =&gt;
PCM) (this is useful if the format required by the
application for playback isn't supported by the soundcard).
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -125,8 +127,13 @@ ...@@ -125,8 +127,13 @@
<title>Other sub systems</title> <title>Other sub systems</title>
<para> <para>
No other is available. Could think of Sun Audio, remote audio systems Support is also provided for ALSA, aRts, NAS, Jack,
(using X extensions, ...), ALSA, EsounD, ArTs... AudioIO, but with less intensive debugging than the OSS.
</para>
<para>
EsounD isn't supported yet. ALSA support still needs a
couple of refinements.
</para> </para>
</sect3> </sect3>
...@@ -202,14 +209,16 @@ ...@@ -202,14 +209,16 @@
<title>Other sub systems</title> <title>Other sub systems</title>
<para> <para>
Could support other MIDI implementation for other sub systems (any Could support other MIDI implementation for other sub
idea here ?) systems (ALSA, any other idea here ?)
</para> </para>
<para> <para>
Could also implement a software synthesizer, either inside Wine or Could also implement a software synthesizer, either inside Wine or
using using MIDI loop back devices in an external program (like using using MIDI loop back devices in an external program (like
timidity). The only trouble is that timidity is GPL'ed... timidity). The only trouble is that timidity is GPL'ed...
Note: this could be achieved using the ALSA sequencer and
Timidity being used as a server.
</para> </para>
</sect3> </sect3>
...@@ -498,7 +507,7 @@ ...@@ -498,7 +507,7 @@
The currently best implementation is the MCI CDAUDIO driver that can The currently best implementation is the MCI CDAUDIO driver that can
be found in dlls/winmm/mcicda/mcicda.c. The implementation is mostly be found in dlls/winmm/mcicda/mcicda.c. The implementation is mostly
complete, there have been no reports of errors. It makes use of complete, there have been no reports of errors. It makes use of
misc/cdrom.c Wine internal cdrom interface. dlls/ntdll/cdrom.c Wine cdrom interface.
This interface has been ported on Linux, FreeBSD and NetBSD. (Sun This interface has been ported on Linux, FreeBSD and NetBSD. (Sun
should be similar, but are not implemented.) should be similar, but are not implemented.)
</para> </para>
...@@ -521,12 +530,6 @@ ...@@ -521,12 +530,6 @@
configuration scheme) configuration scheme)
</para> </para>
</listitem> </listitem>
<listitem>
<para>
The DLL is not cleanly separated from the NTDLL DLL. The CDROM
interface should be exported someway (or stored in a Wine only DLL)
</para>
</listitem>
</itemizedlist> </itemizedlist>
</para> </para>
...@@ -762,16 +765,6 @@ ...@@ -762,16 +765,6 @@
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
add clean-up mechanisms when process detaches from MM DLLs
</para>
</listitem>
<listitem>
<para>
prepare for the 16/32 big split
</para>
</listitem>
<listitem>
<para>
check thread-safeness for MMSYSTEM and WINMM entry points check thread-safeness for MMSYSTEM and WINMM entry points
</para> </para>
</listitem> </listitem>
...@@ -799,9 +792,9 @@ ...@@ -799,9 +792,9 @@
<para> <para>
MCI drivers are seen as regular Wine modules, and can be loaded (with MCI drivers are seen as regular Wine modules, and can be loaded (with
a correct load order between builtin, native, so), as any a correct load order between builtin, native), as any other DLL.
other DLL. Please note, that MCI drivers module names must bear the Please note, that MCI drivers module names must bear the .drv
.drv extension to be correctly understood. extension to be correctly understood.
</para> </para>
<para> <para>
...@@ -867,13 +860,6 @@ ...@@ -867,13 +860,6 @@
using binary command line. using binary command line.
</para> </para>
</listitem> </listitem>
<listitem>
<para>
the Wine native MCI drivers should use the mmThreadXXX API (but since
all built-in MCI drivers are 32 bit, this would require a special
flag to mark 32 bit entry points)
</para>
</listitem>
</itemizedlist> </itemizedlist>
</para> </para>
...@@ -987,6 +973,13 @@ ...@@ -987,6 +973,13 @@
model model
</para> </para>
</listitem> </listitem>
<listitem>
<para>
we need also a generic tool to let the end user pick
up his/her driver depending on the hardware present on the machine.
model
</para>
</listitem>
</itemizedlist> </itemizedlist>
</para> </para>
...@@ -1222,35 +1215,35 @@ Kernel space | Client applications ...@@ -1222,35 +1215,35 @@ Kernel space | Client applications
</sect1> </sect1>
<sect1 id="msacm"> <sect1 id="msacm">
<title>MS ACM Dlls</title> <title>MS ACM Dlls</title>
<sect2> <sect2>
<title>Contents</title> <title>Contents</title>
<para>tbd</para> <para>tbd</para>
</sect2> </sect2>
<sect2> <sect2>
<title>Status</title> <title>Status</title>
<para>tbd</para> <para>tbd</para>
</sect2> </sect2>
<sect2> <sect2>
<title>Caching</title> <title>Caching</title>
<para> <para>
The MSACM/MSACM32 keeps some data cached for all known ACM The MSACM/MSACM32 keeps some data cached for all known ACM
drivers. Under the key drivers. Under the key
<screen> <screen>
Software\Microsoft\AudioCompressionManager\DriverCache\&lt;driver Software\Microsoft\AudioCompressionManager\DriverCache\&lt;driver
name&gt; name&gt;
</screen> </screen>
are kept for values: , are kept for values:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
aFormatTagCache which contains an array of aFormatTagCache which contains an array of
DWORD. There are two DWORDs per cFormatTags DWORD. There are two DWORDs per cFormatTags
entry. The first DWORD contains a format tag entry. The first DWORD contains a format tag
...@@ -1258,37 +1251,36 @@ Kernel space | Client applications ...@@ -1258,37 +1251,36 @@ Kernel space | Client applications
size for a WAVEFORMATEX structure. size for a WAVEFORMATEX structure.
(Fields dwFormatTag and cbFormatSize from (Fields dwFormatTag and cbFormatSize from
ACMFORMATDETAILS) ACMFORMATDETAILS)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
cFilterTags contains the number of tags supported by the driver cFilterTags contains the number of tags supported by the driver
for filtering. for filtering.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
cFormatTags contains the number of tags support cFormatTags contains the number of tags support
by the driver for conversions. by the driver for conversions.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
fdwSupport (the same as the one returned from fdwSupport (the same as the one returned from
acmDriverDetails). acmDriverDetails).
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</para> </para>
<para> <para>
The cFilterTags, cFormatTags, fdwSupport are the same The cFilterTags, cFormatTags, fdwSupport are the same
values as the ones returned from acmDriverDetails values as the ones returned from acmDriverDetails
function. function.
</para> </para>
</sect2> </sect2>
</sect1> </sect1>
</chapter> </chapter>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment