This is a request for more control over segment name formatting (i.e. the "location" property of hlssink/hlssink2)

Currently, segment names are stored as absolute paths if a different playlist-root is specified. This makes no sense to clients that have only access to the folder containing the playlist and segments, but not the full filesystem. This is a regression introduced coming from the fix of 687133 that prepends the location-root if it is available, but also uses the same path as entry in the m3u8. 

Common use case would be a HLS client connecting through a webserver, which would read the segment path and request it through the webserver. The suggestion is to have either an option to force just the segment name as configured by the "location" property, instead of prepending it with the playlist-root, or an additional configurable pattern property that can be set based on pipeline properties (see next paragraph).

Another nice-to-have would be to allow segment filenames to be tored in mockup folder structures (.e.g depending on the encoding caps) of each .ts. The mockup name can be resolved by the webserver internally.  This would add additional security to the service, and also allow for loadbalancing in dynamic streaming situations.

Kind regards,
Ignace