Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Edit Youtube 1080p25 livestream in FCP

  • Edit Youtube 1080p25 livestream in FCP

    Posted by Jonas Bengtsson on March 17, 2021 at 3:18 pm

    We do Livestream on theater plays (Theatre School) through two different ways.

    Direct to Youtube 1080p25, x264, 5 Mbit/s or the same settings through restream.io and restream it to Youtube and some times to other platforms as Facebook.

    After the Livestream we download the stream and edit it so all students can have there own copy of the play.

    The problem is.

    YOUTUBE

    While streaming it is 25p but Youtube recode it direct after to 30p witch is what we can download 1080p30 .mp4 it looks ok but little spoky and jumpy when it is big movements on scen.


    RESTREAM.IO

    If we use reastream.io same setting it is possible to download the 1080p25 stream from their cloud. But it is very jumpy, not god at all – colors are god.

    It bothers me that “Keyframe interval: 1.95 seconds” and could that be the jumpy problem.

    Is it possible to fix it?

    GOOGLE TAKEOUT

    This is the method that actually gives the best result i one way. But then we get at .webm 1080p30 (VP9) not original 25 p – the colors looks to saturated compared to original.

    Is it any way to get the original 25p stream from Youtube?

    FCP import VP9 (.webm)

    What tool should I use to recode VP9 (.webm) to what ProRess quality.

    Jonas Bengtsson replied 5 years, 4 months ago 3 Members · 4 Replies
  • 4 Replies
  • Craig Seeman

    March 17, 2021 at 6:43 pm

    I do quite a bit of live streaming and as a general rule I do a local recording. On Mac, I record ProRes (or ProRes LT to save some space). That’s really the best workflow for post production.

    YouTube will generally convert to 30fps (or 60fps) and you will get duplicate frames coming from 25fps (or 50fps).

    Perhaps Apple Compressor can convert to ProRes although I’m not sure if it’ll handle a webm source.

  • Patrick Donegan

    March 17, 2021 at 11:24 pm

    Does this come out of the webcam of this computer?

    What is the source?

    Is it single camera or multi?

    Is it possible for you to record the source directly?

  • Jonas Bengtsson

    March 18, 2021 at 8:12 am

    Its multicam up to 5, 4k cameras Sony RX0 II with blackmagic intensity pro 4K, and decklink mini recorder 4K and Thunderbolt 3. Wirecast and MacBook Pro 16’ 2019.

    The actully stream is 1080p25, so we can use the 4k pictures to crop, zoom 200% and even pan at 1080. In this case we hade about 20 different Shots plus sound, grafiks, prerecorded media etc. and clearly under 50% CPU usage

    The play we livestream could be up to 2-3 hours so we don’t dare to record it localy, risk for overload CPU, a previous problem we solved. Thats why we stream over restream.io, using their recording of the 25p stream insteed of streaming direct to youtube. Youtube recode the 25p stream to 30p after the livestream is finnished. As previously mentioned .


    restream.io

    Contacted them and the jumpy 25p recording of the stream is unfortunately an issu ? they are looking into.

    So it looks like we recode VP9 to ProRes something.

    Compressor can’t recode VP9, what do you recomend.

    If not someone here has a better idea.

  • Jonas Bengtsson

    March 18, 2021 at 3:31 pm

    I got this answer from restream.io

    Hey there! This is Hannah. wave
    I wanted to reach out about an update from our team.
    They stated that it is known that Wirecast under challenging conditions produces messed-up timestamps, so that could be the reason here for the stream recording. Transcoding usually helps to fix this as things like ffmpeg (and some players too) can fix/guess that on the fly for streaming issues.
    This is an issue with timestamps that Wirecast likes to produce sometimes, we don’t have a fix for this directly on our side, as this is a bug from Wirecast that we are actively working on resolving.
    Thanks for all of your patience!!

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy