Sending SDP data to a Powercore

[fgoupil-cbc]

Hi,

Has anyone been able to push an SDP file to a Powercore (or any other Ember+ device I guess) from Companion so that it subscribes to a stream? The Powercore expects carriage returns for each line of the SDP file but Companion only allows single line text and I tried adding \n to encode each line but Companion keeps sending that as clear text from what I can see using Wireshark. I at least know that Companion is able to empty out the receiver by sending an empty line.

Any ideas?

Thanks,

François

[phillipivan]

Hi François,

What module version are using?

I presume the SDP field is a string parameter, is that correct?

If you download module version 2.4.4 you could create the multiline SDP entry as a variable and try using that in the Set Value String action.

[fgoupil-cbc]

Hi Phillip,

It is indeed a string parameter - I'm currently using version 2.2.0 so I'll update the module and give the variable trick a try before reporting back.

Thanks!

François

[phillipivan]

Great. The built version of the module is attached to the release.

[phillipivan]

Have you been able to test this yet?

[cbjornram]

Hi Phillip,

I also gave this a go (Companion version 3.5.0-7590 and generic ember module version 2.5.0) and can't get it working either. I also tried the idea with a multi line variable using \n for each new line in the SDP, as well as one at the end of the SDP (as required of the Power Core), but with the same result. Just like François, I can clear an SDP by sending an empty string.

Original SDP:

v=0
o=- 09420142300001 0 IN IP4 192.168.99.240
s=core01:rav01
t=0 0
a=clock-domain:PTPv2 0
a=ts-refclk:ptp=IEEE1588-2008:00-0B-72-FF-FE-09-88-F6:0
a=mediaclk:direct=0
a=group:DUP ra0 ra1
m=audio 5004 RTP/AVP 98
c=IN IP4 239.99.240.1/16
a=source-filter: incl IN IP4 239.99.240.1 192.168.99.240
a=rtpmap:98 L24/48000/2
a=mid:ra0
a=framecount:48
a=recvonly
a=ptime:1
a=sync-time:0
a=mediaclk:direct=0
m=audio 5004 RTP/AVP 98
c=IN IP4 239.98.240.1/16
a=source-filter: incl IN IP4 239.98.240.1 192.168.98.240
a=rtpmap:98 L24/48000/2
a=mid:ra1
a=framecount:48
a=recvonly
a=ptime:1
a=sync-time:0
a=mediaclk:direct=0

Manually edited for custom variable:

v=0\no=- 09420142300001 0 IN IP4 192.168.99.240\ns=core01:rav01\nt=0 0\na=clock-domain:PTPv2 0\na=ts-refclk:ptp=IEEE1588-2008:00-0B-72-FF-FE-09-88-F6:0\na=mediaclk:direct=0\na=group:DUP ra0 ra1\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.99.240.1/16\na=source-filter: incl IN IP4 239.99.240.1 192.168.99.240\na=rtpmap:98 L24/48000/2\na=mid:ra0\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.98.240.1/16\na=source-filter: incl IN IP4 239.98.240.1 192.168.98.240\na=rtpmap:98 L24/48000/2\na=mid:ra1\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\n

I also tried creating a trigger to automatically fill the variable from the SDP field of the device's Ember+ Provider, but that only resulted in a single line variable with neither line breaks nor \n. If I paste the original SDP into the Power Core using Ember+ Viewer, the Power Core accepts it.

Best regards,

Christoffer

[phillipivan]

G'Day Christoffer,

Thanks for coming back with more info. I don't think any of the devices I have access to handle multi-line strings so it's not something I have been able to test directly.

The module itself doesn't do anything special with the strings supplied to it, other than parsing variables, so I wonder if this is a characteristic of the ember-plus library being used.

Can I send you a module with some extra logging to test with?

[cbjornram]

Absolutely, if I can help then I would like to.

As additional information, I ran a Wireshark after sending my previous message that I think shows where the issue might be. When patching an SDP with Ember+ Viewer, there are carrage returns (hex 0d 0a) as linebreaks throughout the SDP.

However, the SDP patching message from Companion/Generic Ember Plus module contains the \n characters. so it seems as if the \n characters are not parsed to real linebreaks before being sent.

[phillipivan]

@cbjornram here is a build with some logging (at console level) inserted after parsing of string variables, it should confirm what you have observed in wireshark:

case EmberModel.ParameterType.String:
	value = await self.parseVariablesInString(action.options['value']?.toString() ?? '')
	console.log(`Set Value String:\n${value}`)
	break

companion-module-generic-emberplus_v262.zip

[phillipivan]

Attachment removed as it didn't help.

Give this a try a well if you can
@cbjornram is there an powercore ember+ emulator or similar that I could use to test with?

[cbjornram]

I configured a button with "[emberplus]: Set Value String" as the only action on it as the following image. As can be seen in the tiny button preview, the SDP gets rendered correctly with linebreaks in the Companion UI.

The $(custom:sdptest) variable was set to:

v=0\no=- 09420142300001 0 IN IP4 192.168.99.240\ns=core01:rav01\nt=0 0\na=clock-domain:PTPv2 0\na=ts-refclk:ptp=IEEE1588-2008:00-0B-72-FF-FE-09-88-F6:0\na=mediaclk:direct=0\na=group:DUP ra0 ra1\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.99.240.1/16\na=source-filter: incl IN IP4 239.99.240.1 192.168.99.240\na=rtpmap:98 L24/48000/2\na=mid:ra0\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.98.240.1/16\na=source-filter: incl IN IP4 239.98.240.1 192.168.98.240\na=rtpmap:98 L24/48000/2\na=mid:ra1\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\n

Pressing it on version 262 gave the following output:

system: Starting log. Only lines generated since opening the page are shown here
debug: Got node on 1.6.3.2.1.6
Set Value String:
v=0\no=- 09420142300001 0 IN IP4 192.168.99.240\ns=core01:rav01\nt=0 0\na=clock-domain:PTPv2 0\na=ts-refclk:ptp=IEEE1588-2008:00-0B-72-FF-FE-09-88-F6:0\na=mediaclk:direct=0\na=group:DUP ra0 ra1\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.99.240.1/16\na=source-filter: incl IN IP4 239.99.240.1 192.168.99.240\na=rtpmap:98 L24/48000/2\na=mid:ra0\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.98.240.1/16\na=source-filter: incl IN IP4 239.98.240.1 192.168.98.240\na=rtpmap:98 L24/48000/2\na=mid:ra1\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\n

Pressing it on version 263 gave the same output:

system: Starting log. Only lines generated since opening the page are shown here
debug: Got node on 1.6.3.2.1.6
Set Value String:
v=0\no=- 09420142300001 0 IN IP4 192.168.99.240\ns=core01:rav01\nt=0 0\na=clock-domain:PTPv2 0\na=ts-refclk:ptp=IEEE1588-2008:00-0B-72-FF-FE-09-88-F6:0\na=mediaclk:direct=0\na=group:DUP ra0 ra1\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.99.240.1/16\na=source-filter: incl IN IP4 239.99.240.1 192.168.99.240\na=rtpmap:98 L24/48000/2\na=mid:ra0\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\nm=audio 5004 RTP/AVP 98\nc=IN IP4 239.98.240.1/16\na=source-filter: incl IN IP4 239.98.240.1 192.168.98.240\na=rtpmap:98 L24/48000/2\na=mid:ra1\na=framecount:48\na=recvonly\na=ptime:1\na=sync-time:0\na=mediaclk:direct=0\n

I did verify that the correct version was picked up by Companion before creating the logs. I also tested that that same button still can clear SDPs by sending a blank string, which it could with the following log output:

system: Starting log. Only lines generated since opening the page are shown here
debug: Got node on 1.6.3.2.1.6
Set Value String:

Unfortenately, there are no Power Core emulators that I'm aware of. If it's of any help, the Ember+ Viewer does show and send linebreaks of strings properly, so if you have any provider available (for example the provider of Companion itself), you can write to button labels and see the result. Here I have used shift+return to set a linebreak of a Companion button while inside the "Change..." dialogue:

[phillipivan]

Good idea to test with Companion's own ember plus provider. I'll have another look next week.

[phillipivan]

I have observed the same issue with a syslog client module I wrote a few days ago, so I suspect there is a common root cause.

[phillipivan]

HI @cbjornram @fgoupil-cbc please test this build. It seems to be working for me - controlling companion button text from companion. Using ember+ viewer to confirm the field value.

The fix will only work for \r \n and \t. It is something of a hack, and I have reservations about pushing it to a proper release as the problem lies elsewhere, but for the time being I think it will get you going.

companion-module-generic-emberplus_v263.zip

[cbjornram]

Hi Phillip, thank for the status updates and the new build. I will give this a try as soon as I can (which might be a few days/a week away). I'll keep you posted.