1

BETA 13 - Initial thoughts

Testing Beta 13 (602.a0994769)

 

I've done a bit of testing this morning, but my upload speed was bad - I'll try later when I can connect via ethernet.

 

I really like what has been done with the master shots. It's quite subtle, but it feels more responsive. The live icons aren't something we all definitely need but they are cool. Do we have the option of switching these off if we're trying to conserve GPU?

All in all, Wirecast seems less sluggish and more streamlined which is great.

Unfortunately, Wirecast crashed just after I did a Facebook speed optimization test and created a post. I sent in a report.

When I reopened Wirecast, it recovered the documents, but it "forgot" the name of them and called then "recovered". It would be good if it remembered the name like other programs do.

It seems that the bug that stopped a document being opened when they contained emojis has been fixed. That might have been fixed a while ago, but good that it's been fixed. I've always found Wirecast documents get corrupted very easily. I assume with this latest update that this has been fixed. Could you give more info on this? Because if the document files are more stable and far less easy to become corrupted, then this is GREAT!

I love the idea of the Facebook speed optimization test. How long should this test take? It took a long time for me - like 5 minutes. If this is the norm, I think having a message to say the usual time would be good. I didn't realise you could specify the location of the Facebook server via the API. Once this has been done, is it possible to set the location for future broadcasts, or do we have to do the speed test each time? It would be good if we could specify.

It's probably due to my poor upload speed (although it was 4Mbps - so not awful) but I was getting bad connection issues. I'll test later.

Are there any updates to Rendezvous? I'll test this later, but this was one area that I felt was lacking in previous versions of Wirecast.

This is only a little thing, but I think a change of fonts would be good in the UI. It still looks a little clunky and old fashioned. For example, the font used when I type the live video post looks really old. Just a bit of UI love would be great.

And finally, I'd love to talk about some features that I still think are missing. I know the beta discussion is to talk about the current build and to find any bugs. But I'd love a chat about things that Wirecast really should have. Other tools like vMix & Ecamm Live and web tools like BeLive and StreamYard all have integrated comments. I know there is NewBlue Titler, but a simple way for us to see and highlight comments from Facebook, YouTube, Periscope and when the API supports it, LinkedIn. This is especially important for those of us who produce and host our shows.

5replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Ian Anderson Gray said:
    Are there any updates to Rendezvous? 

     Some things are being done server-side. 

    Ian Anderson Gray said:
    And finally, I'd love to talk about some features that I still think are missing.

     For future feature requests please do post them in the Public Feature Request Forum. We're always interested in what users have to say. 

    Reply Like
  • We really appreciate your beta report. Certainly, keep reporting. Thanks.

    Reply Like
  • HI Ian, Thank you for the feedback! This is great, and keep it coming. To answer a few more of your other questions/comments :


    <Unfortunately, Wirecast crashed just after I did a Facebook speed optimization test and created a post. I sent in a report.>: We are looking into your report. Have you been able to reproduce that or was this a one-time crash. Any other info you can give about that would be helpful.

    <When I reopened Wirecast, it recovered the documents, but it "forgot" the name of them and called then "recovered". It would be good if it remembered the name like other programs do.> . Good feedback.

    <I love the idea of the Facebook speed optimization test. How long should this test take? >  5-10 minutes is the norm.  It's all driven by FB though, so we don't really know the time.  They run through a series of tests and then decide which is the best location- so we don't really have a good time estimate. Though I agree - it would be worth letting the user know that this could take several minutes. 

    <Once this has been done, is it possible to set the location for future broadcasts, or do we have to do the speed test each time?> We have found the results change when running it one day to the next. However, it's linked to a specific output setting once run, until the speed test is run again. So if you do reuse that output setting it does reuse the optimization. It's probably best used by running 20-30 minutes before your live stream for a one-time optimization, rather than reusing it. 

    <This is only a little thing, but I think a change of fonts would be good in the UI.> I would love to talk to you more about this - I'll contact you via direct message to get more info from you.

    <And finally, I'd love to talk about some features that I still think are missing. > Again, - I'll contact you via direct message to get more info from you.

    Thank you again for your feedback - it's very helpful

    Reply Like
  • Thanks CraigS and lynn_elliott

    I've not had the chance to test and try and reproduce the crash. I'll let you know if it happens again. But I did send in a report, so hopefully, you have that.

    If it takes 5-10 mins, then I do think a dialogue box with a message saying this could take 5-10 mins with OK/Cancel would be good.

    Happy to chat to you about fonts and other missing features. I'm away on vacation shortly, so it might need to wait a week.

    Thanks!

    Reply Like
Like1 Follow
  • 1 Likes
  • 3 mths agoLast active
  • 5Replies
  • 75Views
  • 3 Following