CONFIGURATION

As of HASE BETA2, all HASE components now have command-line configuration to simply using the components across multiple systems. The following tables document the configuration options for each component.

HASE - hase.exe

Tip: Set a log file path. HASE generates a log file EACH time it is run and the system defaults to the HASE application directory.

Option Description DEFAULT Example
/logpath Logfile path application directory /logpath:c:\program files\hase\logs
/scriptfile Script filename sample.has in application directory /scriptfile:c:\program files\hase\myscript.has
/key Product Key NO KEY INSTALLED /key:1234-1234-1234-1234
/gatewayfile Gateway Text File - this file lists each socket server loaded by HASE gateway.txt in application directory /gatewayfile:c:\program files\hase\mygateway.txt
/port Socket Port for HASE Commands 12112 /p:12345
/visible Application Visible? TRUE (1) /visible:0

 

Slink-e Socket Server - sss.exe

Tip: Set a log file path. SSS generates a log file EACH time it is run and the system defaults to the HASE application directory.

Option Description Default Example
/logpath Logfile path application directory /logpath:c:\program files\hase\logs
/autocdj Autoload CDJ Devices TRUE (1) /autocdj:0
/playlistpath Path for CDJ Playlists application path /playlistpath:c:\playlists
/lowlevel Autoload Lowlevel FALSE (0) /lowlevel:1
/port Socket Port for Commands / Events 12111 /port:12345
/httpport Socket Port for HTTP functions 12180 /httpport:80
/visible Application Visible? TRUE (1) /visible:0

 

Text2Speech Socket Server - tts_ss.exe

Tip: Set a log file path. TTS_SS generates a log file EACH time it is run and the system defaults to the HASE application directory.

Option Description Default Example
/logpath Logfile path application directory /logpath:c:\program files\hase\logs
/voice Text2Speech Voice (You can find in the Microsoft speech control panel if installed) Mary /voice:Mike
/port Socket Port for Commands / Events 12113 /port:12345
/visible Application Visible? TRUE (1) /visible:0

 

gateway.txt

This text file contains a list of all socket servers that will be loaded into the scripting engine. the socket server will be referenced as an object in the script by the first column which serves as an identifier. The second column contains the hostname of the machine running the socket server. The third column contains the port that is bound to the socket server. The name in the first column will be used when the socket server is bound to the script control. Inside your script, you would reference the following socket servers as slinke_ss, tts_ss, and wm_ss respectively.

example of gateway.txt:

slinke_ss,myserver,12111

tts_ss,myserver,12113

wm_ss,someotherpc,12114

example of script sending a command to the tts_ss socket server:

        tts_ss.command "SPEAK Hello, this is a test"