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
Indigo tries using the image layer to index the sound layer as a first attempt. Depending how it goes, glue team can build something dedicated to sound in glue.
This will mean that the sonified cubes will act as layers in the image viewers, allowing us to use mouse over events independent of the spectrum-at-spaxel tool to trigger the sounds. This will also include having plot options know how to handle sound layers with some configuration options available in that plugin (slider for sound for each layer, ability to mute and unmute, etc.).
After discussion with glue folks (may need splitting into multiple tickets): the first pass of this could be an image layer consisting of lookup indices corresponding to the audio. The audio themselves would still live outside glue, perhaps in a dictionary with keys matching the labels of the layers containing a flat list of audio data. The image layers should either have the drawing methods overwritten to do nothing, or for a POC could just force the opacity to zero. Plot options should know to hide most options and only show "visible/audible" and volume (this might require subclassing the state or could be stored separately for the POC). The stylized layer icon should not show color, but somehow indicate that its an audio layer. Mouseover should skip audio layers in the iterator/top-layer logic. All mouseover events (removed from the tool) should then iterate through any enabled audio layers, use existing mouseover logic to get the index, retrieve the volume, mix all tracks, and play the audio.
Scope for this ticket: keeping the existing implementation for now, if a dev flag is enabled, when sonify also store the audio in a dictionary and create a transparent index layer and at least have a callback to lookup the index. Scope out follow-up tickets from plan above.
The text was updated successfully, but these errors were encountered:
stscijirahubjdat
changed the title
Create a data object for sonified cubes
Create a data object for sonified cubes - hack image layer first
Jan 9, 2025
Issue JDAT-4991 was created on JIRA by Jesse Averbukh:
Indigo tries using the image layer to index the sound layer as a first attempt. Depending how it goes, glue team can build something dedicated to sound in glue.
This will mean that the sonified cubes will act as layers in the image viewers, allowing us to use mouse over events independent of the spectrum-at-spaxel tool to trigger the sounds. This will also include having plot options know how to handle sound layers with some configuration options available in that plugin (slider for sound for each layer, ability to mute and unmute, etc.).
After discussion with glue folks (may need splitting into multiple tickets): the first pass of this could be an image layer consisting of lookup indices corresponding to the audio. The audio themselves would still live outside glue, perhaps in a dictionary with keys matching the labels of the layers containing a flat list of audio data. The image layers should either have the drawing methods overwritten to do nothing, or for a POC could just force the opacity to zero. Plot options should know to hide most options and only show "visible/audible" and volume (this might require subclassing the state or could be stored separately for the POC). The stylized layer icon should not show color, but somehow indicate that its an audio layer. Mouseover should skip audio layers in the iterator/top-layer logic. All mouseover events (removed from the tool) should then iterate through any enabled audio layers, use existing mouseover logic to get the index, retrieve the volume, mix all tracks, and play the audio.
Scope for this ticket: keeping the existing implementation for now, if a dev flag is enabled, when sonify also store the audio in a dictionary and create a transparent index layer and at least have a callback to lookup the index. Scope out follow-up tickets from plan above.
The text was updated successfully, but these errors were encountered: