Run the sam broadcaster setup, use firebird sql, then when it gives the two radio buttons, choose the custom settings one, and in the options that show there, select the embedded one.Ĩ. When the winetricks script is done you should configure wine to your liking if necessary.ħ. In the window that comes up, choose gecko, msxml3, and richedit20Ħ. Open a terminal in the directory with the winetricks script.ĥ. Download the winetricks sh script, remember where you save it, and name it 'winetricks.sh'ģ. With that in mind, a multi-core proc (4 cores or more) should be able to handle SAM with all features turned on.įOR USE WITH FIREBIRD DATABASE (written by a previous maintainer, kept for archive): prefer mysqlĢ. I did switch to a dual core and but still the average load was higher than acceptable levels so I decided to leave all statistics relays turned off and implemented a third party solution of my own to capture my stats. I had to disable statistic relays to bring down the CPU usage to an acceptable level for single core proc. I originally tested on a single core dedicated box, however resource usage was high and the system was unstable. I was unable to install gecko or msxml3 (as the instructions on winehq state are necessary), However I was still able to install and run SAM without them. I have not tested everything, but I have had no show stopping issues for anything I've tested. All the essential features: Playback, Encoding/Streaming, Relay Statistics, DSPs, FX, Playlist, Mysql connections (remote and local), PAL Script Execution, Playlist Rotation, Remote requests.

Sam broadcaster 4.2.2