Intro
Overview New in V15
Apps
Overview Configuration
<camera>
Overview Embedding Configuration Custom Interface JS Methods JS Events Collecting Videos
<photobooth>
Overview Embedding Configuration Custom Interface JS Methods JS Events
<microphone>
Overview Embedding Configuration Custom Interface JS Methods JS Events Collecting Audio
<room>
Overview Embedding Configuration Custom Interface JS Methods JS Events
<player>
Overview Embedding Configuration JS Methods & Events
<wall>
Overview Embedding Configuration JS Methods
<photo>
Overview Embedding
REST API
Overview
Assets
List Assets Show Asset Update Asset Delete Asset
Apps
List Apps Show App Create App Update App
Media Factories
List Media Factories Show Media Factory Create Media Factory Update Media Factory
Asset Responses
Video Object Photo Object Audio Object
Rooms
List Rooms Create Room Show Room Update Room Delete Room
There are four ways to get the the files generated from a recording. Which one is most appropriate for you will depend on the type of application you're building and your comfort with coding.

Manual download
Use a <form> element
Use the JS API
Use a server callback

Manually Downloading

All published recordings can be manually downloaded from CameraTag.com. Clicking on the name of an App in the admin panel will present a list of published assets. Clicking on an individual asset will open a lightbox withe the asset on the left and various actions (inlcuding download) on the right.

Note that you can configure email notifications in the App's setup page so you will know when new assets are available for download. To learn more about email notifications please see the Email Notification documentation.

Using a <form> element

Your CameraTag will create two files for each recording
  • an mp3 audio file
  • a png image of the audio waveform
The easiest way to retrive the recorded files is to place your CameraTag in a form on your website. Once the user has recorded a file the cameratag will automatically create and populate a hidden input field containing the URLs for each file created.

For example, if you included the following a CameraTag named "MyCamera" that recorded in 360p:

<form action='/some_url'>
  <microphone id='MyRecorder1' data-uuid='[YOUR_APP_UUID]'></microphone>
</form>
Your form would post as if the HTML had looked like this: 
<form action='/some_url'>
  <input type='hidden' name='MyMicrophone[uuid]' value='[AUDIO_UUID]'/>
  <input type='hidden' name='MyMicrophone[mp3_url]' value='http://url.to.your/mp3_audio' />
  <input type='hidden' name='MyMicrophone[waveform]' value='http://url.to.your/waveform.png' />
</form>

Using the JS API

After a user has published their recording you can access the URLs of the associated files using the JS API. The getVideo() method returns a JS object containing data about the recorded audio including a formats array. For each reocridng format you've chosen for your camera you will see a corresponding object in the formats array containg the format's file URLs 
CameraTag.observe('MyRecorder1', 'initialized', function(){
  var myMicrophone = CameraTag.microphones["MyRecorder1"];
  var myAudio = myCamera.getAudio();
  var mp3_url = myAudio.mp3_url
})

Using a server callback

You can have the CameraTag servers automatically POST audio data to your servers when a user publishes a recording using one of your microphones. To do so, simply enter the URL that you would like us to POST the data to in the "Callback URL" field of your Camera's settings page. You can learn more about the data that is POSTED here