API for LLHLS Dump #1073
Replies: 2 comments 3 replies
-
I don't know why but it isn't working for me. When I configure the LLHLS dumping it works right. The config is as follows:
I have tried to keep these fields (although it dumps automatically my streamings) and also removing them but when I try to dump it with the API with the following body:
It doesn't create anything. I have already checked that OME has permissions for writing in that directory because the automatic dumping works and saves the files there. The output of the API request is:
which btw is strange because it should be as follows, according to the documentation:
And the response field doesn't appear although I am starting the dumping of the stream multiple times with different ids. I am sure I'm doing something wrong but I don't know what and the OME's logs don't help me. I would be very grateful if you could help me with this. |
Beta Was this translation helpful? Give feedback.
-
Hi again! I'm using the version 0.15.10 of OME and it looks like the tag of the infoFile is not working as expected. It's always "Running". This happens when I stop the dumping making stopHlsDump POST request and also when the stream finishes. I have checked the releases and the only thing related I could find was the 0.15.11 release, but I understand those changes were to recordings not to hls dumping. I hope you can help me. Thank you! |
Beta Was this translation helpful? Give feedback.
-
The LLHLS Dump feature (#902) can be controlled by API now.
Start Dump API
POST /v1/vhosts/<vhost_name>/apps/<app_name>/streams/<stream_name>:startHlsDump
outputStreamName (required)
The name of the output stream created with OutputProfile.
id (required)
ID for this API request.
outputPath (required)
Directory path to output. The directory must be writable by the OME process. OME will create the directory if it doesn't exist.
playlist (optional)
Dump the master playlist set in outputPath. It must be entered in Json array format, and multiple playlists can be specified.
infoFile (optional)
This is the name of the DB file in which the information of the dumped files is updated. If this value is not provided, no file is created. An error occurs if a file with the same name exists. (More details below)
userData (optional)
If infoFile is specified, this data is written to infoFile. Does not work if infoFile is not specified.
Stop Dump API
POST /v1/vhosts/<vhost_name>/apps/<app_name>/streams/<stream_name>:stopHlsDump
outputStreamName (required)
The name of the output stream created with OutputProfile.
id (optional)
This is the id passed when calling the startHlsDump API. If id is not passed, all dump in progress at outputStreamName is aborted.
InfoFile
The info file is continuously updated after the dump file is written. It is in XML format and is as follows.
<Items><Item>
will continue to be added.Beta Was this translation helpful? Give feedback.
All reactions