leandromoreira / leandromoreira/ffmpeg-libav-tutorial

Live streaming to Web Browser or Qt desktop app (Widget or QML)

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
11k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

First thing. Thank you for your awsome work. My purpose is to study various streaming techniques, band witch usage, recovery over poor connections, cpu utilization etc.

I have ROS.org project where I am reading raw frames from few PoE cameras. What I like to do is implement implement simple TCP server that could except connections from web browser (or desktop Qi app) to view remote video. I have extensive expirience with network programming.

What I am missing and hoping someone can help me understand or point me to correct source, how to format trades to any modern browser can display it. What are best and most coming codecs used. I do not care about sound with video so this might be and option to enable so save some bandwidth

Thank you all for any input and suggestions

Contributor guide

No contributing guide indexed for this repository

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

The issue names no files, tests, or entry points. First clarify whether the goal is a browser client, a Qt desktop app, or both, then define the streaming protocol, codec, connection recovery behavior, and a concrete completion criterion for raw frames from the PoE cameras.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
audio-video-rtc
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.