- Feb 05, 2022
-
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
all the same empty {}, it is only one Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
erase the old "recordings.json" and start over. Keep the timestamp of the recorded programs instead of the pid, just like the epg itself does. The pid is something ephemeral of little use after some time, whereas the timestamp can be useful ever after. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
to the saved filename, it makes for nicer archiving, no sense to keep the original verbatim full_title Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
working well, we want it to get to the end whatever the surprise Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
always clean Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
running at once was a good idea but the lock file can get stale, add a safe measure and corresponding warnings Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
confusing 'event' variables most of which were really timestamps but not all Signed-off-by: Javier Marcet <javier@marcet.info>
-
- Feb 04, 2022
-
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
storage when postprocessing recordings. When there are many recordings taking place at once, easy when using the IPTV_BW feature, at the end, if there are many processes copying what can be huge files at full speed all at once, the storage can get a little unresponsive. Now they will make a queue, and only one postprocessing mkvmerge/ffmpeg will run at once. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
greater duration than in the EPG, extending easily way beyond the next program. This might be nice when live watching or even for recording manually a program but it is not the intended behavior for timers, so fix that. The attempt to extend a little bit the recording time now uses the reported recorded duration by Movistar as an upper limit. Recording logs now also show the exact expected duration. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
"Network Staturated" and related messages Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
the same program at the same time, which would collide writing to disk Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
through the HTTP API, now with the endpoint: /record/channel_id/flussonic_url?cloud=1&mp4=1&time=100&vo=1 All the arguments are optional and the flussonic_url accepts the same url styles as everywhere else, which means not only a timestamp works but also YYYYMMDDHHMM/YYYYMMDDHHMMSS do. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
backend, it made no sense to keep it in the main one since vod is not launched as external process anymore but for handling recordings. Still missing is enabling an external api to do such recordings on request, ATM only timers work. Signed-off-by: Javier Marcet <javier@marcet.info>
-
- Feb 03, 2022
-
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
and update all the documentation. It now works really well. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
as all the KODIPROPS. Kodi's iptv.simple addon has now been updated and all that addiontal info is no longer needed. Thanks phunkyfish for all your work :) Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
compress guide.xml for faster loads, keep old style for compatibility. Rework tvg, no more output to stdout, now it's either exporting normal channel list and/or normal guide, OR cloud recordings channel list and/or cloud recordings guide. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
channels urls to /mpegts, which seems more standard Flussonic style. Keep the previous /live working to not break any setup. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
to --update and show tvg instructions in Spanish, like the rest of its strings are Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
turned out not to be enough. SIGCHLD was being received only for a few seconds after the child was launched, so it was neccesary to add a task for each children to cleanup after them. With this, bandwidth consumption of vod processes is always stopped the instant either ffmpeg or the vod process die. Only SIGKILL is not trapped, which cannot. This also applies to Windows systems. The signal handling is completely substituted by the manual cleanup, and far from taxing the system too much, it performs amazingly well. All this still works with movistar_u7d working in multiple processes. And last, the cleanup queues a new /timers_check after a child ends, unless the network is saturated, so the queue of recordings can always be using the entire bandwidth available, non stop :D If a normal client tries to open a stream while this happens, a recording is nicely killed and requeued when there is available bw again. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
processes on unix. No more vod zombies and as an added bonus, in case either ffmpeg or vod die, however badly it happens, the event is properly signaled to the epg backend so the recording is removed from the queue and, a new /timers_check is queued. Thus, when either ffmpeg or vod itself die, it is all cleaned up in a proper way and the recording requeud immediately. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
adding emergency ending options Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
resultant EPG does not have any program overlappings.
-
Javier Marcet authored
maintenance of an EPG cache without errors. It should put an end to wrong empty spaces on programming, beyond those coming as such from Movistar. TiviMate in particular, which does not accept any collapse between programs should be much better now.
-
Javier Marcet authored
launched as a separate process, which from a long time ago only happens for recordings. In this case the client ip does not make too much sense and the rest is unimportant for latency, as it is when watching programs from the catchup. Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
MovistarTVCloud.m3u and Recordings.m3u. Still accept the old names cloud.m3u/nube.m3u & recordings.m3u/grabaciones.m3u, plus also Channels.m3u/Canales.m3u, Cloud.m3u/Nube.m3u & Recordings.m3u/Grabaciones.m3u Signed-off-by: Javier Marcet <javier@marcet.info>
-
Javier Marcet authored
adding a lock so no problems arise when several recordings end at once. Plus make sure metadata is saved after recordings complete and that vod does not end as a zombie. Signed-off-by: Javier Marcet <javier@marcet.info>
-