Hi lar282,
If I understand your question, maybe this will help:
On the client, in F2 (after connecting to the server) check to make sure the server's audio zones appear under the "Audio" tab as "Internal Audio Zones".
If you are properly connected to the server, you should see "default" followed by the names of the audio zones on the server.
You can now play music on the server from the client.
Once you can see the server's audio zones in setup, you can use a simple event to "cycle" through the available zones.
(Create a button that tells you what zone you are controlling, and also acts as a "step through the available zones" event.)
The button text can be something like "Current Zone: %zone>current%", and the event you assign to it is "music:zone next"
Now put that button on any screen where you're controlling audio or getting audio feedback like "nowplaying info", and the controls and info will correspond to whatever is on "%zone>current%"
Here's my typical setup:
Movies and music stored on the server.
Server has 4 audio "zones" that feed distributed audio system and "telephone music on hold."
4 "Client machines" each play movies and music locally, and have the ability to output music from any of the server's 4 audio zones.
The server's 4 audio zones (I call use them as streams: "Mom's", "Dad's", "Kid's", and "Bkgnd") all appear on each of the clients in the system.
I use something similar to the suggested button above to indicate which "zone/stream" is being controlled.
One of the best things about the set-up is that XLobby DOES NOT need separate screens/buttons for each audio zone!
When playing music on the "Local" zone, everything happens locally; if a "server zone" is selected all the commands get sent to the server automatically.
If you are in front of the client, it looks like everything is happening on the client (good for waf), but the client is actually sending "server commands"
The result is that the client is always updated in real-time, and the server doesn't have to have the same pages as the client.
In-fact, the server runs 1024x768 touch-screens on VGA, while the clients all run 1280x720 HDTVs through a matrix switcher on component.
Not sure if your hardware can run a "full/fat" V3, but if it can, you'll never want to go back to "static" screens that need "refresh" commands and never really give you real-time updates.
Not sure how this applies to playing movies on the server from a client since I don't have any reason to even try, but for audio it rocks!