|SoundCount is the fast and easy way to calculate the total playtime of commercial sound in a sequence or project - for FCP users.
SoundCount is a big timesaver if you are working with commercial sounds. Here what's a creative Avid user says: I have tested out SoundCount and it works great. I can see why you made this app, it will save tons of time and painstaking manual work - I'm sure I can make use of it for this film as although we're in Avid, I just send the audio tracks across as an OMF and import using Automatic Duck and then send out the XML; this is what i just did and it worked fine.
By leveraging the power of the FCP XML format, SoundCount allows the user to create cue sheets from a FCP sequence XML.
There are options to calculate the sound for a single track or multiple tracks. Level settings (0 levels) and audio transitons will be taken into account, though levels can be ignored optionally.
Also several sequences can be loaded to get the total time across several sequences.
The resulting tables can be simple or more detailed.
The actual version also can distinguish between foreground and background sound.
The results can be saved in several formats. Either as plain text files or as tab delimited files. Tab delimited files are handy if you want to import the results into a data base.
Here how it works:
SoundCount has a very simple interface. Before you load an XML you can choose to process levels, to calcultate background sounds, to append sound data to an existing file and whether to get a detailed report or not.
The preferences allow to set up the way of calculating the files and the output a little bit more detailed.
When using background sound processing you set up the level which makes a clip a foreground sound and you can split the result into two files: one for foreground, one for background sounds.
You also can set the type how files are saved: just a plain text report or as tab delimited text for import into databases. With the tab delimited output you get some more options like a column headers and to save the play duration as seconds, the later allows do to time calculations way easier in a data base.
The next version will also allow to process EDLs.
If you load a sequence XML, SoundCount will go thru the tracks and look whether they are empty or not. Then a list of not empty tracks will be displayed.
You can choose a single track or - if you have an XML version 2 input, you additionally can use the "Selection..." option. Using this option will display a second panel.
Using this option SoundCount will do a pre-flight and check each clip in the selected tracks and will mark all channels of the clips except the first one. This way a multiple time calculation for a single clip is avoided.
After all clips are parsed, the table view will show the titles and the frames of usage in and out.
And ask you for a place to save the file. The file name by default is set to the sequence name plus the processed tracks.
You can cancel this and check the "Append Data" buttion to add another sequence.
Depending on the selected process options the saved files will either show only the titles plus the total play time or the parts of the title plus the total playtime.
There is also a currently hidden option to search for special titles only. This needs some setup in FCP. Select the bin where you did store your commercial sounds. Then extend the selection (cmd-key) and select the sequence you want to process. Export those into a single XML.
SoundCount will look for a bin when importing an XML and parse the names of the clips in the bin. During the track and clip search only those clips will be taken into the calculation, which match the names in the bin.
Below an explanation (and some examples) of what currently is resolved and what is not resolved:
The above shows a strange but possible usage of unlinked sounds. All of the overlappings are resolved and counted correctly, but only in case the tracks run in synch. So if track 2 would use another part of the sound, which in theory is possible this part might be ignored or taken as master for the timing
The above example shows a slightly modified "clip 6", which fades out by level setting. This is currently not resolved in a correct way.
A similar result will happen with linked clips. The app currently assumes that linked channels have the same kind of usage thru the channels, i.e. track 1 is master for in/out (0, >0 levels). So if the above clips where linked clips, the result will be, that the time calculation of clip 2, clip 4, clip 5 and clip 6 will be incorrect. A way to solve that, is to unlink the tracks in advance before exporting to XML
If you find bugs (or got feature requests) let me know.
Some issues and limitations.
No known - expect the above. Maybe there are issues I am not aware.
The current version is available "as is" for 95 EUR per license/computer with a 6 month suscription for updates and free tech support. You will get the application as prepaid PayPal download version. After confirmed payment you will receive the software and serial number within about 24 hours.
Click here to download the free trial version (14 days fully functional)
To get a current stable beta: eMail: firstname.lastname@example.org,