
Please Post Feature Requests in The Public Feature Requests
For general feature requests, please post them in the public feature requests section.
This will allow more users to chime in on it!
-
Hi Rory.
I've already installed, and the world didn't end - but more testing to come.
My primary concern at the moment is the outstanding Wirecast Go Rendezvous bug with pixelated guests using newer iPhone models. Does Telestream have access to apple's TestFlight programme, to allow beta distribution for IOS? If so, I would be more than willing to kick the tyres on any possible solutions to this issue.
Regards,
Greg. -
Greg Kuhnert
Hi Greg,
Unfortunately that is a bug in webrtc (the underlying technology behind Rendezvous). The issue should only occur when a single guest is connected to the Rendezvous session, in our testing it does not occur when 2+ guests are connected.
I'll keep you in mind if we do an external Wirecast Go beta.
-
Hi Rory. Thanks for the feedback.
I understand your comment about webrtc. But what doesn't make sense is the fact this works with some devices, and not others. What is the factor that causes it to cause issues on some devices and not others?
As a interim measure - can wirecast detect the fault situation, and add a "virtual" additional fake local webrtc guest, that is just sharing a black screen? At least something like that would be a workaround that would simplify the process for someone trying to use Rendezvous today.
Regards,
Greg. -
Greg Kuhnert
Thank you for your feedback.
But what doesn't make sense is the fact this works with some devices, and not others. What is the factor that causes it to cause issues on some devices and not others?
Different iOS devices send different video resolutions, the newer devices send a resolution that webrtc doesn't like which results in the pixelated/garbled video feed. The reason that adding another device corrects the video feed is because we downscale the video resolutions when additional peers join the session for performance reasons. We'll take your suggested workaround into consideration when working on a fix to this issue, thanks!
-
Rory Maloney - I got to thinking more about the Rendezvous webrtc issue. You mentioned that webrtc doesn't like the resolutions of newer IOS devices... but you downscale the resolutions when additional peers join for performance reasons. Is it wirecast or the Wirecast GO app that decides to downscale? How is that decision made and why not make that decision to downscale the default? How easy would that be to code?
Sorry if I am hammering on about this. Rendezvous is a great capability to have natively built into wirecast, but it does not add much value if it doesn't work for a large portion of your market.
-
and I looked again today, and found a post https://developers.google.com/web/updates/2012/12/WebRTC-hits-Firefox-Android-and-iOS#resolution_constraints on webrtc - This capability has been around since 2012 to put a constraint on resolution... Wouldn't this be a simple fix to implement?
-
Greg Kuhnert said:
Is it wirecast or the Wirecast GO app that decides to downscale?The rendezvous server (webrtc) is a factor. Note than when you send a link it points to a server.
Such as:
https://rendezvous.telestream.net/(etc) -
CraigS said:
Greg Kuhnert said:
Is it wirecast or the Wirecast GO app that decides to downscale?
The rendezvous server (webrtc) is a factor. Note than when you send a link it points to a server.
Such as:
https://rendezvous.telestream.net/(etc)So that should make it easier to fix. If it can be controlled by your RTC server - if you can make the change there, it will fix this by forcing clients to not connect at unsupported resolutions...
-
For some reason I can't post in feature request's for Wirecast..
Looking at the Beta test of Wirecast 9 ..
could we have videos in the image Carousel ??
This would allow us to have form of playlist's inside playlists..
Then when shuffling content in the Playlist certain items can me remained locked together ..
i.e. .. Television Commercial / Main Show content