Quicktime Audio Error

Deadline
1

I’m trying to use deadlines quicktime submission to generate mov’s from jpg sequences. It works great normally but when I try to add audio (a wav file) it errors out when attempting to add the audio. Any thoughts?

**** ERROR LOG SNIP ****
0: STDOUT: Quicktime Version: 7.62.14.0
0: STDOUT: Input file: “\shade.vfx.com\Isilon\dailies\08.04.09\extreme_peril\ep105\SNO_002_001\jpg\EP105_SNO_002_comp_v01.0999.jpg”
0: STDOUT: Audio file: “\shade.vfx.com\Isilon\jobs\extreme_peril\ep105\shots\SNO_002\audio\SNO_002_audio.wav”
0: STDOUT: Export settings file: “C:\Users\shade\AppData\Local\Frantic Films\Deadline\slave\jobsData\quicktime_export_settings.xml”
0: STDOUT: Codec: QuickTime Movie
0: STDOUT: Start frame: 999
0: STDOUT: End frame: 1231
0: STDOUT: Frame rate: 29.97
0: STDOUT: Output file: “\shade.vfx.com\Isilon\dailies\08.04.09\extreme_peril\ep105\SNO_002_001\EP105_SNO_002_comp_v01.mov”
0: STDOUT:
0: STDOUT: Loading images
---- August 05 2009 – 04:04 PM ----
Repository time: 08/05/2009 16:04:32
---- August 05 2009 – 04:07 PM ----
0: STDOUT: Initializing exporter
0: STDOUT: Loading exporter settings from file
0: STDOUT: Creating movie…
---- August 05 2009 – 04:08 PM ----
0: STDOUT: Loading audio file
0: STDOUT: Adding audio file to movie
0: STDOUT: Error: Unknown Error (COM)
0: An exception occurred: Exception during render: An error occurred in RenderTasks(): Error: Unknown Error (COM) (FranticX.Processes.ManagedProcessAbort) (Deadline.Plugins.RenderPluginException)

at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage) (Deadline.Plugins.RenderPluginException)
0: Unloading plugin: Quicktime
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - Exception during render: An error occurred in RenderTasks(): Error: Unknown Error (COM) (FranticX.Processes.ManagedProcessAbort) (Deadline.Plugins.RenderPluginException)

at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)
**** END SNIP ****

2

Hey there,

This is an issue we’re aware of, and recently fixed. The fix should be in the next release.

Cheers,

  • Jon
3

Awesome, thanks for the response. Don’t mean to be a bother, but any ideas on when the release for this will be?

4

I believe the current plan is to release 4.0 in November, though I could be wrong (Ryan would have to confirm, he’s unfortunately gone for the week). Either way, however, the beta for 4.0 actually just got started, so if you’re needing this fix earlier it might be worth checking out:
viewtopic.php?f=10&t=2778