versatica / mediasoup-website Goto Github PK

I'm going to presume it's not "Single Family Unit", "Société Française des Urbanistes" or any of the other things my search has suggested.

Be kind to us and go easy on the TLAs, eh?

As shown at https://mediasoup.discourse.group/t/are-close-events-in-mediasoup-client-replicated-from-server-side/3881/5?u=piranna and https://mediasoup.discourse.group/t/are-close-events-in-mediasoup-client-replicated-from-server-side/3881/8?u=piranna, mediasoup-client Device shows a close event that doesn't exist in the actual implementation, the same that there's no close() method at all to be called. Based on the anchor of the URL, seems like it was copy&pasted from Mediasoup documentation, this needs to be removed.

Has it been deprecated? Or moved to private API?

As discussed in versatica/mediasoup#403

cargo add mediasoup

error: no such subcommand: `add`
	Did you mean `d`?

The table of contents (side menu) on the API documentation pages (e.g.: https://mediasoup.org/documentation/v3/mediasoup/api/) stopped working somewhere in the last couple of days. The problem is related to the AnchorJS library initialization.

I created a PR that seems to fix it: #30

In the explanation as below

room.getPeerByName(name)

Retrieves the Peer with the given name, or undefined if not found.

the above description seems confusing to me. I expect that I'll get undefined if the room doesn't have the peer in the argument. However getPeerByName returns newly created mediasoup Peer as long as I tested. So I think the description is misleading.

https://github.com/versatica/mediasoup-website/blob/master/documentation/v3/mediasoup/api.md

include documentation/v2/mediasoup/api/xx.md
include documentation/v3/mediasoup/api/xx.md

But no exist documentation/v3/mediasoup/api/ directory

Hi,

We implemented a workaround for orientation issues when sending video from iOS, and thought we’d post it here in case it’s useful to others.

We support Firefox, and we record video tracks using PlainRtpTransport/ffmpeg. For both of these use cases, video received from iOS clients is not properly rotated. Firefox does not support the video-orientation rtp header extension. And ffmpeg doesn’t either (or, perhaps, we have failed to figure out how to pass the orientation signaling through to ffmpeg in a usable fashion.)

So, removing the urn:3gpp:video-orientation from the sdp generated by mediasoup is a good workaround for these orientation issues. (Removing the extension from the sdp forces the client to encode the video rotated, rather than signaling rotation out of band.)

Here’s how we disable the extension, prior to calling the mediasoup-client device.load() function:

  log('loading soup device', routerRtpCapabilities);
  // remove rtp header orientation extension for mobile Safari,
  // because neither Firefox nor ffmpeg support it. so we need
  // Safari to encode the video as rotated, rather than just
  // signal rotation changes
  if (getBrowserName() === 'Safari' && browserMobile_p()) {
    routerRtpCapabilities.headerExtensions =
      routerRtpCapabilities.headerExtensions.filter(
        (ext) => ext.uri !== 'urn:3gpp:video-orientation'
      );
  }
  await this.soupDevice.load({ routerRtpCapabilities });

In our tests, Android Chrome clients work fine, which suggests that Android Chrome is not actually using this header extension. (We plan to revisit this to test more heavily on Android, however, and will update this post if we learn anything new.)

–
Kwin

https://www.chromestatus.com/features/5316065118650368

Hi, thank you for develope the mediasuop library.
First, i'm sorry for my engslish.

I have try mediasoup.types properties like in documentation.

on the documentation is like this :

import { Worker, RtpParameters } from "mediasoup/lib/types";

but i got path module not found.

i think the correct way is :

import { Worker, RtpParameters } from "mediasoup/node/lib/types";

At https://mediasoup.org/documentation/v3/mediasoup/api/#WebRtcServerOptions, listenInfos is documented as Array<[TransportListenInfo](https://mediasoup.org/documentation/v3/mediasoup/api/#TransportListenInfo)|String>, but at https://github.com/versatica/mediasoup/blob/bf7a3973f93282a3d296c8702ddad53c368076a8/node/src/Worker.ts#L692-L709, listInfo as string is ignored, allowing it to only be defined as a TransportListenInfo.