FORUMS: list search recent posts

Problem Encoding Apple ProRes 422 (HQ) to WMV

COW Forums : Telestream Episode

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Michael Lawson
Problem Encoding Apple ProRes 422 (HQ) to WMV
on Nov 12, 2009 at 3:50:11 pm

I am submitting my film to an online distributor, however, they require that it be a WMV file. I exported my film from FCP as an Apple ProRess 422 (HQ) file. I put the mov. file into Episode Pro and tried encoding it to WMV, however Episode Pro keeps telling me, "job died (10) after 3 retries." The settings I am using are the following:

Output Format: WMV File Extension: wmv
Video: Encode
Audio: Encode
Time Code: Same as Source

Bandwidth Settings: 2-pass VBR Peak Constrained
Peak rate: 5000 kbit/s
Average rate: 5000 kbit/s
VBV buffer size: 3.0
Smoothness/crispness: 80
Profile Settings: Main Profile
Keyframe Control: Natural and Forced Keyframes
Keyframe distance: 4.0 seconds
Number of B-frames: 2
Encoding Complexity: Offline Normal

WMA Version: WMA 9 Professional
Coding Method: One pass, constant bit rate (CBR)
128 kbps, 44.1 kHz, Stereo, 24 bit

If anyone could give me just the slightest insight, it would be very well appreciated.

Return to posts index

Michael Lawson
Re: Problem Encoding Apple ProRes 422 (HQ) to WMV
on Nov 12, 2009 at 11:23:33 pm

Come on, people answer questions on here all of the time. I've posted numerous times on this site and people respond back asking me where I'm sending it to or what I'm doing or what the specs are. I've given you guys everything this time around and nobody can give me anything. Come on, where's creative cow's best?

Filmmaking is like a religion.

Return to posts index

Craig Seeman
Re: Problem Encoding Apple ProRes 422 (HQ) to WMV
on Nov 13, 2009 at 12:31:55 am

Make sure you're using Episode 5.3.

The settings don't seem to make sense. You're using 2 Pass VBR Peak Constrained and you've set the peak to match the average. That's not VBR. You also can't set Smoothness/crispness in 2 pass encodes.

It's always good to start with a template and do a test encode first. Then if it fails after modifying, you know it's a settings issue. If it fails with the template it may be another issue.

It's hard to venture a guess when the settings themselves don't seem to make sense.

Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2018 All Rights Reserved