livepeer / livepeer/go-livepeer

Add higher-resolution video profiles to the default set of options

Open
#3,785 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: triage
Dominant language
Go
Stars
586
Forks
226
Avg merge
1d 17h
Merged PRs (30d)
19

Description

Is your feature request related to a problem? Please describe.

With 4320p (8K) video emerging onto the global scene, we need to be able to allow people to easily configure higher resolution renditions.

Currently, the highest resolution offered as part of the default options is 720p (HD) at 60fps, which is only 55,296,000 pixels per second. See screenshot.

Allowing, for example, 4320p streams to be transcoded into 2160p (4K), 1440p, and 1080p (FullHD) would increase the potential number of pixels per second being processed:

  • 1080p (FullHD) at 60fps = 124,416,000 pixels per second (2.25x the current maximum)
  • 1440p at 60fps = 221,184,000 pixels per second (4x the current maximum)
  • 2160p (4K) at 60fps = 497,664,000 pixels per second (9x the current maximum)

Describe the solution you'd like

Add the following profiles to the default list of options proposed when calling 15. Set broadcast config

13		P1080p30fps16x9
14		P1080p60fps16x9
15		P1440p30fps16x9
16		P1440p60fps16x9
17		P2160p30fps16x9
18		P2160p60fps16x9

Describe alternatives you've considered

Of course I have considered not adding these, and keeping things as they are.

But this feels like it might miss an opportunity to demonstrate the powerful capabilities of Livepeer's Transcoding network, which ought really to be able to process these kinds of dimensions with ease, and also result in greater revenue for Orchestrators and Delegators. These default options were configured a long time ago, when 1080p was effectively the highest available resolution, and so they made sense. But things have moved on a lot since then, with most modern smartphone cameras capable of at least 4K video capture.

Additional context

This screenshot shows one of the questions asked when a Gateway user calls option 15. Set broadcast config in the livepeer_cli:

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the livepeer_cli implementation of option 15, Set broadcast config, and the default profile list it presents. Add the six requested 1080p, 1440p, and 2160p profiles, then verify that the CLI shows them as options 13 through 18.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.