Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

livepeer / go-livepeer Public

Notifications You must be signed in to change notification settings
Fork 178
Star 553

Code
Issues 207
Pull requests 66
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

Estimate cost using a framerate of 60 rather than 120#2896

Merged

thomshutt merged 3 commits intomasterlivepeer/go-livepeer:masterfrom framerate-120livepeer/go-livepeer:framerate-120Copy head branch name to clipboard

Oct 19, 2023

+5-3

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Oct 19, 2023

Estimate cost using a framerate of 60 rather than 120
thomshutt
committed
Update test with new estimation numbers
thomshutt
committed
Update changelog
thomshutt
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.