Nhell yea
Ooh also nova, so i am creating a stardust client but im also creating a spatial audio library behind it, what do you think abt adding a standard spatial audio implementation to stardust fusion?
Nok so, spatial audio standardization isn't trivial
Nwe need to first come up with a prototype for it in stardust
Nthen we can look at putting it in fusion
Ni'm not opposed to the idea but we don't know what we need yet
Ook sure :D,, i was just making sure that would be something thats actually
Oin the scope of fusion
Nfusion is specifically for the stardust nodes
Nso if we want spatial audio to be built into the server (which i'm not sure it needs to be)
Nthen it'll be in fusion
Oi dont think its necessary either and i actually
Otalked abt this with saphira alot last night when she recommended having a spatial audio server that processes everything, but i think all that would do is increase latency
Oit would be better to be compiled into each client
Ni like the pipewire filter with stardust client
Nkeep in mind you can have 1 spatial audio processor in stardust as a client
Ois there not
Ohmm,, actually yea ig i could
Nthe way you'd do that is have pulse receivers on all the spatial audio sources containing the output channel and pid of the process
Opipewire also allows you to send custom messages between nodes, and i wonder if there would be a way for the orbs to be aware of which client its coming from using that
Nthen your client has a pulse sender that can see all those pulse receivers and set the filters on the pipewire nodes to it relative to the HMD
Nit's really elegant IMO
Nremember, pulse receivers' masks are sent to the pulse senders as well as their fields/positions
Nso that means you can use them as tags
Nnot just message sending
Nthis also means you can have global spatial audio settings
Nso you can flatten out sounds if you want in 1 place
Othat is fair
Nor change doppler shift amount
Nor mute individual audio sources visually :D
Nwhat do you think?
Ohmm,,,im not sure,
Nand the audio sources can suggest what volume/doppler they should be at to the spatial audio processor
Oooo thats a good idea
Nand the spatial audio processor can send any data back to them too
Oyea that actually addressed one problem i was abt to point out so XD
Npulse senders/receivers were unintentionally so hella OP in stardust
Ni didn't intend for them to be so varied but they can do keyboards, mice, accessibility, spatial audio, etc.
Ocan a clients nodes be aware of their position in global space, or only relative to the client root spatial
Nthere's no global space, but you can easily just get their position relative to the HMD
Ooh ok
Oyea thats all you need
Nthe audio processor can just look at all the audio sources and get their position/rotation relative to the HMD in 1 call
Ohow would i do that
Nfor each
PulseReceiver just do pulse_receiver.get_position_rotation_scale(client.hmd());Ni have docs
Nthat i can send to people!!
N:0
O:0
