By default Phenix uses the semicolon (;) character to separate the capabilities and other Phenix specific terms in URLs used for RTMP ingest from the StreamKey.
However, many third-party encoders (vMix, Tricaster, etc.) break strings at a semicolon, so capabilities and other arguments do not support the use of a ; in an RTMP ingest URL and everything following the semicolon in the URL are trimmed is removed from the information sent to the Phenix platform.
To support these encoders, Phenix also supports the use of a pipe (|) character instead of a semicolon as a separator between arguments in ingest stringsURLs.
| Warning |
|---|
The two delimiters MUST NOT be mixed in any given URL. That is, either the pipe OR the semicolon must be used. Mixing the delimiters will result in unexpected behavior. |
For more information, please see the API documentation.
Examples of correct ingest URLs
All semicolons
rtmp://ingest.phenixrts.com:80/ingest/96characterStreamKey;capabilities=hd,multi-bitrate,mpegts-unicast-ingest;tags=my-awesome-stream-id,MyAppId
All pipes
rtmp://ingest.phenixrts.com:80/ingest/96characterStreamKey|capabilities=hd,multi-bitrate,mpegts-unicast-ingest|tags=my-awesome-stream-id,MyAppId
Examples of incorrect ingest URLs
Mixed delimiters
rtmp://ingest.phenixrts.com:80/ingest/96characterStreamKey|capabilities=hd,multi-bitrate,mpegts-unicast-ingest;tags=my-awesome-stream-id,MyAppId
...