> For the complete documentation index, see [llms.txt](https://docs.v-nova.com/technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v-nova.com/technologies/mpeg-5.lcevc/v-nova-lcevc/lcevc-best-practices.md).

# Best practices

This page gives advice on how to get the very best results when applying LCEVC-enhancement to your encoding workflows.

## Introduction

V-Nova LCEVC is a comprehensive SDK for enhancing any encoding and decoding workflow with MPEG-5 Part 2 Low Complexity Enhancement Video Coding.&#x20;

LCEVC provides a boost to the compression efficiency of any existing or future video codec, to achieve higher quality at up to 40% lower bitrates, while accelerating encoding and reducing compute costs by up to 4x.

![LCECV: Less Bitrate Less Processing Power](https://content.gitbook.com/content/II3HaKNLFEqGvuN59zwF/blobs/rB7p4H5DBlop7SSmB8wa/LCEVC_bitrate_comp_power.png)

## How to select the optimal bitrates and resolutions for encoding with LCEVC

Our Video Quality Framework allows us to define the ideal LCEVC-enhanced ABR ladder for the specific business requirements of a video service provider.&#x20;

A Convex Hull approach that combines VMAF and subjective video quality assessment has been used to determine the best combination of bitrate/resolution for specific content and base codec.&#x20;

The charts below provides a guideline, based on V-Nova's experience across a broad range of content.

![Native H.264 vs LCEVC H.264](https://content.gitbook.com/content/II3HaKNLFEqGvuN59zwF/blobs/LCYGEmuqHvZATVqb4Adf/LCEVC_H.264_COMPARISON.jpg)

![Native H.265 vs LCEVC H.265](https://content.gitbook.com/content/II3HaKNLFEqGvuN59zwF/blobs/EZYcCDuxwhrEXFu7toRV/LCEVC_H.265_COMPARISON.jpg)

## Try our LCEVC-enhanced ABR Ladder Builder

The extensive testing and analysis above has been incorporated into easy-to-use excel sheets that provide initial suggestions for how to select optimal LCEVC-enhanced adaptive streaming profiles for your use case. Click on the links below to try them.

* ### [LCEVC-enhanced H.264/AVC](https://docs-vnova-com.s3.eu-west-1.amazonaws.com/LCEVC+%26+H.264+ABR+Ladder+Builder+\(web\).xlsx)
* ### [LCEVC-enhanced H.265/HEVC](https://docs-vnova-com.s3.eu-west-1.amazonaws.com/LCEVC+%26+H.265+ABR+Ladder+Builder+\(web\).xlsx)

## An example LCEVC-enhanced ABR ladder

The table below provides an example, from a report written by industry analyst Jan Ozer.&#x20;

The H.264 ABR Ladder profiles, encoded using x264 (medium preset), are in line what recommended by Apple in the HLS Authoring Specification.&#x20;

The LCEVC H.264 ABR Ladder profiles have been opt**i**mised to achieve both a quality uplift and a reduction in the total average bitrate streamed.

The amount of motion in the source can also determine encoding settings.&#x20;

![Example of H.264 ABR ladder vs LCEVC H.264](https://content.gitbook.com/content/II3HaKNLFEqGvuN59zwF/blobs/NnSTWPp0Bvo0P6vz3ptD/image.png)

With LCEVC the ABR Ladder profiles have been reduced from 7 to 6, reducing the total bitrate streamed by 27% (whilst achieving a better quality).&#x20;

Jan Ozer's report confirms that **LCEVC generates both bandwidth** **savings** - between 19% to 22% reduction in the total average bitrate streamed, based on typical playback frequency of profiles -  **and improvement in overall quality of experience**, measures both subjectively via Mean Opinion Score (MOS) and with VMAF.

Full details and results are available [here](https://streaminglearningcenter.com/codecs/lcevc-excels-in-full-ladder-live-use-case-testing.html).&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v-nova.com/technologies/mpeg-5.lcevc/v-nova-lcevc/lcevc-best-practices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
