Weekly Summary 22/06/09 – 28/06/09

Weekly Summary 22/06/09 – 28/06/09

Phase:  Engineering

Version:  None

Weekly Summary of Activities:

The weekly objectives of July 22nd through the 28th were punctually completed within the first few days.  The primary objective was to complete the the player sub patch that controls the random/aleatoric triggering of recorded digital audio.  However, it may be necessary to tweak this sub patch in order to fit the needs of the environment within the coming weeks.  This gave room to start preliminary engineering of the sub patch, surround1, dedicated to automation within the surround sound channels during the latter portion of week.  

This Week’s Objectives:

The aim of the next two weeks is to complete the first module along with the spatialization parameters of the environment.  Once this is done, the modules will be duplicated and the first beta of the environment should be ready for testing.  The following section of this blog is the objectives for the coming week:

1. Engineer and complete the surround1 module
   
2. Initial engineering (and tentatively the completion) of the reverb effect section
   

28/06/09

Date:  28/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

The remainder of the week has been targeted upon the competition of the action storage system.  As a part of one of the main objectives of this week, the storage system has be finished, thus allowing time to work on other facets of the environment.  This additional time has allowed some focus to be given upon the spatialization effects of the module.  

Notes:

The focal point of next week's activities will be on the spatialization effects of the module, which will be inclusive of audio surround sound, 3d panning automation between speakers, and reverb.  Once these functions are finished, the activities surrounding the first module should be nearing its end.  Then the archetype will be duplicated according to the original model of the environment.  This will be laid out in detail in tomorrow's weekly summary. 

24/06/09

Date:  24/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Similar to late last week, the past few days have been dedicated to finishing the player sub patch.  As such, final touches were made and a few changes along with it.  One inlet has been added to receive the total count of audio files within the module's playlist.  Furthermore, two outlets were also added to the sub patch.  The first is the randomized playlist index number and the latter is sends the count message the the umenu within the main window. The proceeding is the updated summary of the sub patch's inlets and outlets along with a screenshot of the finished product. 

Inlets

1. Play/stop toggle:  start and stop the module
   
2. Macro, Meso/Sound, & Object/Event:  activate certain timescale dependent functions (ex:  looping)
   
3. Delay Min:  connected to the minimum delay selected*
   
4. Delay Max:  connected to the maximum delay selected*
   
5. Intensity Min:  connected to the minimum amplitude selected*
   
6. Intensity Max:  connected to the maximum amplitude selected*
   
7. Loop Start:  set the start loop point of the audio file
   
8. Loop End:  set the end loop point of the audio fille
9. Playlist Count:  receiver of the total number of files in the module's playlist

Outlets

1. Signal:  Audio from the groove object (plays audio straight from the module's dedicated buffer)
   
2. Random Playlist Index Number:  changes the selected file within the playlist*
3. Count:  sends a "count" message to the umenu and this information is received in the last inlet of the sub patch*
   

*aleatoric parameters or messages

Notes:

Tomorrow will be focused upon the action storage system for each module.

Weekly Summary 15/06/09 – 21/06/09

Weekly Summary 15/06/09 – 21/06/09

Phase:  Engineering

Version:  None

Weekly Summary of Activities:

The majority of the tasks set out for this week were completed.  In addition, major developments were made in regards to the engineering of the "player" sub patch, which will house the key functionality in generating and producing the urban soundscapes.  One bug persists with the sub patch and is anticipated to be fixed within the next few days.  More will be posted on the sub patch once it is finished.

This Week’s Objectives:

The proceeding  section is the outline for the objectives of this week.

1. Fix major bugs with the sub patch's functionality
   
2. Complete the player sub patch
   
3. Implement the sub patch within the environment
   
4. Complete action storage functionality
   

21/06/09

Date:  21/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Activities since Thursday have primarily surround the engineering of the "player" sub patch. The player sub patch within the environment will serve as the central hub of functionality of each module and will control the player of the audio within the buffer.  The following is summary of the sub patch's inlets and outlets:

1. Play/stop toggle:  start and stop the module
   
2. Macro, Meso/Sound, & Object/Event:  activate certain timescale dependent functions (ex:  looping)
   
3. Delay Min:  connected to the minimum delay selected*
   
4. Delay Max:  connected to the maximum delay selected*
   
5. Intensity Min:  connected to the minimum amplitude selected*
   
6. Intensity Max:  connected to the maximum amplitude selected*
   
7. Loop Start:  set the start loop point of the audio file
   
8. Loop End:  set the end loop point of the audio file
   

*aleatoric parameters

Notes:

The proceeding week will also surround the developmental of the functionality of the player sub patch along with other various functions of the sub patch.

18/06/09

Date:  18/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Early this week has been largely aimed at housekeeping, engineering aleatoric functions, and small changes in the interface.  The main focus has been upon engineering the aleatoric functions that will allow the user to specify a range in the frequency/delay of the sample and the amplitude of it.  Once the range has been chosen, the environment will select an random value (much like in our random environment) that will either trigger the sample or boost/attenuate the sample's amplitude.

Notes:

The next few days will continue on this trend.  In addition, the following is a list of known bugs for my own reference and the reference of others:

[++++++-Known Bugs-++++++]

1. "Load playlist" brings up dialogue box twice
   
2. Continuity drop box has duplicate items
   
3. Loops points are not saved as part of action storage
   

Weekly Summary 08/06/09 – 14/06/09

Weekly Summary 08/06/09 – 14/06/09

Phase:  Engineering

Version:  None

Weekly Summary of Activities:

The aim of this week was to begin the engineering of the environment's main window, and, specifically the modules within it.  Activities comprised of placement and design of the module's visual features as well as preliminary engineering of different basic functions and parameters (loading the playlist within the module, hide/show parameters pertaining to each timesclae, load settings, etc.).  This task was sufficiently complete, however may still require some attention during this week.

This Week’s Objectives:

The subsequent  section outlines the objectives of this week.

1. Fix bug with playlist loading function
2. General housekeeping to free up the main window's landscape
3. Continuation of the engineering of the main window's modules.  Including:

• a sub patch for handling six separate audio buffers
  
• initial engineering of three (as it pertains to the audio's timescale within the soundscape) sub patches capable of handling the audio

14/06/09

Date:  14/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

The focal points of Sunday's activities was upon the visuals of the module as well as some preliminary engineering of parameters and functions.  The load playlist function was finished today by modifying the data storage sub patch to a simpler version of the sub patch in the main window to fit the needs of loading stored playlists within each module. 

Notes:

Next week will be a  continuance of the engineering this week.  Specific engineering objectives will be posted in the weekly summary tomorrow.

13/06/09

Date:  13/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Similar to the beginning of the week, the past few days' focus has been on the structure as well as preliminary engineering of functions within the environment.  Functionality includes the enable/disable sub patch and is anticipated to be finished within the next few days.  The following is a preview of the module as designed in accordance to the modeling done earlier this month.

Notes:

Tomorrow's activities are projected to be similar to today's activities.

10/06/09

Date:  10/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Both Monday and Tuesday’s focus was centered upon the engineering of the environment’s main window.  Although, mostly concerned with visual design, some progress has been made with the timescale selection and enabling/disabling specific functions and parameters that pertain to it.

Notes:

The rest of the week is expected to be a continuance of these activities.

Weekly Summary 01/06/09 – 07/06/09

Weekly Summary 01/06/09 – 07/06/09

Phase:  Engineering

Version:  None

Weekly Summary of Activities:

As planned, last week's core objectives were completed.  These objectives included the implementing of the data storage sub patch, engineering of the playlist window, and debugging the window accordingly.  With the conclusion of the playlist window, activities in the following week are focused upon the basic designing of the main window as well as the initial engineering of the modules.

This Week’s Objectives:

The proceeding are the key objectives of this week:

1. Basic engineering of the main window
   
2. Engineering the modules according to the design model
   

07/06/09

Date:  07/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

As aforementioned, this week’s aim is to complete the playlist window.  The past few days have been focused on the final touches of the window.  These activities are inclusive of housekeeping, visuals, and a few simple additions to the functionality of the environment.  The proceeding is a summary of the playlist window along with its features and functions. 

Playlist Edit Window

The playlist window is a window separated from the main window that functions as a means of recalling/storing/editing groups of file paths on the host computer’s hard drive.  The typical user often collects massive amounts of audio files that may be located on different parts of the hard drive.  The playlist window allows the user to group these files as well as their paths and store them to an indexed text document, which will be later recalled in the main window or recalled in the playlist window for editing.  For an example, Joe has five audio files he wishes to be a part of his café meso timescale sounds (patrons walking to the tables, mobile phones ringing, etc), however these files are located on specific parts of the hard drive.  Joe is able to group these sound files and save their appropriate paths that are relevant to the file nametag he wishes (i.e. ‘misccafesounds’).

Basic Features

• Drag and drop file (WAVE and AIFF formats only): for easy accumulation of audio files 
  
• Waveform display:  view the waveform of the audio file
  
• Auditioning:  listen to the audio file within the playlist
  
• Audio On/Off:  the toggling on/off of Max/MSP’s Digital to Analog Converter
  

Editing Features

• Delete:  deletion of the current file from the playlist
  
• Clear:  clear all files from the playlist
  

Storage Features

• Store:  save current playlist
  
• Read:  load saved playlist
  

Notes:

The primary weekly objective, completion the playlist window, has been successful.  Next week will be the starting point for the engineering of the main window. 

05/06/09

Date:  05/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Thursday and Friday was dedicated to fixing major bugs and finishing the functionality of the Thursday and Friday was dedicated to fixing major bugs and finishing the functionality of the playlist window.  The objective was completed and the delete parameter as well as the “integer bug” is working as expected.

Notes:

With the major obstacles of the playlist window’s functionality out of the way, focus will be turned upon tweaking of these parameters and visual aesthetics.  A full summary of the window will be added to the blog by the end of the weekend

03/06/09

Date:  03/06/09

Phase:  Engineering

Version:  None

Summary of Activities:

Recent activities have been centered upon the engineering of the playlist window.  Inclusive of this is the programming of parameters and organization of processes within the window.

Notes:

The next few days will be focused upon finishing the playlist window.  Most parameters and their functions have been completed.  Left of these parameters is the audition and delete button, which is projected to be completed, tentatively, in the next few days.  In addition, one bug persists, as the read function adds an unwanted integer (believed to be the length of the coll list) to the playlist.  Fixing this will also be an aim in the next few days.

Weekly Summary 25/05/09 – 31/05/09

Weekly Summary 25/05/09 – 31/05/09

Phase:  Research & Development

Version:  None

Weekly Summary of Activities:

This week’s objectives were completed as listed in last week’s summary, which was primarily focused on completing of the data storage sub patch and modeling of the main window and modules of the environment.  With the conclusion of the first segment of the project, research & development, engineering of the environment will be the focal point of the coming week and thereafter.

This Week’s Objectives:

The following are the aims of this week:

1. Engineer and finish the playlist window
   
2. Implement the data storage sub patch within the playlist window
   
3. Test and debug the functionality of the playlist window
   
4. Initial engineering of the environment’s main window