MPA

Context:

The pre-listening of projects is possible only if the user has prepared an audio file for it.
We should now implement a solution to easily upload those audio files, and as well assigning them to the correct revision.
It also needs a certain degree of integration with the website.

Details:

We recognize the preview file by its name: we would have a standard name for example "mixdown", and any file of the allowed format which has this name and is present in a revision directory is automatically pushed and used as preview file for this revision, so it can be pre-listened 

• the default name is "mixdown"
• it works also for "Mixdown"; "mix-down" ; "Mix-down"; "mix down" 
• the most recent file is always pushed 
• as soon as the file is added it is auto-pushed
•  allowed formats are .wav and .mp3 

Integration with website:

For the master version, the preview file is also a way of keeping track with the project, because it represent the last version of the master.
On the website this file is displayed in the "project workspace" , and will be displayed also in the workspace of the client, therefore we must define a way to integrate the pre-listening on both ends, so that if it updated on one end it can be grabbed on the other one.

I propose:

• The website will change the location where it stores this pre-listen file and store it in the revision bucket on S3, here the master
• The website will change the file name when uploading and call it mixdown so that the client can recognize it
• When this file is being pushed, it must be considered as a sort of revision, so that it triggers a notification and that the user/ apps can grab it
• It would be good however to have a different type of notification for this