What is the structure of a Quortex I/O publishing point?
Let's see how publishing points can help you customize endpoint URLs used by players!
A publishing point on Quortex I/O is the HTTPS endpoint a player will use to access a stream.
New publishing points are automatically added when you add inputs, processing configurations, or targets to a pool.
The general structure of a publishing point is as follows:
https :// <pool_id> .live.quortex.io / <input> / <processing> / <target> / index.<extension>
Let's break it down:
<pool_id> is an unique identifier for your pool, it cannot be changed.
<input> is the identifier of your choice for each input. Its default value is generated using the input name.
<processing> is the identifier of your choice for each processing configuration. Its default value is generated using the processing configuration name.
<target> is the identifier of your choice for each target. Its default value is generated using the target name.
<extension> depends on the target type, it cannot be changed.
Example publishing point URLs:
https :// j6r3vxpj .live.quortex.io / wildlife_channel / hd / dash / index.mpd
https :// j6r3vxpj .live.quortex.io / wildlife_channel / hd / hls / index.m3u8
The neat thing about publishing points is that you can customize them the way you want, without changing the names of components themselves. Think of this as "public identifiers vs internal names"!
You can change the hd identifier of the "HD" processing configuration to premium:
The identifier will change in the two publishing points simultaneously.
You can also disable a specific combination of input, processing and target:
That endpoint will be unavailable for players.
You can also disable a whole component:
If you do that, be sure to create a rule that will select the appropriate component, because we won't find it in the URL anymore!
For example, you could create an Always rule selecting the "HD" processing configuration:
As a result, the following endpoints will use the "HD" processing configuration, even if it's not in the URL:
https :// j6r3vxpj .live.quortex.io / wildlife_channel / dash / index.mpd
https :// j6r3vxpj .live.quortex.io / wildlife_channel / hls / index.m3u8
That's it, have fun with publishing points!
General structure
A publishing point on Quortex I/O is the HTTPS endpoint a player will use to access a stream.
New publishing points are automatically added when you add inputs, processing configurations, or targets to a pool.
The general structure of a publishing point is as follows:
https :// <pool_id> .live.quortex.io / <input> / <processing> / <target> / index.<extension>
Let's break it down:
<pool_id> is an unique identifier for your pool, it cannot be changed.
<input> is the identifier of your choice for each input. Its default value is generated using the input name.
<processing> is the identifier of your choice for each processing configuration. Its default value is generated using the processing configuration name.
<target> is the identifier of your choice for each target. Its default value is generated using the target name.
<extension> depends on the target type, it cannot be changed.
Example publishing point URLs:
https :// j6r3vxpj .live.quortex.io / wildlife_channel / hd / dash / index.mpd
https :// j6r3vxpj .live.quortex.io / wildlife_channel / hd / hls / index.m3u8
Going further
The neat thing about publishing points is that you can customize them the way you want, without changing the names of components themselves. Think of this as "public identifiers vs internal names"!
Customizing identifiers
You can change the hd identifier of the "HD" processing configuration to premium:
The identifier will change in the two publishing points simultaneously.
Disabling a publishing point
You can also disable a specific combination of input, processing and target:
That endpoint will be unavailable for players.
Disable a whole component
You can also disable a whole component:
If you do that, be sure to create a rule that will select the appropriate component, because we won't find it in the URL anymore!
For example, you could create an Always rule selecting the "HD" processing configuration:
As a result, the following endpoints will use the "HD" processing configuration, even if it's not in the URL:
https :// j6r3vxpj .live.quortex.io / wildlife_channel / dash / index.mpd
https :// j6r3vxpj .live.quortex.io / wildlife_channel / hls / index.m3u8
That's it, have fun with publishing points!
Updated on: 01/03/2024
Thank you!