When you are using a Dual Source recording from two different client machines and both machines have an audio input, there could be a problem in the resulting generated media files. I have seen this problem myself where we used non Podcast Capture dual source recordings with in each input an audio track. In the resulting files, both audio tracks are combined and there almost always is a slight sync difference. The result is an echo-like effect. One solution would be to disable the audio input on the screen recording client, but that would have presented some problems. I wanted to be able to archive the screen recordings with the audio track included, and there are some situation when people want to only record the screen and not have to change anything about the audio inputs. What I did was as simple few extra actions in the workflow that removed the audio track in the primary recording, after the file was already archived. Add this to your template.plist file:
delete_extra_audio
arguments
audio
$$GLOBAL::Library Bundle Path$$/Contents/Resources/Working/$$SOURCE::0::Filename$$
$$GLOBAL::Library Bundle Path$$/Contents/Resources/Working/primary-no-audio.mov
command
/usr/libexec/podcastproducer/qttrackdelete
dependsOnTasks
preflight
Make sure to add 'delete_extra_audio' the import-plugin-dualvideo-generate action's dependsOnTask list and to set the primary_input argument to the 'primary-no-audio.mov' file, like this:
import-plugin-dualvideo-generate
arguments
pip
--prb=$$GLOBAL::Library Bundle Path$$
--primary_input=primary-no-audio.mov
--secondary_input=$$SOURCE::1::Filename$$
--output=import-plugin-dualvideo-generated.mov
--pqz=$$GLOBAL::Workflow Resource Path$$/Compositions/Theater.pqz
--enable_automatic_transitions
command
/usr/bin/pcastaction
dependsOnTasks
delete_extra_audio
Now the archive actions still archive the intact media files, but the dual video will have correct audio.