Mark Franken is an award-winning software developer and founder of Sounds In Sync, specializing in cutting edge solutions for sound post-production. His work as a sound editor on some of the top feature films and television shows has inspired him to develop these programs that are used by sound professionals word-wide. He can be contacted via the Sounds In Sync website.
Website URL: http://www.soundsinsync.com/contact
Have you been given a folder of WAV files and wished there was an easy way of loading them into a Pro Tools session with them all located to their individual timestamps? Now with EdiLoad v3.4 you can do just this using it’s WAV File List window.
Have you ever wished you could see where a scene starts and ends in your Pro Tools timeline? Now with EdiLoad v3.4 it’s even easier to generate a Pro Tools track containing clips showing where each scene starts and ends. You can also include the description of each scene within the clip name.
Have you been given an AAF where the location audio clips have been taken from the camera? Wondering how you can conform or link these clips to your multi-track location WAV files?
In the following video I run through how EdiLoad can be used to modify different elements of an Edit List, either when imported from an EDL or AAF, so that each event in the list will link to the correct location WAV file.
Are you having problems getting an AAF or OMF that contains the audio that you need, or that can be used to expand your location WAV files in Pro Tools?
In the following video I run through everything you need to know. I’ll explain why you would want to conform your original location WAV files (rather than use an AAF or OMF), how to conform your rushes using EdiLoad and the Pro Tools field recorder functions, and finally, one of the sync issues you might encounter when performing this process.
Being able to transfer ADR cue data from one system or application to another can save hours of manual cueing, or copy and pasting of individual data fields. However, the most common way of transferring this data is via a text file, and there are several things about this method that can get you stuck. When dealing with non-English text, or transferring between different operating systems, there’s a good chance your data won’t come across as expected.
While printing ADR cues in EdiCue, text characters can sometimes be displayed incorrectly. If this is happening to you, you probably have a 'text encoding' issue.