Livestream Lessons Learned, Again

3 minute read

Always Record to an External Hard Drive

Apparently I forgot my own advice.

Use fast external disks as the destination.

Even if recording to an uncompressed format like ProRes, always use a different drive than the OS’ hard drive.

Even if it’s an SSD.

What Happened?

The result was particularly bad. Large dropped frames, audio/video sync issues, the works. And by works, I mean it’s going to be a ton of work to cleanup too.

I didn’t catch the error until after coming home, because all I was paying attention to was the CPU usage. I wasn’t even streaming and merely using Wirecast as a multicam monitor. CPU usage was always around 30%, and so I thought, “Oh we’re doing really good.”

Wirecast Record to Disk Best Practices

Here are the recommendations from Craig over on a post1 at the Wirecast forums from Nov 2017:

  • Make sure you have the best possible throughput. Avoid using the system disk.
  • Separate internal SCSI drives are OK.
  • Avoid using USB2 drives.
  • If USB3 it should, ideally, be the only device on the bus. Even separate ports may be on the same bus.
  • Best is to use SSD or RAID0 striped drives. 7200 RPM disks may be OK though.
  • Avoid spinning disks below 7200rpm
  • Keep CPU below 80% and below 70% is even better.
  • Make sure the drive never gets filled beyond 80% capacity. Especially for spinning disks, they can slow as they fill.
  • Make sure you’re not confusing variable frame rate with dropped frames. Wirecast records a variable frame rate to avoid dropped frames and keep motion smooth.
  • If you’re going to do post editing consider using MJPEG MOV instead of H.264.

Interestingly, another forum post2 suggests USB3 can be temperamental. One person had dropped frames from a bad cable!

Why It Worked Last Month

Back in May 2018 (during the All-Night concert), I was connected via Thunderbolt to a RAID 0 striped LaCie 4 TB drive. Recording the livestream + HDV camera via Wirecast worked just fine.

However this time, the internal Scratch disk was actually on the same physical SSD as the OS. It did have 500 GB free, but free space was irrelevant.

One Strike and You’re Out… to Make it Better Next Time

Not recording to a dedicated, write disk is a fatal flaw. Let’s put on that growth mindset, shall we?

References

  1. Dropped Frames when recording to disc https://telestreamforum.forumbee.com/r/m2knvp ↩

  2. ISO Dropping Frames https://telestreamforum.forumbee.com/t/80tr9x/iso-dropping-frames ↩

Updated: