You can do this. I'm sure you can setup two encoders in SAM. One setup to stream to streamerp2p and another setup to stream to the shoutcast / icecast server. Normaly you do this to provide two different streams, a low bandwidth stream for modem users and high bandwidth stream for ADSL.
You can also stream to shoutcast only and connect streamer as a relay. You can find this setting under [Bcast] / Sources. This way you don't need to encode two streams and it helps to keep CPU usage moderate.
If you only want to monitor your stream you can activate "Lan unicast" in the IP/Ports Tab of the Config section. Means you can connect over the local lan to the unicast port of streamerp2p.
Example:
- TCP Audio (in use) is port 8000 in streamer
- your stream id is something like 'aefgdcc9862fa570'
Now you can open your stream with Winamp or any audioplayer supporting your streamtype using
http://<IP_OF_YOUR_STREAMSERVER>:8000/ceffdcc9831fa560.pls
You can also listen local, on the same pc streamer is running on (works without lan unicast enabled):
mp3 / mp3Pro:
http://127.0.0.1:8000/streamer.mp3ogg:
http://127.0.0.1:8000/streamer.oggaac / aac+:
http://127.0.0.1:8000/streamer.aacnsv:
http://127.0.0.1:8000/streamer.nsvBut if you use local monitoring you have to take care the monitored audio isn't captured and rebroadcasted again (can be a issue depending how you capture audio).
In streamer v1.47 there is a bug causing two streamers in the same local lan can't listen to each other. using a second streamer installation to listen to your broadcast can be a problem. It works fine with the latest beta 2.06.