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
Problem connecting consumer mediasoup libraries	0	179	June 10, 2022
Mediasoup publishing probator packets on rtp port of plain transport mediasoup libraries	8	755	July 28, 2022
!broadcaster.data.rtpCapabilities is for producer or consumer mediasoup-demo	1	418	February 3, 2021
Producer's WebRTC would not connect mediasoup libraries	8	1501	May 12, 2020
pipeToRouter warning mediasoup libraries	17	2462	May 25, 2021

Consequences of Creating RTCMediaStreamTrack with Different PeerConnectionFactory

Related topics