Sound objects should contain sound samples to be played on a given schedule, or on command from the local object on the server to the remote object on the client. If a sound object also has an "a3dl:object3d" type, then it could be spatialized in 3d space by the client. The tricky part is how to achieve approximate synchonization between all clients.

See also MODs for inspiration.

Voice chat?

d

  • Should sound store current state in a property, or send special play, pause,
    • etc. messages? How is current time point stored? How can new clients connect?
  • Maybe a hybrid: use messsages for play, pause, etc. but new clients can
    • query current state (and recieve e.g. play message containing starting time point in the stream).
  • One question, is should we assume that VOS property updates are delivered to
    • the listener ASAP? Or should we say that messages are always delivered ASAP, but property updates may take some time? Does VOS need priority numbers on messages?
  • speech comm. using http://www.speex.org/ or something similiar.

MetaObjectsForSound (last edited 2007-02-14 18:42:35 by bnh-3-10)