ibc

9 ms·

1.
by ibc 6y ago
Yeah please, let the author know your preferred programming language so he'll rewrite the whole software.
2.
by ibc 6y ago
Yep, I know. However the effort required to make and maintain DEB/RPM packages for different architectures (mediasoup has a C++ component) is huge.
3.
by ibc 6y ago
DataChannels are transmitted over the same UDP/ICE "connection" that is used to transmit audio and video packets. So if you plan to send real-time data (for example: real-time subtitles, metadata related to the current video
4.
by ibc 6y ago
mediasoup is not an application, is a Node.js library. It's yet nother NPM dependency in your Node.js application. No reason to have a DEB package.
5.
by ibc 6y ago
mediasoup (server side, so the Node + C++ component you mean) does not implement "RTCPeerConnection". That's just needed for browsers. In mediasoup we don't use SDP but specific RTP parameters as defined here: https:&#x
6.
by ibc 6y ago
Yes, you can use WebRTC DataChannels for sending custom text/binary data on top of a ICE+DTLS connection. BTW mediasoup supports DataChannels. Any question or comment about mediasoup?
7.
by ibc 6y ago
I thought that this news was about mediasoup, not about generic WebRTC questions.
8.
by ibc 6y ago
PornHub uses mediasoup for live cams.
9.
by ibc 6y ago
It's a Node library, yes.
10.
by ibc 6y ago
mediasoup (in server side) is a Node.js library or a NPM dependency that you integrate into your Node.js app. Of course it comes with tons of C++ lines but, from the point of view of the user, it's just yet another NPM dependency into
11.
by ibc 6y ago
Yep, two active developers but being just a set of libraries it's good enough. We also get nice contributions (C++ fixes and optimizations) via PR in GitHub. And we use mediasoup in different commercial products.
12.
by ibc 6y ago
Jitsi is a full application (web app, backend servers) with a specific use case: meetings (similar to Zoom or Google Meet). mediasouop is not an application but a set of server and client low level libraries to build whichever kind of audio
13.
by ibc 6y ago
10 users? the cheapest one.
14.
by ibc 6y ago
In WebRTC spec (although not super mandatory but the current way to go), the client no longer signals its sending SSRCs into the SDP but a MID and optional RID values (if simulcast is in use), and those MID and RID are not supposed to be un
15.
by ibc 6y ago
This is RTP not WebSocket or HTTP. Media servers need a separate port for each RTP communication. A hack could be done to make all WebRTC endpoints to use a single port in mediasoup side. However mediasoup also support plain RTP endpoints a
16.
by ibc 6y ago
Why is that so important? As I said, choosing a specific port is not enough. This is not TLS. An aggressive firewall may drop those TCP connections because there is no TLS data on them.
17.
by ibc 6y ago
Majority of RTP media server listen into a separate port for each connection. That's how RTP typically works. This is not TCP connections.
18.
by ibc 6y ago
> is like sending information at several resolutions and each peer selecting the best one. Well, no. This is not about sending all video layers to all receivers and let them choose which one to render. Not al all. The purpose of video si
19.
by ibc 6y ago
Not at all.
20.
by ibc 6y ago
You cannot select a specific listening port for a specific transport, because each WebRTC transport requires, at least, a different listening port in the server: https://mediasoup.org/documentation/v3/mediasoup&#x2
21.
by ibc 6y ago
I thought this news was about mediasoup, not about WebRTC in general. Said that I agree that your scenario is valid without any media server.
22.
by ibc 6y ago
We do support TCP ICE candidates for long time: https://mediasoup.org/documentation/v3/mediasoup/api/#WebRtc... > TCP candidate so a TURN server isn't needed at all? This is not true. A router ma
23.
by ibc 6y ago
The demo is just a demo. mediasoup is a low level library (no UX into mediasoup). The online demo backend does not have any TURN server. It's obviously recommended to deploy a TURN server.
24.
by ibc 6y ago
Just to easily explain that mediasoup is not a replacement for Jitsi or Zoom, but a low level set of libraries for building build different kind of real-time applications, including multi-party videoconference apps (such as Jitsi or Zoom) a
25.
by ibc 6y ago
mediasoup is a SFU that must be deployed in a reachable server, so STUN is not needed at all. You may need a TURN server if a client has a restrictive firewall that blocks UDP. mediasoup is not a TURN server but you can deploy a TURN server
26.
by ibc 6y ago
Hi, mediasoup co-author here. TL'DR': Pornhub uses mediasoup. I've read many comments here asking about "how mediasoup is different than XXX" or about "mobile apps". I think the Overview in the website sho
27.
by ibc 6y ago
mediasoup co-author here. So you don't know what mediasoup does but you assure that "no need to use a SFU". Too much free time to comment maybe? e2ee makes sense in one-to-one and N-to-N scenarios. It's just more complex
28.
by ibc 6y ago
mediasoup co-author here. Comparing Jitsi with mediasoup is like comparing Netflix (backend + apps) with Express.js + libcurl. Jitsi developers may replace their RTC core internals (including the SFU) with mediasoup + mediasoup-client and y
29.
by ibc 6y ago
And somehow this discussion become a general topic about WebRTC scenarios. They do exist, yes, but mediasoup is a SFU scenario. No STUN is required at all. TURN may be needed if the client network/router blocks UDP.
30.
by ibc 6y ago
mediasoup co-author here. > You don't even need servers if you go full p2p If you have N participants into the same "room", and do not have a central SFU that relays streams to others, then you have a full mesh network wit

More ›