identify layers<\/h2>\n\n\n\n
For this, you switch your listening over from hearing events in time, to listening to layers. Think of this as converting your mode of listening from considering form and structure (i.e.\u00a0time\/rhythm) towards a consideration of timbre and colour and its shifts in-time. How are different layers of sound material competing for attention, allowing one another to coexist? How is the spectra broken up? What\u2019s missing in the spectra?<\/p>\n\n\n\n
Label for yourself the function of each layer.<\/h2>\n\n\n\n- what is the function of each layer? How much presence is there?<\/li>
- When do things emerge into ‘view’? <\/li>
- What else in the soundspace might make that possible to hear?<\/li>
- Are things interconnected? See below…<\/li><\/ul>\n\n\n\n
combine your spectral and temporal thinking<\/h2>\n\n\n\n- do different elements of different layers change roles? For example, does the background move to the foreground?<\/li>
- When does it happen?<\/li>
- Why?<\/li><\/ul>\n\n\n\n
Now what?<\/h1>\n\n\n\n
In your DAW, it\u2019s wise to setup different conceptual groups of \nmaterial. There may be different kinds of content depending upon what \nyou\u2019re trying to do. In the end, it\u2019s probably sensible to give yourself\n some busses to mix, rather than trying to mix what could be over 100 \ndifferent tracks in the end. You can think of mixing back, middle and \nforegrounds. Alternatively, you may have something more like a film mix \nwhich could require you having mixing tracks for:<\/p>\n\n\n\n
- dialogical\/discursive\/semantic<\/li>
- environmental\/contextual\/spot-event sounds (diegetic, in-world sounds)<\/li>
- atmospheres\/feelings\/sentiments\/drones (non-diegetic, music-like behaviour)<\/li><\/ul>\n\n\n\n
space<\/h1>\n\n\n\n
listening to your guide track, there will almost certainly be a sense of space in there. Things aren\u2019t simply in one location all the time, rather they\u2019re moving across the spatial field (as captured by the mics). So, how will you handle the spatial positioning of your different layers and what path<\/em> is each sound on?<\/p>\n\n\n\nDownload<\/h4>\n\n\n\n
Access the Reaper session I showed and the files I recorded for demonstration purposes in the audiocrafting group folder. It’s called “scenes.zip”.<\/p>\n\n\n\n
sonic objects<\/h1>\n\n\n\n
You have your library, but it probably doesn\u2019t really do much as a series of sounds on their own, so, how will you layer and group these together in order to make individual sonic events?<\/p>\n\n\n\n
Making sub\/micro libraries from your words<\/h3>\n\n\n\n
I can’t laud the powers of micro-sound library manipulation enough. As we saw from Krotos’ work<\/a>, a well organised library of sounds can be really usefully be put to work to make new sounds very quickly. This happens often in game audio too. <\/p>\n\n\n\nMicro-sound editing is extremely laborious and although it’s true to say that we lose detail if we don’t edit precisely (and that perhaps means manually), we can get a very long way with sound file manipulation and reorganisation using batch processing tools to auto-extract chunks of sound and using other tools (such as the one below) to recombine them in interesting ways. <\/p>\n\n\n\n
Batch slicing using Aubio<\/h2>\n\n\n\n
Aubio<\/a> is a library of very handy tools written in C for a very fast real-time implementation. There is a Python interface to these tools which makes it possible to run aubio on the commandline or shell. <\/p>\n\n\n\nTo install aubio on OS X<\/h4>\n\n\n\n
You should definitely use a prebuilt and compiled version which means you want to get a python package manager installed first, this is called pip. This should be installed automatically with more recent python installs. If you don’t have it, you can follow the instructions here: pip.pypa.io\/en\/stable\/installing\/<\/a><\/p>\n\n\n\nWhen your package manager is installed, try typing in the aubio install command:<\/p>\n\n\n\n
pip install aubio
<\/pre>\n\n\n\nor if your installation is python3-based, then<\/p>\n\n\n\n
pip3 install aubio<\/pre>\n\n\n\naubio.org\/manual\/latest\/python_module.html#python-install<\/a><\/p>\n\n\n\nWhen aubio is there <\/h4>\n\n\n\n
Try running a command to check it’s happy, type this:<\/p>\n\n\n\n
aubio -h<\/pre>\n\n\n\nIf aubio is comfortably installed, you’ll see the following:<\/p>\n\n\n\n
usage: aubio [-h] [-V] \u2026
optional arguments:
-h, --help show this help message and exit
-V, --version show version
commands:
help show help message onset estimate time of onsets (beginning of sound event) pitch estimate fundamental frequency (monophonic) beat estimate location of beats tempo estimate overall tempo in bpm notes estimate midi-like notes (monophonic) mfcc extract Mel-Frequency Cepstrum Coefficients melbands extract energies in Mel-frequency bands quiet extract timestamps of quiet and loud regions cut slice at timestamps<\/code>
use \"aubio --help\" for more info about each command<\/pre>\n\n\n\nSo, try and slice up a sound…<\/p>\n\n\n\n
aubio cut fileName.wav -o path\/Where\/You\/Want\/Some\/Slices\/To\/Appear<\/pre>\n\n\n\nIf that worked, then you can run batch on LOADS of sounds all at once:<\/p>\n\n\n\n
for f in *.wav; do aubio cut \"$f\" -o path\/to\/outouts\/; done
<\/pre>\n\n\n\nReorganising sounds with a custom tool.
<\/h3>\n\n\n\n
One approach is to invent an event-maker tool and see how you get on. You could explore some of the very powerful tools shown by Krotos last week, or try rolling your own in MaxMSP. An example application is uploaded here: www.dropbox.com\/s\/vfehghs6hle11ql\/shapeMaker_OSX.zip?dl=0<\/a><\/p>\n\n\n\n![\"\"](\"https:\/\/digital.eca.ed.ac.uk\/sounddesignmedia\/files\/2019\/10\/dropAFolder-1024x544.png\")
Drop a folder of sound files in the top-right area. Ideally these should be very short sounds with a fade at the beginning and end of each file. <\/figcaption><\/figure>\n\n\n\n- drag and drop a folder of sounds on the top right<\/li>
- set an event duration (how long do you want the gesture to take?<\/li>
- how much tail for the event do you need? Will there be some long sounds that will get clipped at the end of the recording if they don’t play to the end<\/li>
- hit the clear buttons on the pan and files curves and draw some curves through the library of sound files<\/li>
- you can set the file name of the sound you want to record in the little recorder unit at the bottom of the right hand side<\/li>
- every time you hit the button at the top left of the shape-maker window (not the init button, the one to its right), a new gesture will be made of the duration that you set in point 2 above<\/li>
- specify pan journey through the file<\/li>
- use your mic to walk through the sound file collection instead, or play a sound file by clicking the buttons below. To record your sound you’ll need to manually trigger it when using your microphone, but when playing a sound file, it will stop recording at the end of the sound file play routine.<\/li>
- have fun…<\/li><\/ul>\n\n\n\n
![\"\"](\"https:\/\/digital.eca.ed.ac.uk\/sounddesignmedia\/files\/2019\/10\/Screenshot-2019-10-15-at-16.57.52.png\")
sound control of the shapeMaker<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"workflow go forth and listen It\u2019s not a mad idea to listen to existing forms and try to work out what\u2019s going on with them. I find it useful to engage in purposeful, active tasks and record myself doing them. …<\/p>\n
combine your spectral and temporal thinking<\/h2>\n\n\n\n- do different elements of different layers change roles? For example, does the background move to the foreground?<\/li>
- When does it happen?<\/li>
- Why?<\/li><\/ul>\n\n\n\n
Now what?<\/h1>\n\n\n\n
In your DAW, it\u2019s wise to setup different conceptual groups of \nmaterial. There may be different kinds of content depending upon what \nyou\u2019re trying to do. In the end, it\u2019s probably sensible to give yourself\n some busses to mix, rather than trying to mix what could be over 100 \ndifferent tracks in the end. You can think of mixing back, middle and \nforegrounds. Alternatively, you may have something more like a film mix \nwhich could require you having mixing tracks for:<\/p>\n\n\n\n
- dialogical\/discursive\/semantic<\/li>
- environmental\/contextual\/spot-event sounds (diegetic, in-world sounds)<\/li>
- atmospheres\/feelings\/sentiments\/drones (non-diegetic, music-like behaviour)<\/li><\/ul>\n\n\n\n
space<\/h1>\n\n\n\n
listening to your guide track, there will almost certainly be a sense of space in there. Things aren\u2019t simply in one location all the time, rather they\u2019re moving across the spatial field (as captured by the mics). So, how will you handle the spatial positioning of your different layers and what path<\/em> is each sound on?<\/p>\n\n\n\nDownload<\/h4>\n\n\n\n
Access the Reaper session I showed and the files I recorded for demonstration purposes in the audiocrafting group folder. It’s called “scenes.zip”.<\/p>\n\n\n\n
sonic objects<\/h1>\n\n\n\n
You have your library, but it probably doesn\u2019t really do much as a series of sounds on their own, so, how will you layer and group these together in order to make individual sonic events?<\/p>\n\n\n\n
Making sub\/micro libraries from your words<\/h3>\n\n\n\n
I can’t laud the powers of micro-sound library manipulation enough. As we saw from Krotos’ work<\/a>, a well organised library of sounds can be really usefully be put to work to make new sounds very quickly. This happens often in game audio too. <\/p>\n\n\n\nMicro-sound editing is extremely laborious and although it’s true to say that we lose detail if we don’t edit precisely (and that perhaps means manually), we can get a very long way with sound file manipulation and reorganisation using batch processing tools to auto-extract chunks of sound and using other tools (such as the one below) to recombine them in interesting ways. <\/p>\n\n\n\n
Batch slicing using Aubio<\/h2>\n\n\n\n
Aubio<\/a> is a library of very handy tools written in C for a very fast real-time implementation. There is a Python interface to these tools which makes it possible to run aubio on the commandline or shell. <\/p>\n\n\n\nTo install aubio on OS X<\/h4>\n\n\n\n
You should definitely use a prebuilt and compiled version which means you want to get a python package manager installed first, this is called pip. This should be installed automatically with more recent python installs. If you don’t have it, you can follow the instructions here: pip.pypa.io\/en\/stable\/installing\/<\/a><\/p>\n\n\n\nWhen your package manager is installed, try typing in the aubio install command:<\/p>\n\n\n\n
pip install aubio
<\/pre>\n\n\n\nor if your installation is python3-based, then<\/p>\n\n\n\n
pip3 install aubio<\/pre>\n\n\n\naubio.org\/manual\/latest\/python_module.html#python-install<\/a><\/p>\n\n\n\nWhen aubio is there <\/h4>\n\n\n\n
Try running a command to check it’s happy, type this:<\/p>\n\n\n\n
aubio -h<\/pre>\n\n\n\nIf aubio is comfortably installed, you’ll see the following:<\/p>\n\n\n\n
usage: aubio [-h] [-V] \u2026
optional arguments:
-h, --help show this help message and exit
-V, --version show version
commands:
help show help message onset estimate time of onsets (beginning of sound event) pitch estimate fundamental frequency (monophonic) beat estimate location of beats tempo estimate overall tempo in bpm notes estimate midi-like notes (monophonic) mfcc extract Mel-Frequency Cepstrum Coefficients melbands extract energies in Mel-frequency bands quiet extract timestamps of quiet and loud regions cut slice at timestamps<\/code>
use \"aubio --help\" for more info about each command<\/pre>\n\n\n\nSo, try and slice up a sound…<\/p>\n\n\n\n
aubio cut fileName.wav -o path\/Where\/You\/Want\/Some\/Slices\/To\/Appear<\/pre>\n\n\n\nIf that worked, then you can run batch on LOADS of sounds all at once:<\/p>\n\n\n\n
for f in *.wav; do aubio cut \"$f\" -o path\/to\/outouts\/; done
<\/pre>\n\n\n\nReorganising sounds with a custom tool.
<\/h3>\n\n\n\n
One approach is to invent an event-maker tool and see how you get on. You could explore some of the very powerful tools shown by Krotos last week, or try rolling your own in MaxMSP. An example application is uploaded here: www.dropbox.com\/s\/vfehghs6hle11ql\/shapeMaker_OSX.zip?dl=0<\/a><\/p>\n\n\n\nDrop a folder of sound files in the top-right area. Ideally these should be very short sounds with a fade at the beginning and end of each file. <\/figcaption><\/figure>\n\n\n\n- drag and drop a folder of sounds on the top right<\/li>
- set an event duration (how long do you want the gesture to take?<\/li>
- how much tail for the event do you need? Will there be some long sounds that will get clipped at the end of the recording if they don’t play to the end<\/li>
- hit the clear buttons on the pan and files curves and draw some curves through the library of sound files<\/li>
- you can set the file name of the sound you want to record in the little recorder unit at the bottom of the right hand side<\/li>
- every time you hit the button at the top left of the shape-maker window (not the init button, the one to its right), a new gesture will be made of the duration that you set in point 2 above<\/li>
- specify pan journey through the file<\/li>
- use your mic to walk through the sound file collection instead, or play a sound file by clicking the buttons below. To record your sound you’ll need to manually trigger it when using your microphone, but when playing a sound file, it will stop recording at the end of the sound file play routine.<\/li>
- have fun…<\/li><\/ul>\n\n\n\n
sound control of the shapeMaker<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"workflow go forth and listen It\u2019s not a mad idea to listen to existing forms and try to work out what\u2019s going on with them. I find it useful to engage in purposeful, active tasks and record myself doing them. …<\/p>\n
Now what?<\/h1>\n\n\n\n
In your DAW, it\u2019s wise to setup different conceptual groups of \nmaterial. There may be different kinds of content depending upon what \nyou\u2019re trying to do. In the end, it\u2019s probably sensible to give yourself\n some busses to mix, rather than trying to mix what could be over 100 \ndifferent tracks in the end. You can think of mixing back, middle and \nforegrounds. Alternatively, you may have something more like a film mix \nwhich could require you having mixing tracks for:<\/p>\n\n\n\n
- dialogical\/discursive\/semantic<\/li>
- environmental\/contextual\/spot-event sounds (diegetic, in-world sounds)<\/li>
- atmospheres\/feelings\/sentiments\/drones (non-diegetic, music-like behaviour)<\/li><\/ul>\n\n\n\n
space<\/h1>\n\n\n\n
listening to your guide track, there will almost certainly be a sense of space in there. Things aren\u2019t simply in one location all the time, rather they\u2019re moving across the spatial field (as captured by the mics). So, how will you handle the spatial positioning of your different layers and what path<\/em> is each sound on?<\/p>\n\n\n\n
Download<\/h4>\n\n\n\n
Access the Reaper session I showed and the files I recorded for demonstration purposes in the audiocrafting group folder. It’s called “scenes.zip”.<\/p>\n\n\n\n
sonic objects<\/h1>\n\n\n\n
You have your library, but it probably doesn\u2019t really do much as a series of sounds on their own, so, how will you layer and group these together in order to make individual sonic events?<\/p>\n\n\n\n
Making sub\/micro libraries from your words<\/h3>\n\n\n\n
I can’t laud the powers of micro-sound library manipulation enough. As we saw from Krotos’ work<\/a>, a well organised library of sounds can be really usefully be put to work to make new sounds very quickly. This happens often in game audio too. <\/p>\n\n\n\n
Micro-sound editing is extremely laborious and although it’s true to say that we lose detail if we don’t edit precisely (and that perhaps means manually), we can get a very long way with sound file manipulation and reorganisation using batch processing tools to auto-extract chunks of sound and using other tools (such as the one below) to recombine them in interesting ways. <\/p>\n\n\n\n
Batch slicing using Aubio<\/h2>\n\n\n\n
Aubio<\/a> is a library of very handy tools written in C for a very fast real-time implementation. There is a Python interface to these tools which makes it possible to run aubio on the commandline or shell. <\/p>\n\n\n\n
To install aubio on OS X<\/h4>\n\n\n\n
You should definitely use a prebuilt and compiled version which means you want to get a python package manager installed first, this is called pip. This should be installed automatically with more recent python installs. If you don’t have it, you can follow the instructions here: pip.pypa.io\/en\/stable\/installing\/<\/a><\/p>\n\n\n\n
When your package manager is installed, try typing in the aubio install command:<\/p>\n\n\n\n
pip install aubio
<\/pre>\n\n\n\nor if your installation is python3-based, then<\/p>\n\n\n\n
pip3 install aubio<\/pre>\n\n\n\n
aubio.org\/manual\/latest\/python_module.html#python-install<\/a><\/p>\n\n\n\n
When aubio is there <\/h4>\n\n\n\n
Try running a command to check it’s happy, type this:<\/p>\n\n\n\n
aubio -h<\/pre>\n\n\n\n
If aubio is comfortably installed, you’ll see the following:<\/p>\n\n\n\n
usage: aubio [-h] [-V] \u2026
optional arguments:
-h, --help show this help message and exit
-V, --version show version
commands:
help show help message onset estimate time of onsets (beginning of sound event) pitch estimate fundamental frequency (monophonic) beat estimate location of beats tempo estimate overall tempo in bpm notes estimate midi-like notes (monophonic) mfcc extract Mel-Frequency Cepstrum Coefficients melbands extract energies in Mel-frequency bands quiet extract timestamps of quiet and loud regions cut slice at timestamps<\/code>
use \"aubio --help\" for more info about each command<\/pre>\n\n\n\nSo, try and slice up a sound…<\/p>\n\n\n\n
aubio cut fileName.wav -o path\/Where\/You\/Want\/Some\/Slices\/To\/Appear<\/pre>\n\n\n\n
If that worked, then you can run batch on LOADS of sounds all at once:<\/p>\n\n\n\n
for f in *.wav; do aubio cut \"$f\" -o path\/to\/outouts\/; done
<\/pre>\n\n\n\nReorganising sounds with a custom tool.
<\/h3>\n\n\n\nOne approach is to invent an event-maker tool and see how you get on. You could explore some of the very powerful tools shown by Krotos last week, or try rolling your own in MaxMSP. An example application is uploaded here: www.dropbox.com\/s\/vfehghs6hle11ql\/shapeMaker_OSX.zip?dl=0<\/a><\/p>\n\n\n\n
Drop a folder of sound files in the top-right area. Ideally these should be very short sounds with a fade at the beginning and end of each file. <\/figcaption><\/figure>\n\n\n\n - drag and drop a folder of sounds on the top right<\/li>
- set an event duration (how long do you want the gesture to take?<\/li>
- how much tail for the event do you need? Will there be some long sounds that will get clipped at the end of the recording if they don’t play to the end<\/li>
- hit the clear buttons on the pan and files curves and draw some curves through the library of sound files<\/li>
- you can set the file name of the sound you want to record in the little recorder unit at the bottom of the right hand side<\/li>
- every time you hit the button at the top left of the shape-maker window (not the init button, the one to its right), a new gesture will be made of the duration that you set in point 2 above<\/li>
- specify pan journey through the file<\/li>
- use your mic to walk through the sound file collection instead, or play a sound file by clicking the buttons below. To record your sound you’ll need to manually trigger it when using your microphone, but when playing a sound file, it will stop recording at the end of the sound file play routine.<\/li>
- have fun…<\/li><\/ul>\n\n\n\n
sound control of the shapeMaker<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":" workflow go forth and listen It\u2019s not a mad idea to listen to existing forms and try to work out what\u2019s going on with them. I find it useful to engage in purposeful, active tasks and record myself doing them. …<\/p>\n