1. Here's the XML that specifies these associations in one of our apps
(not realplayer).
<List Name="Sel00">
<Var Title="14.4 K Modem"/>
<Var Value="14400"/>
</List>
<List Name="Sel01">
<Var Title="19.2 K Modem"/>
<Var Value="19200"/>
</List>
<List Name="Sel02">
<Var Title="28.8 K Modem"/>
<Var Value="28800"/>
</List>
<List Name="Sel03">
<Var Title="33.6 K Modem"/>
<Var Value="33600"/>
</List>
<List Name="Sel04">
<Var Title="56 K Modem"/>
<Var Value="34430"/>
</List>
<List Name="Sel05">
<Var Title="56 K Single ISDN"/>
<Var Value="57600"/>
</List>
<List Name="Sel06">
<Var Title="112 K Dual ISDN"/>
<Var Value="115200"/>
</List>
<List Name="Sel07">
<Var Title="256 Kbps DSL/Cable"/>
<Var Value="262200"/>
</List>
<List Name="Sel08">
<Var Title="300 Kbps DSL/Cable"/>
<Var Value="307200"/>
</List>
<List Name="Sel09">
<Var Title="512 Kbps DSL/Cable"/>
<Var Value="524300"/>
</List>
<List Name="Sel10">
<Var Title="T1/LAN"/>
<Var Value="1544000"/>
</List>
<List Name="Sel11">
<Var Title="10 Mbps LAN"/>
<Var Value="10485800"/>
</List>
2. NoAsyncDNS=1 turns off the creation of another process.
Unfortunately, when you link with pthreads, you always get at least 2
threads, I think. iff you don't link with pthreads, you dlopen rmacore
with RTLD_LAZY option, and you turn off all the prefs, you might get a
working core with only 1 thread.
3. Yes, good point
SoundDriver=0 ..... regular OSS
SoundDriver=1 ..... ESD
SoundDriver=2 ..... braindead OSS for bad audio driver
implementations.
I think you need to restart after changing this pref.
Cheers,
Pete
On Mon, 26 Feb 2001, Matthew Campbell wrote:
> Thank you for the configuration details, Pete. Three questions:
>
> 1. In RealPlayer, some of the bandwidth values are given names like
> Cable, T1, and T3. Can you tell us which names are associated with
> which numbers, so that info can be incorporated in a text-based
> configuration utility?
>
> 2. Are there any threading options other than the ones you mentioned?
> I ask because I turned off both NetworkThreading and ThreadedAudio,
> and there are still extra threads when I run TRPlayer. TRPlayer
> doesn't do any multi-threading directly, so those extra threads must
> be coming from RealPlayer client core. And as you mentioned, it's
> helpful to turn off any multi-threading when debugging with GDB.
>
> 3. I was told that there's an option in RealPlayer under Linux to
> select the method of sound output to use (either EsounD or the normal
> audio device). Can you give us the details on that so that TRPlayer
> can be used with EsounD?
>
> Thank you.
>
> --
> Matt Campbell <http://www.pobox.com/~mattcampbell/> ICQ #: 33005941
>
