individual FOV sound extraction

what do we have

• a few new FOVs
• different sizes from [640, 480]
• stage pos for center, in mm's
• old code to deal with stitching, saving each temp results
• old code to trace grooves in individual FOVs, with input data from stitching results

where are we going

• use audio extraction on new sine waves

what do we not have

• stitching data, bbox, trc_vertex, etc.
• an intuitive

what to do

• create new project repository
• use an individual process to create "stitching data" (centered coords)

Webcast metadata

<webcast>
make it simple
1 - layout of list
2 - workflow of listening
3 - workflow of tagging

3. workflow of tagging
- mp3 files -> server
- manual input:
  single entries: time, place, concert title
  matrix: title, composer, performer (instr) (omit allowed)

intelligent: blank strip

Webcast overall

<webcasting sites>
template
talk to alain
mcgill information service center
- possible using mcgill content management (CMS) API/component, instead of creating myself
- cosmetic features

make sure services that they ask for

after talking with CMS, know how much coding i have to do

user stats (who, where, when downloaded)

Music Manager ver 0.1.0

<re-arrange music according to date>

chrono list
add new stuff to their genre list
- rescan through metadata

-------------------

so that new releases stands out

input: folder
output: m2u list, renamed folders

1. all new music goes to 'my music'
2. when needed to be moved to USB, a folder named after the "creation date" is created (if it does not exist), and all albums got on the same date get in, accurate to month
3. 'monthly' and 'dayly' m3u lists are created to the 'my playlists', rescan
4. related genre playlists are updated

Tagging program

What do we have

• Mutagen fully working
• Questionable Tags clarified
• Metadata INI file developed

What are we trying to get

• Program running on Music server to tag everything

What are we not sure of?

• Whether Mutagen works on Music server or not?
• What tags to use to make info in the limited fields provided by Winamp, iTunes look good
• INI parser to get all info out

What do we do

• quick remote test of Mutagen
• list all tags:values in use
• finish parser

Detail

• "track number" is explicit, because it can be error-prone and annoying to rearrange lines
• "conductor" is unseen at this point, so fill it in as performer, can be rearranged later because we have the role filled in.
• the human editor is responsible for using correct characters for various fields (encoding)
• "performer", "composer" etc can be multi-value, use ', ' to separate; use ';' to separate fields
• mark any field without data 'N/A'
• UTF8 with BOM will mess up the first char '[' in the first row
• in ini parser, all strings have to be explicitly unicoded into UTF-8