How is the config file named and where is it on the system?
On Mon, 26 Feb 2001, Peter Godman wrote:
> Hello. Here's some information on the config file. I marked default
> values with (!). Sorry I haven't located a file I can give you yet about
> presets/favorites. We should coordinate on this though because RP9 for
> unix will have favorites again.
>
> Attached is an explanation I just wrote of the preferences you're likely
> to want to change.
>
> Cheers,
> Pete
>
> Bandwidth: bandwidth that player should attempt to use for streams.
>
> possible values:
> 14400 19200 28800 33600 34430 57600 115200 262200 307200 524300
> 1544000 10485800
>
> MaxBandwidth: most bandwidth the player should use to play a stream (this
> may be higher than bandwidth because there will be streams at higher
> rates.
>
> possible value:
> as above
>
> PNAProxySupport: (0!/1) use a pna proxy
> PNAProxyHost: (string) host name of pna proxy
> PNAProxyPort: (port number) port number of pna proxy
>
> RTSPProxySupport (0!/1)
> RTSPProxyHost (same as PNA but for RTSP)
> RTSPProxyPort
>
> HTTPProxySupported (0!/1)
> HTTPProxyHost
> HTTPProxyPort
>
> NoProxyFor (list of comma-separated hostnames that no proxy should be used
> for (local hosts))
>
> AttemptRTSPvMulticast: (0/1!) Turn on if you have multicast internet
> AttemptRTSPvUDP: (0/1!) " udp "
> AttemptRTSPvTCP: (0/1!) " tcp "
>
> AttemptRTSPvHTTPOnly: only use http for streaming (don't use unless you
> have a strict firewall that only allows http)
>
> AttemptPNAvMulticast (0/1!)
> AttemptPNAvUDP (0/1!)
> AttemptPNAvTCP (0/1!)
>
> MulticastTimeout: (number (4000!)) wait this many milliseconds before
> determining that we don't have multicast available
> (by no packets arriving).
>
> AttemptPNAvHTTPOnly: only use http for PNA: for firewall situations
>
> UDPTimeout: Give up on UDP after this many milliseconds... used for
> fallback to TCP in situations where UDP is not available (e.g. through IP
> masquerade on non-bridged DSL, etc.)
>
> UseUDPPort: (0!/1) Just use a list of UDP ports on my machine that I
> specify to receive content.
>
> UDPPort: (comma and dash-separated numbers) List of ports on my machine
> to use to receive content.
>
> PerfectPlayEntireClip: (0!/1) Buffer enough of the clip to ensure that
> there won't be any rebuffering during playback.
>
> PerfectPlayTime: (number) Buffer this many seconds of data to avoid
> rebuffering.
>
> Volume: audio volume to start player at (0-100).
>
> NoAsyncDNS: (0!/1) For debugging only... stops the creation of a
> separate process to handle DNS requests.
>
> NetworkThreading (0/1!) Turn on a threaded networking implementation.
> Turning this off may aid debugging.
>
> ThreadedAudio (0/1!) Turn on audio threading. Turning this off
> may aid debugging.
>
>
> On Sat, 24 Feb 2001, Matthew Campbell wrote:
>
> > Now that I've sent out the release announcement for TRPlayer 1.2.0, I
> > hope the whole version numbering mess is cleared up. Now I'd like to
> > start discussing future development of TRPlayer.
> >
> > At this point, I think TRPlayer has all of the basic features it needs
> > to be useful as a media player. Any other features added to TRPlayer
> > -- configuration options, bookmarks, volume control, etc. -- are
> > extras. However, there's one other thing that I've been asked to
> > create: a program to create and modify the configuration file that
> > RealPlayer's shared libraries use to determine the maximum stream
> > bandwidth, the available methods for connecting to a server, and some
> > other parameters. This configuration file is a plain-text file with a
> > simple format, so I could probably write such a configuration utility
> > in an interpreted language such as Python. However, I can't find any
> > documentation about this configuration file in the RealSystem SDK, so
> > I may need to figure out the possible values for the parameters on my
> > own (especially the bandwidth-related parameters).
> >
> > Once we have a utility to create and modify the RealPlayer
> > configuration file, then I can work on other features that have been
> > suggested on the mailing list. What additional features would be most
> > useful? We've discussed bookmarks before; I still need to get some
> > more information from RealNetworks about the XML-based file format
> > that they use for bookmarks or presets.
> >
> > This project has been dormant long enough; I'd like to bring it backto
> > life and continue to make TRPlayer more useful.
> >
> > --
> > Matt Campbell <http://www.pobox.com/~mattcampbell/> ICQ #: 33005941
> >
>
>
