Think about musical orchestrations of change

[sewardlee337]

LJ to think about musical orchestrations of change. Will build 3-5 different points of change within each musical genre. Also think about other ways to denote change in information musically.

[sewardlee337]

@lj42 - This is related to our conversation about different types of data:

http://www.ucl.ac.uk/ich/short-courses-events/about-stats-courses/stats-rm/Chapter_2_Content/Types_of_Data

[lj42]

Ah that's actually one of the best things I've read on explaining different types of data - thanks for that. it's incredibly useful

[lj42]

SONIFICATION PHASE 01: identify more than just one thing at once by listening. For the program to work the way I imagine to be the most helpful, and easy to program, see below:

1. create .wav files (unless anyone prefers .mp3 / aiff etc files, can convert to any musical file as required)

2. In the first instance, music for our PCAP project will consist of

   • constant, looping PEDAL NOTES; and
   • intermittent, data-dependent DINGS (Backonym: Data-Inferred Notes Generated by State)

Detail: PEDAL NOTES - play in loops for each state: Think of these as ‘backdrops’ for each state, giving a broad overview of what the current system state is.

EXAMPLE PEDAL NOTES STABLE / QUIET: Stable_A and StableB (alternating for a reason) MONITORING: Green YELLOW: Yellow
RED: Red

Feel free to suggest different filenames and I shall name them accordingly. I could put P in front of each of these to denote that they are pedal notes. PStable_A for example. There are 2x Stable backdrops so the user doesn’t lose the sense that there is music playing.

DINGS - one-shot samples triggered by data activity. There can be >1 kind of DING for each state to help delineate what could be happening aurally - these can also be panned left and right to denote west/east co-ordinates. As to the sounds - these can be mapped to an individual attack with frequency or volume. Do we have different ports that we should be listening for traffic on? This can be easily denoted through using different sounds. The more important a port, the more ‘urgent’ the sound. The use of these sounds depends largely on a) behaviour of data and b) the most ‘useful’ way for humans to receive it.

EXAMPLE DINGS DING_Stable_A_01, DING_Stable_A_02, DING_Stable_B_01, etc DING_Green_01, DING_Green_02 etc. DING_Yellow_01 DING_Red_01, DING_Red_02, DING_Red_03 etc

Re: Filename I’ve called these DINGs but again let me know if you think there is a better term, just making things up as I go.

EXTRA NOTES

FUTURE THOUGHTS LOCATION: At the start of the program it might be nice to enter our co-ords so that in UK/US we can experience movement to the left and right for each data point location. Not essential at the moment

GENRE: we can change genres and make something more ‘dance’ ‘classical’ ‘metal’ depending on preference. Perhaps for different tasks / datanaut preferences we can look at creating other soundscapes

[lj42]

I've created the following musical samples that we can call during our program

Files on the left will play in a loop Files on the right are trigger files and will play when a) a particular event takes place b) a threshold is reached c) toggles state or d) anything else noteworthy

[lj42]

(the numbers at the end of each filename denote how many bars each sample is. BPM is 90)

[sewardlee337]

Regarding genres/soundscapes, this seems analogous to how, in data visualization libraries, you can often choose custom color palettes for your graphs. For example:

https://matplotlib.org/tutorials/colors/colormaps.html

https://seaborn.pydata.org/tutorial/color_palettes.html