Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Begin transcode right after PUSH_END trigger #54

Merged
merged 8 commits into from
Oct 10, 2022
Merged

Conversation

emranemran
Copy link
Collaborator

Begin transcode right after PUSH_END trigger is receieved after segmentation is completed:

  • generate transcodeRequest in SegmentingPushEnd handler (since transcodeRequest will not be generated from the HTTP API endpoint)
  • update Segmenting cache Store function to store additional fields which will be used in transcodeRequest above

segmentation is completed:

* generate transcodeRequest in SegmentingPushEnd handler (since
  transcodeRequest will not be generated from the HTTP API endpoint)

* update Segmenting cache Store function to store additional fields
  which will be used in transcodeRequest above
SourceFile: si.SourceFile,
CallbackUrl: si.CallbackUrl,
}
go handlers.RunTranscodeProcess(d.MistClient, transcodeRequest)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! I think for the /vod API behavior, you might want to wrap this into a local helper which handles the results sending the appropriate callbacks to Studio etc. I guess that's somewhat what you've done on your local change that you mentioned tho?

Btw does this StreamInfo have the "probing" information of the file? If so, should be really easy to generate the profiles copying that logic from task-runner

@codecov
Copy link

codecov bot commented Oct 7, 2022

Codecov Report

Merging #54 (bb98537) into main (1cbf6db) will decrease coverage by 1.25083%.
The diff coverage is 12.25806%.

Impacted file tree graph

@@                 Coverage Diff                 @@
##                main         #54         +/-   ##
===================================================
- Coverage   36.42447%   35.17364%   -1.25084%     
===================================================
  Files             17          17                 
  Lines           1046        1123         +77     
===================================================
+ Hits             381         395         +14     
- Misses           618         681         +63     
  Partials          47          47                 
Impacted Files Coverage Δ
api/http.go 54.28571% <0.00000%> (-1.59665%) ⬇️
clients/mist_client.go 45.81498% <0.00000%> (-4.67046%) ⬇️
clients/mist_client_mock.go 0.00000% <0.00000%> (ø)
handlers/misttriggers/push_end.go 29.00763% <0.00000%> (-4.32570%) ⬇️
handlers/misttriggers/triggers.go 67.85714% <ø> (+48.46938%) ⬆️
handlers/transcode.go 5.78947% <0.00000%> (-4.58789%) ⬇️
cache/segmenting.go 74.19355% <61.11111%> (-25.80645%) ⬇️
handlers/upload.go 49.33333% <100.00000%> (+5.21567%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1cbf6db...bb98537. Read the comment docs.

Impacted Files Coverage Δ
api/http.go 54.28571% <0.00000%> (-1.59665%) ⬇️
clients/mist_client.go 45.81498% <0.00000%> (-4.67046%) ⬇️
clients/mist_client_mock.go 0.00000% <0.00000%> (ø)
handlers/misttriggers/push_end.go 29.00763% <0.00000%> (-4.32570%) ⬇️
handlers/misttriggers/triggers.go 67.85714% <ø> (+48.46938%) ⬆️
handlers/transcode.go 5.78947% <0.00000%> (-4.58789%) ⬇️
cache/segmenting.go 74.19355% <61.11111%> (-25.80645%) ⬇️
handlers/upload.go 49.33333% <100.00000%> (+5.21567%) ⬆️

@emranemran emranemran marked this pull request as ready for review October 10, 2022 04:53
@thomshutt thomshutt merged commit 26265bd into main Oct 10, 2022
@thomshutt thomshutt deleted the emran/async-transcode branch October 10, 2022 12:50
@victorges
Copy link
Member

victorges commented Oct 10, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants