log file: "GET /hls-live/livepkgrRadio/_definst_/liveevent/livestream1_audio_only.m3 u8 HTTP/1.1" 404 353 "-" "AppleCoreMedia/126.96.36.199A405 (iPhone; U; CPU OS 5_0_1 like Mac OS X; he_il)"
Few queries from my side, before diving more into your issue:
1) My last version was FMS 4.5.1
2) I am using windows server 2008 enterprise r2
3) Yes HLS live streaming worked good in version 4.5.1
4) HDS live steaming work good also in version 4.5.2
5) M3 u8 it's copy problem
You may try these options if everything is configured correctly then you should be able to fetch m3u8 file.
Before I wrote the question on the forum I checked everything and all is well specified.
No change was made in these files just like I mentioned version has been updated.
This problem is created in the development environment and production environment.
I would appreciate your care.
Few more queries:
Finally I solved the problem!
IN the help documentation "Stream live media (HTTP)"
Edit the Event.xml file to look like the following:
<Event> <EventID>liveevent</EventID> <Recording> <FragmentDuration>4000</FragmentDuration> <SegmentDuration>16000</SegmentDuration> <DiskManagementDuration>3</DiskManagementDuration> </Recording> </Event>
I copied the file Manifest.xml to my livepkgrbreslev3 folder from The
default library livepkgra and strangely now everything works.
I am also having this issue. Version jump from 4.5.0 r 297
I have followed all the steps as suggested earlier, removed the manifest file, etc. ver 4.5.0 HLS works 4.5.2. on iPad and iPhone "The operation could not be completed" similar to an issue if the .m3u8 is improperly configured. I know they aren't improperly configured as they function flawlessly on version 4.5.0
Something is missing or has been changed with this new version and there is no documentation to support it........
I am also having the exact same problem. Without the Manifest.xml in the event folder, requesting the m3u8 for the stream results in a 404 message.
Using CentOS 5 and FMS 4.5.2.
Everything works without the Manifest.xml in FMS 4.5.1 with the same stream configuration.
This is a known issue with FMS 4.5.2. If you request m3u8 from the server and no Manifest.xml is available for that particular event, you may land into errors.
Please make sure you create a copy of manifest.xml for the event you are using and place it inside application/livepkgr/event/_definst_/<your-event-name>/ directory.
We are tracking this issue and it will be fixed in the new updated version of FMS which will be released soon.
So the Manifest.xml file _DOES_ need to be in place.
I'm assuming that file should be edited so that the bitrates match what you've entered into the set-level manifest files, as well as what you're streaming out from the FMLE, correct?
It probably does need to be set to the same levels because it doesn't work for us with the original manifest. I will report our findings once we test with the edited manifest
For the record I am also using CentOS 6.2
It is a good practice to keep the bitrates in manifest.xml same as the ones with which you are publishing from FMLE. However, this itself will not cause any problems if the bitrates do not match.