Official RIVA thread

[Dean Roddey]

I guess I was kind of looking at it more from the perspective that some (potentially important) RIVA clients might not have any such ability to do this but would have ways to make simple sounds built into them. In that case, you would set up the RIVA specific templates not to point to actual paths, but to just use some identifying keyword. They don't actually have to be paths per se.

Those would then be used to trigger available built in sounds on the target device. I was thinking of like set top boxes in the future and things like that, or some these smarter remote controls that are showing up.

The way it has worked in the past is that it's assumed that the thing to play back will be availble on the client where the playback occurs. The path is interpreted as a local path. For instance, the back end may be a Windows Server machine that doesn't have the same files as the Vista/Win7 clients do, so it couldn't serve them up without having to move those files to the server.

So it's kind of tricky either way.