Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
20 Views

Target usage

Jump to solution

Hello,

What exactly does the target usage setting do? I'm noticing that if I use "BEST_QUALITY" with a bitrate of 4mbit, sometimes the encoder is not fast enough to keep up with a live stream (24 fps).

However, when I am using "BALANCED" with a bitrate of 50mbit, there is no such speed issue.

I'd like to know what exactly the targetusage setting is doing, since it is also not documented anywhere.

 

I'm using a

Intel(R) Core(TM) i7-4700EQ CPU @ 2.40GHz


if that matters.

0 Kudos

Accepted Solutions
Highlighted
20 Views

TargetUsage (TU) is similar to the "preset" concept in FFmpeg.  It provides a quick way to change quality/speed tradeoffs in codec settings.

Assuming you're looking at H264, a TU range of 1-7 is available. 

  • 1=Best quality (but lowest performance)
  • 2=quality boost vs. TU4 at cost of speed
  • 4=settings calibrated for preserving quality and speed
  • 6=speed boost vs. TU4 at slightly lower quality
  • 7=best speed (but with larger quality drop) 

(With TU 3 and 5 as points between those described above.)

Here are some starting points which have more info on TargetUsage behavior:

The next level of detail is harder to get because it can change between hardware and driver versions.  However, the relationships between the TUs should remain similar to the references above.  Is this sufficient information?

Regards, Jeff

 

View solution in original post

0 Kudos
2 Replies
Highlighted
21 Views

TargetUsage (TU) is similar to the "preset" concept in FFmpeg.  It provides a quick way to change quality/speed tradeoffs in codec settings.

Assuming you're looking at H264, a TU range of 1-7 is available. 

  • 1=Best quality (but lowest performance)
  • 2=quality boost vs. TU4 at cost of speed
  • 4=settings calibrated for preserving quality and speed
  • 6=speed boost vs. TU4 at slightly lower quality
  • 7=best speed (but with larger quality drop) 

(With TU 3 and 5 as points between those described above.)

Here are some starting points which have more info on TargetUsage behavior:

The next level of detail is harder to get because it can change between hardware and driver versions.  However, the relationships between the TUs should remain similar to the references above.  Is this sufficient information?

Regards, Jeff

 

View solution in original post

0 Kudos
Highlighted
Beginner
20 Views

Thank you Jeff, that's enough information. I will have to fine-tune the setting to find the perfect fit for my application. I understand now also that the behavior may be different for each type of hardware.

Best regards,

Chris

0 Kudos