Table of Contents

1. Introduction

1.1 What is Healing Soundscapes?

Healing Soundscapes is a project developed by the Ligeti Center in collaboration with the University Hospital Hamburg-Eppendorf (UKE). The project implements an intelligent speaker system to be used in hospital waiting areas and operation rooms. Music therapists, composers, programmers, patients and doctors collaborate in the development of soundscapes that ensure to improve patients well-being in waiting areas as well as help doctors to concentrate during operations.

1.2 The GUI

The Graphic User Interface (GUI) consists of tools for the control of the soundscape, both during operation hours as well as during the development process of a composition. Hospital staff is advised not to use the expert control menu, since this is designed for the composers and developers that know the system under-the-hood.

1.3 Dependencies And Compatibility

The graphic user interface of the Healing Soundscapes Max patch makes use of the drawsocket package, a Max/node.js based server/client system. It also requires the CNMAT Odot package which can be installed from the Max package manager. The patch works in Max 8 and Max 9.

1.4 Acknowledgements

Back to top

2. How to use

The Graphic User Interface (GUI) consists of tools for the control of the soundscape, both during operation hours as well as during the development process of a composition. Hospital staff is advised not to use the expert control menu, since this is designed for the composers and developers that know the system under-the-hood.

2.1 Basic Mode

2.1.1 What is Basic Mode?

Basic Mode includes the necessary parameters for controlling the soundscape on-site, such as playback and playlist control.

2.1.2 Piece

The dropdown list shows all pieces listed in the currently selected playlist. Read section 2.1.2 for an explanation on how pieces are changed.

2.1.3 Playing Mode

The dropdown list for Playing Mode lists two options:
1. Selected Piece: the title chosen in the Piece list (see section 2.1.1) will be played continuously.
2. Playlist: the patch will play through the pieces in order of sequence.
Each piece will be played for the length specified in the duration box. Between the pieces – or the iteration of the same piece – there will be a silence whose length is specified in the silence box. Read section 2.1.3 to learn how to change the selected playlist on your device.

2.1.4 How to select a Playlist

Each device can play only one playlist at a time. Playlists are organized as subfolders within:
/Users/user/Documents/Max 8/Library/healing-soundscapes/environments
To select a playlist, create an empty text file named blessed.txt inside the desired playlist folder.
⚠️ Important: The system will automatically select the first folder it finds that contains a blessed.txt file. Only one playlist folder should contain this file at any given time.
When switching playlists, be sure to either move the existing blessed.txt file to the new folder or delete it before creating a new one. Having multiple blessed.txt files may result in unpredictable behavior.

2.1.5 Play

A toggle to start or stop the soundscape.

2.1.6 Tempo

Set the tempo in beats per minute (BPM) of the soundscape. A lower number results in more sparse events, a higher number will make the soundscape more lively.

2.1.7 Duration

The length of each piece in seconds (e.g. 300 seconds = 5 minutes).

2.1.8 Silence

The length of silence between each piece (or iteration of the same piece, if in ‘selected piece’ playing mode) in seconds.

2.1.9 Volume

The volume of the soundscape in decibels.

Back to top

2.2 Expert Mode

2.2.1 What is Expert Mode?

Expert Mode includes all parameters for controlling each individual DJster instance. This screen is meant only for the composers and programmers. There is a menu where each instance can be selected, called “Player 1” up until “Player 4”.

2.2.2 Instrument (dropdown list)

Selects the playback instrument or sound source for the sampler.

2.2.3 Scale (dropdown list)

Defines the tonal environment.

2.2.4 Meter (dropdown list)

Sets the time signature, choosing rhythmic grouping.

2.2.5 On (toggle)

Activates or deactivates the DJster instance.

2.2.6 Sorted (toggle)

Determines whether the notes of each event are outputted sorted by pitch or not.

2.2.7 Overlap (toggle)

Enables overlapping of musical events, allowing simultaneous layers instead of strictly sequential playback.

2.2.8 Outset Pulses (slider 1–16)

?

2.2.9 Eventfulness (slider 0–100)

Controls the overall density and frequency by controlling the probability of note output.

2.2.10 Event Length (slider 5–1000)

Sets the average duration of events in milliseconds, from short staccato notes to sustained tones.

2.2.11 Metriclarity (slider 0–100)

Controls how strictly the generated notes fall within the chosen meter: lower values produce freer timing, higher values enforce clearer metric structure.

2.2.12 Harmoniclarity (slider 0–100)

Controls how close the notes are to the chosen scale: lower values have more notes outside of the scale, higher values stress tonal stability.

2.2.13 Chordal Weight (slider 1–5)

Determines the importance of harmonic (chord-based) events relative to melodic material.

2.2.14 Melodic Cohesion (slider –100–100)

Controls the tendency for melodic continuity: negative values create disjunct leaps, positive values favor stepwise motion.

2.2.15 Melody Scope (slider 0–9)

Sets the span of melodic exploration, defining how wide or narrow the pitch contour can be.

2.2.16 Tonic Pitch (slider C–1 – C6)

Assigns the tonal center note of the scale, anchoring pitch relationships to a chosen tonic.

2.2.17 Pitch Center (slider C–1 – C6)

Specifies the register around which pitches are distributed, centering the melodic activity.

2.2.18 Pitch Range (slider 0–36)

Sets the span (in semitones) above and below the pitch center notes can be generated.

2.2.19 Dynamics (slider 0–127 = MIDI)

Controls the output velocity (loudness) of events, corresponding to MIDI dynamic levels.

2.2.20 Attenuation (slider 0–100)

Applies a scaling factor to dynamics, reducing or moderating the overall loudness of output.

Back to top

2.3 Room Settings

2.3.1 Level 1 (dB) (slider -70–6)

Sets the volume of the first DJster instance in decibels.

2.3.2 Level 2 (dB) (slider -70–6)

Sets the volume of the second DJster instance in decibels.

2.3.3 Level 3 (dB) (slider -70–6)

Sets the volume of the third DJster instance in decibels.

2.3.4 Level 4 (dB) (slider -70–6)

Sets the volume of the fourth DJster instance in decibels.

2.3.5 Room Size (slider 1–300)

Sets the virtual size of the simulated acoustic space, from small rooms to large halls.

2.3.6 Rev. Time (ms) (slider 0.5–15)

Controls the reverb decay time in milliseconds.

2.3.7 Spread (slider 0–100)

Adjusts the stereo width of the reverb field: lower values keep it narrow, higher values create a wider spatial impression.

2.3.8 Bandwidth (slider 0–100)

Sets the frequency range passed into the reverb: lower values darken the sound, higher values keep it brighter.

2.3.9 Damping (slider 0–100)

Controls the high-frequency absorption in the room: lower values yield brighter tails, higher values make the reverb warmer and darker.

2.3.10 Early (slider 0–100)

Balances the level of early reflections, shaping the sense of proximity and room definition.

2.3.11 Tail (slider 0–100)

Adjusts the level of the late reverb tail, affecting the spaciousness and depth of the acoustic.

2.3.12 Dry (slider 0–100)

Sets the balance of the unprocessed (dry) signal relative to the reverberated (wet) signal.

Back to top

2.4 System

2.4.1 Updates

Checks for a new software version and updates if new version was found.
⚠️ Important: This requires an active internet connection.
⚠️ Currently not working

2.4.2 Server IP Address

Shows the IP address of the GUI, so it can be accessed on another device.

2.4.3 Shut Down

Shuts down the software. This will require a manual restart.

Back to top