Open ericxtang opened 6 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 0.25 ETH (107.83 USD @ $431.3/ETH) attached to it.
Important to note is that this should not come from the video metadata but rather the video itself like ffprobe is doing it. I guess it means inspecting the NAL units and really see what is in there.
Hi @darkdarkdragon, Pavel Baykov have been talking to me about this in Discord so I created this issue for him. Sorry about the confusion. I will be more clear about this next time when I create a bounty. Thank you for being so active engaging with Livepeer - I'm making more open bounties this week!
Issue Status: 1. Open 2. Cancelled
Work has been started.
These users each claimed they can complete the work by 8 months, 1 week ago. Please review their action plans below:
1) deeghabba has been approved to start work.
Thanks, i try if didn't work I'm so sorry because I'm beginning
Learn more on the Gitcoin Issue Details page.
@deeghabba Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@deeghabba Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Sorry about that, I didn't know how to working.
On Wed, Jul 4, 2018, 11:15 PM Gitcoin.co Bot notifications@github.com wrote:
@deeghabba https://github.com/deeghabba Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
- warning (3 days)
- escalation to mods (6 days)
Funders only: Snooze warnings for 1 day https://gitcoin.co/issue/livepeer/lpms/83/699?snooze=1 | 3 days https://gitcoin.co/issue/livepeer/lpms/83/699?snooze=3 | 5 days https://gitcoin.co/issue/livepeer/lpms/83/699?snooze=5 | 10 days https://gitcoin.co/issue/livepeer/lpms/83/699?snooze=10 | 100 days https://gitcoin.co/issue/livepeer/lpms/83/699?snooze=100
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/livepeer/lpms/issues/83#issuecomment-402519761, or mute the thread https://github.com/notifications/unsubscribe-auth/AYBBdsBUGqiChpml7PFixyCUuWI7jhtdks5uDOosgaJpZM4U5B5m .
Issue Status: 1. Open 2. Cancelled
The funding of 0.25 ETH (120.52 USD @ $482.09/ETH) attached to this issue has been cancelled by the bounty submitter
Is your feature request related to a problem? Please describe. We don't know the parameters of an video segment.
Describe the solution you'd like To implement a video inspector that returns parameters about a HLSSegment.
What we want to understand:
We want to implement a
vidInspector/inspector.go
with a singleInspect
method that takes aHLSSegment
and returns the above parameters. For inspirations, check outlpms_length
. You should follow the example offfmpeg.go
, possibly adding functions to it (by adding to the native libav integration).Describe alternatives you've considered We can also implement an inspector for the RTMP stream, but doing the check for the HLS segment can be used on the broadcaster and the transcoder.
Additional context We are planning to use this inspector to inspect incoming videos, and automatically make choices about the ABR list.
We assume the video parameters will remain the same throughout the entire video. In practice, we'll probably examine the first segment of the video after the RTMP video is segmented into HLS, or if the input is in HLS, simply inspect the first segment.