31/05/09

Date:  31/05/09

Phase:  Research & Development – Modeling

Version:  None

Summary of Activities:

The focal point of today’s activites was upon research and modeling of the environment’s main window as well as modules.  In accordance, the proceeding section is a summary of the main window and modules of the main window. 

Main Window

The main window is the workstation of the environment and will comprise of: 

Sound Modules:  the six modules, assignable through the module selection, will serve as the control center for each sound or groups of sounds

Record and Playback Parameters:  

section devoted to the recording and playback of the generated soundscape

Reverb:  optional so one may apply the effect elsewhere, the reverb unit will be significant feature due to its importance in producing urban soundscapes 

Options & Miscellaneous:  section consisting of different options, buttons, and menus

Modules

The module is assignable to “macro”, “meso”, and “object/event” - each type refers to the diverse stratums with the soundscape’s timescale.  Also inclusive in the module is the action parameter and action preset storage, which will house parameters to control the sound’s movement, intensity, and timbre.  Finally, the spatialization parameters will allow the user to graphically place the sound within the surround sound “superfield”.

Notes:

Tomorrow will be beginning of the engineering phase.

30/05/09

Date:  30/05/09

Phase:  Research & Development – Modeling

Version:  None

Summary of Activities:

The subsequent summary is an analysis of the data storage sub patch that will be utilized to store and recall playlists within the soundscape generating environment.

Playlist Data Storage Sub Patch Summary

As shown in the picture above, the sub patch consists of three inlets, two outlets, and two main sections devoted to the storage and recall of data.

Inlet One:  receives information pertaining the index of the file and it’s placement within the playlist

Inlet Two:  collects file path data and location of the audio file on the hard disk

Inlet Three:  receives four different messages

• Write:  brings up a dialog box and saves playlist to a drive
  
• Read:  brings up dialog box and loads playlist information into the coll object
  
• Load:  send data from current playlist within the coll object to the outlets
  
• Clear:  clears data within the coll object
  

1. Outlet One: outputs index number information
   
2. Outlet Two:  outputs file path information
   

Storage Section

Consists of the coll and router object that is used in order to store and recall data to a text file.  The router object then directs the integer (in the this case, our index number) to the appropriate outlet.

Recall Section

Comprises of a metro object, counter, and router object.  The metro object sends bang messages (limited by the length of the playlist within the coll object) to the counter.  Once the counter receives a bang it will increase the outputted number by an increment of one, which then recalls file path and index information contained with the coll object.

Notes:

Tomorrow will consist of final preparations for the engineering phase on Monday, which will be primarily focused up finishing the modeling of the main environment’s modules and interface.

29/05/09

Date:  29/05/09

Phase:  Research & Development – Modeling

Version:  None

Summary of Activities:

The focus the past few days’ activities surrounded playlist data storage, which has been fully finished.  Some initial work has been done with the playlist window that is in its very early stages.

Notes:

Tentatively, all objectives for the week will be completed, which will mark the formal first phase of engineering.  A summary of the playlist data storage sub patch will be posted within the next blog.

27/05/09

Date:  27/05/09

Phase:  Research & Development – Modeling

Version:  None

Summary of Activities:

Activities of the past few days have been primarily aimed at finishing the data storage sub patch for playlists.  The sub patch is nearly complete as it successfully saves the file path and index number of the items within the playlist.  Moreover, the data recall function is also nearly finished and may need a few more days of finalizing and bug fixes.  The following picture is the sub patch in its nearly completed form:

 

Patch cord information

• Red: Path of playlist index number
  
• Green:  Path of file location data
  
• Blue:  Path of the merged data (index number and file path)
  
• Black:  Miscellaneous

Notes:

The next couple of days will be focused upon polishing the sub patch as well as working on the basic layout of the environment’s main window.  More information will be posted regarding the patch when it’s complete.

Weekly Summary 18/05/09 - 24/05/09

Phase:  Research & Development 

Version:  None

Weekly Summary of Activities:

Goals this week comprised of designing the layout of the environment as well as research and some preliminary engineering of the data storage system for playlists.  These activities are expected to be continued in the next few days of this week.

This Week's Objectives: 

The continuance of last week's activities are anticipated to take until the middle of week three. Implementation of the playlist model and its functions being the focal point until the end of the week.

Next week's objectives are as followed:

1. Finish the basic layout of the environment and its windows
   
2. Finish the data storage system subpatch for playlists
   
3. Begin the engineering of the environment (playlist window)
   

24/05/09

Date:  24/05/09

Phase:  Research & Development – Modeling

Version:  None

Summary of Activities:

Design of the main window’s modules and some further work on data storage were the focus of the past few days.  Modules will consist of sets of parameters that are applicable to the timescale.  For instance, macro modules need the capability to loop a recording/sample of a soundscape’s ambience (people talking, room tone, etc), whereas on a meso modules one will need to be in control of the relative frequency of the samples being played and the order (ascending, descending, random) of them.  Modules will also have the capability to store Actions.  Actions will be a means of saving/recalling information such as the sound’s spatial placement on the horizontal plane as well as its movement within it.

Notes:

In the next few days more work will be done on recalling playlist information as well as finalizing the basic framework of the environment. The storage of playlist file paths and their relative index numbers has been successful.

21/05/09

Date:  21/05/09

Phase:  Research & Development – Research & Modeling

Version:  None

Summary of Activities:

Design of the playlist window and research of the implementation of each function within the window were the central activity.  The following is a simple design layout illustrating the sections of the playlist window.

 

Areas in light grey represent the visual components of the window, whilst the orange show the placement of functions.

1. Drag/Drop Files:  drag in specific digital audio files to the current playlist
   
2. Data Storeage/Recall & Playlist Editing:  functions for editing playlists (delete, clear, etc) as well as storing and recalling them
   
3. Playlist Files:  list box of files along with their respected filepatch
   
4. Waveform display:  Visual display of each file
   
5. Audition:  listen to the digital audio file
   

Furthermore, some work has been put in on data storage.  After some research, a subpatch has been started that’s intended to store as well as recall playlist file paths and their indexes to a text file. 

Notes:

Because data storage is anticipated to be then most challenging portion of the playlist window I have decided to start it.  It’s expected that the subpatch will be complete by the end of the week.  More will be posted when the information is available.

19/05/09

Date:  19/05/09

Phase:  Research & Development – Modeling

Version:  None

Summary of Activities:

The fundamental modeling of the environment was the main aim of today’s work.  These activities comprise of designing the basic framework of the environment.  As mentioned before, the environment will consist of a main window and playlist window.  The playlist window will allow the user to form groups of sounds whilst the main window will contain the functionality of the environment.  The following is a basic model of the current environment: 

Notes:

Modeling of the playlist window will be the focal point of tomorrow’s work.  A very basic design will be created along with some research as well as troubleshooting of how this objective may be implemented within Max/MSP. 

Weekly Summary 12/05/09 - 17/05/09

Phase:  Research & Development

Version:  None

Weekly Summary of Activities:

The focus last week was upon preliminary planning.  Activities comprised of:

1. Planning the framework of the development of the environment
   
2. Meeting and corresponding with an expert engineer regarding my framework and other various aspects of the project
   
3. Beginning phases of the research and modeling stage
   

This Week’s Objectives:

This week’s focal points are projected to be upon the research of literature and modeling of the environment.  This includes making final decisions regarding the environment’s structure.  So far, it’s anticipated that the environment will be divided into sections that corresponds to the distinctive stratums of a soundscape’s timescale.  Also, the modeling and design stage of a “playlist” function is a key goal.  Playlists will allow the user to drag and drop files as well as group them to be used within the main window.  This will be elaborated upon in the coming week.

This week’s goals are as followed:

• Gather literature pertaining to soundscapes
  
• Design the basic framework of the environment
  
• Model the “playlist window”
  

17/05/09

Date:  17/05/09

Phase:  Research & Development – Preliminary Planning

Version:  None

Summary of Activities:

During the meeting with the expert engineer several aspects of the project were discussed.  These aspects included the versioning of the software environment, overall structure, and procedure.  It was decided that the software versioning methodology would start with 0.9.1 and move forward.  Each major update would incrementally move this forward until the version 1.0 public release.  Additionally, when the environment is in beta, it will contain the letter “b” (example:  0.9.5b) in order to indicate the beta phase.  The engineering agreed that the structure and process was sufficient, so no key changes are necessary as of this time. 

Notes:

Weekly summaries will begin tomorrow.  This summary will consist of summarizing the week’s activities as well as defining the objectives for the coming week.

14/05/09

Date:  14/05/09

Phase:  Research & Development – Preliminary Planning, Modeling, & Research

Version:  None

Summary of Activities:

Activities comprised of researching literature and documents regarding acoustics and Max/MSP.  Also, some initial modeling of the environment was done.  It was found that while working with multiple sound files, it would be appropriate to construct a system for creating “playlists”.  These timescale distinct playlists will hold data relating to file’s path as well as serve as a means to group audio files that may be on different parts of the hard drive and hold similar characteristics.  For example, a ‘café sounds’ macro playlist may have people conversing and cars driving by.

Notes:

Tomorrow’s activities are to be more of the same.  Additionally, time will be taken to formulate questions to ask the expert engineer.

13/05/09

Date:  13/05/09

Phase:  Research & Development – Preliminary Planning & Research

Version:  None

Summary of Activities:

The concentration of today’s activities was upon research and information gathering.  Various pieces of literature in the form of books and websites were studied.  These sources were primarily concerned with the programming environment Max/MSP, acoustics, and sound theory.  Acquired sources are projected to aid the modeling process and the later engineering of the environment.

 

Notes:

After corresponding with the engineer through email, the meeting with the expert software engineer regarding advice on my project's methodological framework is going ahead as planned.  The meet, itself, is planned for May 16^th.   Until then, some changes may be made in the project’s methodology; however, research and information gathering will be the center of activities.

12/05/09

Date:  12/05/09

Phase:  Research & Development – Preliminary Planning

Version:  None

 

Summary of Activities:

Today marks the formal beginnings of project module CMP 461/462.  Final preparations and planning of the project being the aim and focal point, each aspect as well as stage of the project was scrutinized.  Major developments include the detailing of every phase pertaining to the environment’s construction and the activities as well as methodology included within them – all of which will be recorded here.  These phases include the following:

 

1. Research & Development:  Primarily concerned with the planning of the environment’s structure
• Preliminary planning:  planning of the details of the project’s methodology

• Research:  compositing of resources and information regarding pertinent theoretical research
• Modeling:  planning of the structure of the environment

2. Engineering:  Creation and testing of the soundscape generator
• Engineering:  Implementation and construction of the environment
• Beta Testing:  testing of the effectiveness of the beta and updating the environment
  

 

Notes:

These activities are expected to continue tomorrow.  Furthermore, I will be seeking advice regarding my methodology behind construction of the environment from an expert software engineer as to comparatively verify their processes to mine.

12/05/09

Date:  12/05/09

Phase:  Research & Development

Version:  None

Today marks the formal beginning of project module CMP 461/462.  Final preparations and planning of the project being the aim and focal point, each aspect as well as stage of the research was scrutinized.  Major developments and activities include: 

• Detailing of every phase within the study
  
• Planning the methodology and processes utilized in order to engineer and test the environment
  
• Resource gathering