What are your input and output sizes, fps, codec settings, and devices used?

Are you testing with the same content in both?

Are you sure that the input and output sizes are same in both 2.5 and 3.1?

Could you please compare 2.5 and 3.1 by keeping the input and output sizes same in both? Keep input and output to same 720x420 size and compare the CPU usage.

Let me know the result.

Alright.

Could you please compare 2.5 and 3.1 by keeping the input and output sizes same in both - 720x480 ? I mean do not resize.

Can you please check output FPS by both FMLE 2.5 and FMLE 3.0.

Actually in FMLE 2.5, resize filter was single core resulting in lesser output FPS so in FMLE 3.0 resize filter was improved to use multicores resulting in more CPU usage but more Output FPS.

if you dont use Resize filter than performance of FMLE 2.5 and FMLE 3.0 should be same but if you are resizing Video then FMLE 3.0 will use more CPU but results in more output FPS.

Can you please share the snapshot of FMLE statistics for 2.5 and FMLE 3.0 to confirm this.

I have been pulling my hair out for two days on this same exact issue!  I've learned a few additional things, so I figured I'd add it here in case in helps someone or someone can use it to help me.

I am experiencing the same problem of maxed out CPU usage on two machines using either 3.1 or 3.2 (same with both). One machine is a Core Duo and the other is a Core i7 (Q 720 @ 1.6 GHz each).  It's crazy that it even maxes out all 8 CPU threads (hyperthreaded dual duo cores!).

Here's what I learned:

1. Doesn't matter between H.264 and VP6.

2. Upon Reboot, you can get about 5 minutes of encode before the CPU jumps to high 90s and causes stuttering encode.

3. Core thread usage continues to increase.

4. If the output is the same size as the input, the CPU usage will remain stable. If however, you change the output size (resizing) then the CPU will begin to spike.  If you stop it before it gets too high, and restart it with the size the same again, it will stay stable, but not drop back down to where it was before (meaning that FME is not letting go of the CPU threads it started using when resizing?).

5. If I use the webcam as the input source (640x480) and resize to a 16:9 frame size, I can encode indefinitely without going over 20% CPU, it's only if I hook up a camera via Firewire that I max the CPU out.

6. Elevating the priority in Task Manager of the FME process has no effect.

I hope this can be addressed, as it's obviously some kind of a problem.  A Core i7 computer should be good enough to encode and resize video!  For now, I will have to revert back to 2.5, which runs fine.

Are these running OSX or Windows?