You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding 2 channel (stereo) audio delivery to FlyVR. This involves modifying soundserver mostly on the backend side. This shouldn't be too difficult. I think the stimulus code already handles mixing multiple signals into one buffer for sending to the device. This was working for the DAQ previously at least. There is a question of what the user interface for specifying multiple channels should be? Should stimulus entries have an optional channel field?
The text was updated successfully, but these errors were encountered:
hardware: a pair of earbuds plugged into the sound card
Example of why we want 2 channel (stereo) audio: the male fly moves around during courtship, so I might want that song to also "move" from left earbud to right earbud (so, one playlist item, with different sound on each earbud). A second example is simply testing for neural responses that come from the left, or from the right (so these would be separate playlist items; maybe even the exact same playlist item, but played only thru one earbud speaker).
I wonder if a good solution is for the user to always provide 2 columns of audio data (left earbud, right earbud). I like your idea of having an optional channel field (channel 1, channel 2, or both).
Adding 2 channel (stereo) audio delivery to FlyVR. This involves modifying soundserver mostly on the backend side. This shouldn't be too difficult. I think the stimulus code already handles mixing multiple signals into one buffer for sending to the device. This was working for the DAQ previously at least. There is a question of what the user interface for specifying multiple channels should be? Should stimulus entries have an optional channel field?
The text was updated successfully, but these errors were encountered: