SRT Input (Listen) mode to bring in as source
SRT (Secure Reliable Transport) Input (Listen) mode to bring in as source. SRT supports both output and input. Wirecast SRT Output is already in development. We'd like to gauge development priority for input/listen mode. Please include a specific use case if possible.
-
Would be very useful for bringing in remote guests.
-
For our use cases, SRT input would be priority over output, however both would be very useful!
Mobile production input, iOS SRT device such as the app Larix
-
It would be good if the received streams SRT supported:
- 8 audio channels (AAC supports up to 8 channels) - vMix audio [MABCDEFG] : https://www.vmix.com/help23/index.htm?SRT.html
- Multiple audio track - OBS: https://obsproject.com/wiki/Streaming-With-SRT-Protocol#option-2-stream-srt-with-the-custom-ffmpeg-record-output
- Stream ID
-
The most simple argument for SRT output is getting away from RTMP, targeting CDNs or streaming providers. Wowza for instance, allows SRT ingest and everyone should prioritize SRT over RTMP getting the mix into the cloud securely and reliable.
And I have to add. Ingesting SRT adds burden to the wirecast network (open ports). I believe the majority is streaming out of wirecast into some services in the cloud. I assume the minority is ingesting SRT into their production. Maybe Telestream has to rethink priorities.
-
Jens Jarke We're doing output first. That's happening in the near future. I wanted to start the ball rolling on ingest though since we have been getting requests for that.
-
CraigS Output only is good but not enough. For example you cannot connect 2 wirecast in different location (my case) if you do not have input. I think Input is a great priority as well. You know I don't like comparison but competition is becoming aggressive and already have this feature since months...
-
Ermanno Bonifazi I understand the need for input which is why we have this vote. I think the developers need to be pushed by user interest to make sure it's prioritized. If you have strong arguments that you think the developers may be overlooking please do fill out the form and give them an earful. Users like you can make the most persuasive case.
-
CraigS I totally agree with you but this open up another discussion: are really developer seeing our priorities or more their own agenda only? I have seen recently changes that were not necessarily needed why others that are crucial (srt, quality for audio/video in RV, and many other) where left behind... and trust me competition is coming hard from all over. Even some online tools now include great quality feature for audio/video/guest/ndi/srt. While i was more confident in ability to listen users input, more recently I was a little discouraged on the outcome from the releases.
-
Ermanno Bonifazi They need to better understand the user's needs. They sometimes find users doing unexpected things or wanting to do things more frequently than they expect. Sometimes when looking at the competition it's not only "does x have this feature" but is the feature really being used that much. Basically, some features turn out to be niche and shouldn't be prioritized over features a broad user base needs more immediately. First-hand use cases give them a much better idea of how widely a feature may be used. Also which kind of user needs a feature can have an influence. Is a feature a "novelty" or is it in demand for the corporate user for example?
-
-
I would say the most famous ingest option is with larix broadcaster App from the field. Or some enodr appliances.
-
Jens Jarke Thanks. We should test with Larix then as we develop ingest.
-
CraigS SRT Alliance is pretty big, lots of encoders can send/receive... I target hardware on that list as a priority. The protocol is brilliant. Epiphan Pearl products are amazing, but OBS/Larix is the best way to do it for free.
-
-
Do hope we get SRT ingest as the soonest. We also have use cases for both actually as we're using WC for our events with 2 locations. Currently we have to settle to send to Youtube and capture that from the hub system. If we could setup point-to-point using SRT it would be huge.
-
Swami Trika Output will be coming first most likely.
-
CraigS it’s a deal breaker for us. Have to go to vMix. My team loves Wirecast too.
-
Chris Barnett As you can see there's a fair number of requests and Telestream is part of the SRT Alliance. I can't say more than that at the moment though.
-
Chris Barnett said:
Have to go to vMixBut the trouble is that vMix is not for for MacOs platforms. That why I went for Wirecast.
-
-
The function of SRT input is very important, and the technical means are being updated day by day. Please do not give up your users for the commercial interests of some partners. What's more, vmix, a competitor of wirecast, has already supported this function.
-
With more and more field cameras turning to SRT and Zixi QoS as IP-based export platforms with bonded cellular and broadband this only makes sense to offer SRT in addition to the Telestream Rendezvous web-based platform for remote ingest into Wirecast.
-
Absolutely needed! For external feeds in situations like election's day, live sport like running, marathon, cycling race...
Is it possible a return channel to remote caller?
-
Emmanuel De Donato said:
Is it possible a return channel to remote caller?How would you want that to work?
Rendezvous (which is WebRTC) sends back to guests of course.-
CraigS I don't know how systems like LiveU LU500/600 or TVU have a return channel to the remote unit... a method like that!
Some new JVC camcorders have also return channel feature...
-
Emmanuel De Donato We'd need to know how that is done. That may be a separate feature request.
-
CraigS Here the scheme to connect JVC cameras to video return & IFB!
https://m.facebook.com/story.php?story_fbid=1186523478414612&id=595572137509752
TVU Networks use custom technology like Rendezvous called "Partyline".
https://www.tvunetworks.com/products/tvu-partyline/
https://www.tvunetworks.com/return-video-feedback-tvu-anywhere-live-broadcast/
-
Emmanuel De Donato Good details in that. I think you should make it its own feature request as this probably deserves separate attention. Those real-world workflow examples help. Note that Wirecast Rendezvous (based on WebRTC) sends back to the "caller" which can be host, Wirecast output, mixed audio sources, and with 14.1, backchannel text chat.
-