Consequences of Creating RTCMediaStreamTrack with Different PeerConnectionFactory

GEverding · October 10, 2021, 12:13am

Hi, I’ve been trying to fix various issues with mediasoup-ios-client and I’m wondering what the consequence of creating RTCMediaStreamTrack with differentI RTCPeerConnectionFactor would be?

github.com

ethand91/mediasoup-ios-client/blob/master/mediasoup-client-ios/src/Consumer.mm#L25

    
      
          @implementation Consumer : NSObject
          
          
-(instancetype)initWithNativeConsumer:(NSValue *)nativeConsumer {
              self = [super init];
              if (self) {
                  self._nativeConsumer = nativeConsumer;
                  
                  webrtc::MediaStreamTrackInterface *nativeTrack = [ConsumerWrapper getNativeTrack:self._nativeConsumer];
                  rtc::scoped_refptr<webrtc::MediaStreamTrackInterface> track(nativeTrack);
                  
                  self._nativeTrack = [RTCMediaStreamTrack mediaTrackForNativeTrack:track factory:[[RTCPeerConnectionFactory alloc] init]];
              }
              
              return self;
          }
          
          
-(NSString *)getId {
              return [ConsumerWrapper getNativeId:self._nativeConsumer];
          }
          
          
-(NSString *)getProducerId {

Topic		Replies	Views
New consumer added missing MediaStreamTrack object info mediasoup libraries	18	1245	August 12, 2020
Exposing RTCPeerConnection for a given transport mediasoup libraries	5	963	May 7, 2020
how react-native-webrtc consume stream in one RTCView render？ mediasoup libraries	2	518	April 22, 2021
Using libmediasoupclient with mediasoup v2 server side mediasoup libraries	9	1072	January 21, 2020
Set SSRC in consumer of PlainRTP transport mediasoup libraries	9	919	December 2, 2019

Consequences of Creating RTCMediaStreamTrack with Different PeerConnectionFactory

Related topics