It's possible it may just be that ffmpeg requires specific ordering for some flags, but I was asked how to have segment filenames prefixed with a FQDN within the generated manifest.
The answer
should be
FFMPEG_FLAGS='-segment_list_entry_prefix "http://foo.bar/"'
export FFMPEG_FLAGS
./HLS-Stream-Creator.sh -i example.avi -s 10
Which should lead to the segment filenames within the manifest being prefixed with the FQDN.
For some reason it didn't work, though manually adding that option to ffmpeg within the script worked fine.
Activity
2015-12-14 11:57:30
First run, without flags
Adding flags to try and repro reported behaviour
Looks like it's being passed through by HLS-Stream-Creator at least to me. Checking Manifest output
Syntax used was wrong though, so retrying with valid flags
Looks good to me
2015-12-14 11:57:42
2015-12-14 12:03:57
So, that seems to have worked too.
Looking at where the flags are inserted though, I wonder if we need to take argument order into account
What happens if FFMPEG_ADDITIONAL is non-empty?
2015-12-14 12:12:28
Without export
Seems to work.
Multiple bitrates?
Non-live ABR?
Seems to work without issue.
It should work even when video and audio are split out into fifos as the arguments related to those come at the beginning of the arg list.
For the time being, I'm going to close this as cannot reproduce.
2015-12-14 12:12:43
2015-12-14 12:12:53
2015-12-14 12:12:53
2015-12-14 12:12:58