Convert.conf

[Tim Long]

Been looking at the new transcoding features, great work everyone.
Clearly, you have been listening to your users.

The format of the convert.conf file _almost_ makes sense, but I need one
clarification...

Am I correct in thinking that items between the $ signs, like $lame$ are
environment variables? As a Windows user, I'm used to seeing them
between % signs, %lame% etc. I assume the variable is meant to contain
the full path of the encoder executable, right?

If i just define the appropriate environment variable in Windows, can I
assume that the perl platform will 'just know what I mean' and take care
of the $/% thing?

Regards,
Tim Long

DarkManager <http://groups.yahoo.com/group/DarkManager> - automate the
acquisition of your reduction frames
ASCOM Telescope driver for Takahashi Temma
<http://software-y-ddraig.long-family.com/Temma/ASCOMTemma.htm>

[dean]

Hi Tim,


On Nov 18, 2003, at 8:33 AM, Tim Long wrote:
> Been looking at the new transcoding features, great work everyone.
> Clearly, you have been listening to your users.
We try. :)

> The format of the convert.conf file _almost_ makes sense, but I need
> one clarification...
>
> Am I correct in thinking that items between the $ signs, like $lame$
> are environment variables? As a Windows user, I'm used to seeing them
> between % signs, %lame% etc. I assume the variable is meant to contain
> the full path of the encoder executable, right?
Sort of. The server uses the path to look for an executable matching
what's between the $'s. It does some platform-specific extensions
(like adding .exe on windows and looking in some special specific
folders.)

The simplest thing is to make sure that the executable is in your path
and you shoudl be good to go.

-dean