0

Help! What Am I Doing Wrong (Specs Included)

Sometimes Wirecast records and stream at 30fps and it is awesome when it does, but other times I open Wirecast and it will only stream/record in anywhere from 11-6 fps ... No rhyme or reason. I do not change any settings from one day to the next.

 

Sometimes, I can delete the camera and then re-add them and that does it, sometimes I close and restart a few times and that does it ... sometimes I have to close it down and use mimoLive instead.

I hope someone can offer some guidance here is my technical information and settings

 

Mac - 2018 Mac mini with 32Gb Ram and 256Gb SSD

OS - Catalina 10.15.4 (19E287)

Processor - 3.2 GHz 6-Core Intel Core i7

Camera is Logitech Brio 4k

I am attempting to record and stream in 720p at 30 frames per second

Wirecast Version: 13.1.2

 

  

You can see from the images above that I have 30 fps set in both the video display rate and the output destination as well as the camera setting itself.

 

What am I doing wrong and how can I fix it. Wirecast really is a groovy app and I hope I can get it to where it is reliable for me to use daily.

7replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
    • Gary Byrd
    • Gary_Byrd
    • 2 yrs ago
    • Reported - view

    NOTE:

    I could not record or stream today with more than 14 frames per second using the document I had used the last 3 days.

    I had to delete that document and create a new document and then I could stream in 30fps.

     

    I guess I don't mind doing this every day, its just cumbersome to do and I don't think that its supposed to work that way.

    Like
    • Matthew Potter
    • Creative Technologist & Problem
    • Matthew_Potter
    • 2 yrs ago
    • Reported - view

    Gary Byrd Interesting resolution. This may be similar to some of the critical caching issues that Greg Kuhnert has been reporting on.

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 2 yrs ago
    • Reported - view

    Gary Byrd I'm not sure if that's the complete information. Any other graphics or clips or sources? What else is running on the computer? There's no reason for the frame rate to vary that much from use to use unless something else is in play. Encoder settings? Canvas size?
    Sorry but there's just not enough information. You need to describe as if you wanted someone to match everything.

    Like
    • Gary Byrd
    • Gary_Byrd
    • 2 yrs ago
    • Reported - view

    CraigS you need more info? 
     

    canvas size 1280x720

    wirecast, safari, loopback ... nothing else

    encoder settings? Streaming to YouTube at 720, 30 FPS, 2mb a second

    encoder settings- mp4, 720p30 2mbps, h.264

    NOTE: I either stream or record, never both simultaneously 


    Again, from day to day, it may record in 30fps, or it may only do 16fps. Same file used each day, my shots are all built for some time and they do not change. 
     

    In the meantime, I can just rebuild my shots each morning. When I create a new document and rebuild my shots each day I get it to record in 30fps. 
    It’s a pain in the butt to have to do that each day but at least Wirecast does not have audio/video syncing issues like mimoLive does. 

    Like
    • CraigSModerator
    • Telestream Desktop Forum Moderator
    • CraigS
    • 2 yrs ago
    • Reported - view

    Gary Byrd It's not clear what the contents of your shots are.
    Why do you have Safari open?
    What are you doing with Loopback?
    It's possible some sequence of events might be the cause.
    You have to describe so someone can duplicate what you are doing.

    Like
    • Greg Kuhnert
    • wirecast.community
    • Greg_Kuhnert
    • 2 yrs ago
    • Reported - view
    Gary Byrd said:
    I could not record or stream today with more than 14 frames per second using the document I had used the last 3 days.

    This is an interesting thread for a number of reasons. I have some data from a recent bad broadcast, which points to similar symptoms.

    I capture the console log from Wirecast. There are some regular "known" messages that are seen every time you use Wirecast that I am familiar with. If I exclude those, there are a lot of H.264 errors in my last broadcast.

    I am going to include a small fragment of the console log below. Other interesting points to note:

    1. CPU load warnings were happening during the broadcast. Yellow only. I couldn't see the number, it was too far away from where I was watching a camera.
    2. Rendezvous guests were experiencing out of sync audio, and stuttering in video.
    3. Mac started beach balling mid-broadcast.

    I'll be creating a ticket with all of this data for investigation in the near future... Why is it related to this post? I ee errors about frame rates being different from configured frame rates ... and it keeps changing.... thought it might help to look at this.

    Greg Kuhnert

     

    [OpenH264] this = 0x0x7fe459051900, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe459051900, Warning:Actual input framerate 0.000000 is different from framerate in setting 24.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe46cc9bdb0, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe46cc9bdb0, Warning:Actual input framerate 0.000000 is different from framerate in setting 24.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:Actual input framerate 0.000000 is different from framerate in setting 24.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:[Rc] iDid = 0,iContinualSkipFrames(3) is large

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:[Rc] iDid = 0,iContinualSkipFrames(6) is large

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:[Rc] iDid = 0,iContinualSkipFrames(9) is large

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:[Rc] iDid = 0,iContinualSkipFrames(12) is large

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:[Rc] iDid = 0,iContinualSkipFrames(3) is large

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:[Rc] iDid = 0,iContinualSkipFrames(6) is large

    [OpenH264] this = 0x0x7fe44f3f4590, Warning:Actual input framerate 17.526390 is different from framerate in setting 24.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe44bd6baa0, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe46de6ff90, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe46de6ff90, Warning:Actual input framerate 0.000000 is different from framerate in setting 24.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe44d8dcec0, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe44d8dcec0, Warning:Actual input framerate 0.000000 is different from framerate in setting 25.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe49d0af850, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe49d084140, Warning:Change QP Range from(0,51) to (12,42)

    [OpenH264] this = 0x0x7fe49d0af850, Warning:Actual input framerate 0.000000 is different from framerate in setting 13.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe49d084140, Warning:Actual input framerate 0.000000 is different from framerate in setting 14.000000, suggest to use other rate control modes

    [OpenH264] this = 0x0x7fe49d084140, Warning:[Rc] iDid = 0,iContinualSkipFrames(3) is large

    Like
    • Greg Kuhnert
    • wirecast.community
    • Greg_Kuhnert
    • 2 yrs ago
    • Reported - view

    CraigS

    For your information, the above warnings to the console appear to be linked with capturing from a 2nd monitor on my iMac. Just sharing with you in case it is useful data.

    @greg_kuhnert

    Like
Like Follow
  • 2 yrs agoLast active
  • 7Replies
  • 85Views
  • 4 Following