Cian Posted February 15, 2021 Share Posted February 15, 2021 Hi, the the "Start/Stop by EPG Running Status" option used tp work perfectly for me, but bince the DMS 3.0.1, it does not seem to work anymore. I saw in the ReadMe for 3.0.2, there was a reference to changing it for imported EPG's to "Start/End Time Update by EPG", but I still end up with recordings that are 12 minutes too long (I use a 2min/10min pre/post buffer). There is a link referenced for the change, but for some reason I don't have permission to view the page. I'm recording mostly from BBC on Satellite. Can someone update me as to what is happening? Thanks, C. Quote Link to comment
Griga Posted February 15, 2021 Share Posted February 15, 2021 Are you using imported EPG? Is the "EPG Event ID usage on timer handling" tweak enabled? Are you using "Start/End Time Update from EPG" or "Start / Stop by EPG running status" as recording option? Quote Link to comment
Cian Posted February 15, 2021 Author Share Posted February 15, 2021 Hi Griga, 1. Most of the EPG info is coming direct from the internal EPG grabber. I am using an imported EPG just for Channe 4, since they do not broadcast the EPG for the HD version of C4. 2. EPG tweak is set to 2. 3. I have tried using both, but it makes no difference. Running Status worked perfectly for me in the past, so that would be my preferred option. For testing purposes, I will stop importing the EPG and see how I get on with a test of each type this evening. C. Quote Link to comment
Griga Posted February 15, 2021 Share Posted February 15, 2021 vor 8 Stunden schrieb Cian: but I still end up with recordings that are 12 minutes too long It would be helpful to see a log for such a recording (DMS Options -> Recordings -> Write log file). Quote Link to comment
Griga Posted February 17, 2021 Share Posted February 17, 2021 Basically it works. I've just tried a short recording from Astra 28.2° East with "EPG Event ID usage on timer handling" enabled. Here is the log: Spoiler CBeebies HD (AC3,eng) 17.02.2021 D:\Dateien von Griga\Videos\DVBViewer Pro\New Tik Tak_CBeebies HD (AC3,eng)_2021-02-17-12-25-02.ts Naming Scheme: %event_%station_%year-%date-%time Device: Professional DVB Digital TV DVB-S2 (5) EventID: 19371 Timer Name: New: Tik Tak - Episode 18. Explore a dissection puzzle of a wheel Timer Start: 17.02.2021 12:25:00 Timer Duration: 00:20:00 (20 min. incl. 5 min. lead time, 10 min. follow-up time) Timer Options: Teletext=0, DVB Subtitles=1, All Audio Tracks=1, Adjust PAT/PMT=1, EIT EPG Data=0, Transponder Dump=0 Timer Source: Web Monitoring Mode: Start/stop by running status 12:25:02 / 00:00:00 (~ 0,00 MB) Start EPG Monitoring 12:25:02 / 00:00:00 (~ 0,00 MB) Pablo running | EventID: 19370 PDC: 0x00000 12:25:03 / 00:00:00 (~ 0,00 MB) New: Tik Tak not running | EventID: 19371 PDC: 0x00000 12:30:57 / 00:05:55 (~ 0,00 MB) New: Tik Tak running | EventID: 19371 PDC: 0x00000 12:30:57 / 00:00:00 (~ 0,00 MB) Start Recording 12:30:57 / 00:00:00 (~ 0,00 MB) New: My Very First not running | EventID: 19372 PDC: 0x00000 12:30:59 / 00:00:01 (~ 0,28 MB) PID 5300: H.264 Video, 16:9, 1920x1080, 25 fps 12:30:59 / 00:00:01 (~ 0,28 MB) PID 5301: AC3 Audio Stereo, 48 khz, 192 kbps 12:30:59 / 00:00:01 (~ 0,28 MB) PID 5302: MPEG Audio Stereo, 48 khz, 256 kbps 12:31:00 / 00:00:02 (~ 0,90 MB) PID 5304: DVB Subtitles 12:37:09 / 00:06:11 (~ 166,94 MB) New: My Very First running | EventID: 19372 PDC: 0x00000 12:37:09 / 00:06:11 (~ 167,70 MB) Stop Average Data Rate: 0,451 MB/s Total Size: 167,7 MB (175850876 Bytes) Removed Filler Data: 1,7 MB (1,2%) Quote Link to comment
Cian Posted February 17, 2021 Author Share Posted February 17, 2021 (edited) I did an event this morning, but it didn't work using the Start/Stop by EPG. I have another recording scheduled for an hour's time with Running Status. Spoiler BBC One HD (AC3,eng) 17/02/2021 F:\Recorded Video\Homes Under the Hammer - A former bank in Crewe, a flood-damaged home in Cumbria and a two-bedroom flat in London are all sold under the hammer. [S] [HD] BBC One HD (AC3,eng).ts Naming Scheme: %event - %title %station Device: Professional DVB Digital TV DVBS2 (4) EventID: 19744 Timer Name: Homes Under the Hammer - A former bank in Crewe, a flood-damaged home in Cu Timer Start: 17/02/2021 09:58:00 Timer Duration: 01:12:00 (72 min. incl. 2 min. lead time, 10 min. follow-up time) Timer Options: Teletext=0, DVB Subtitles=1, All Audio Tracks=0, Adjust PAT/PMT=1, EIT EPG Data=0, Transponder Dump=0 Timer Source: Web Monitoring Mode: Start/end update by EPG 09:58:00 / 00:00:00 (~ 0.00 MB) Start Recording 09:58:01 / 00:00:00 (~ 0.00 MB) Morning Live running | EventID: 19743 PDC: 0x00000 09:58:01 / 00:00:00 (~ 0.00 MB) Homes Under the Hammer not running | EventID: 19744 PDC: 0x00000 09:58:02 / 00:00:01 (~ 0.31 MB) PID 5401: AC3 Audio Stereo, 48 khz, 192 kbps 09:58:02 / 00:00:01 (~ 0.31 MB) PID 5404: DVB Subtitles 09:58:03 / 00:00:02 (~ 1.11 MB) PID 5400: H.264 Video, 16:9, 1920x1080, 25 fps 09:59:16 / 00:01:15 (~ 57.44 MB) Homes Under the Hammer running | EventID: 19744 PDC: 0x00000 09:59:16 / 00:01:15 (~ 58.66 MB) Wanted Down Under not running | EventID: 19745 PDC: 0x00000 10:59:44 / 01:01:43 (~ 1732.12 MB) Wanted Down Under running | EventID: 19745 PDC: 0x00000 10:59:44 / 01:01:44 (~ 1732.12 MB) Critical Incident not running | EventID: 19746 PDC: 0x00000 11:10:01 / 01:12:00 (~ 2106.96 MB) Stop Average Data Rate: 0.488 MB/s Total Size: 2107.0 MB (2209307380 Bytes) Edited February 17, 2021 by Cian Quote Link to comment
Cian Posted February 17, 2021 Author Share Posted February 17, 2021 (edited) It appears that even though I selected Running Status, it is insisting on using Start/Stop as the PDC monitor. This is the service.xml file: Spoiler <?xml version="1.0" encoding="UTF-8"?> <settings> <section name="Info"> <entry name="Version">DVBViewer Media Server V3.0.2.0</entry> </section> <section name="Service"> <entry name="Charset">0</entry> <entry name="NextEPGUpdate">1613017169</entry> <entry name="EPGBefore">2</entry> <entry name="EPGLanguage">eng</entry> <entry name="AutoTimezone">1</entry> <entry name="Timezone">60</entry> <entry name="EPGUpdateInterval">30</entry> <entry name="EPGUpdateAuto">1</entry> <entry name="OnlyFavEPG">0</entry> <entry name="AutoSearch">1</entry> <entry name="UseMulticast">1</entry> <entry name="FastEPGUpdate">1</entry> <entry name="AutoTSStreamDevice">1</entry> </section> <section name="MHW"> <entry name="Frequencies">11428h2</entry> </section> <section name="uPNP"> <entry name="UUID">DC5819C9-50D4-461C-8925-02F0DBF4AF77</entry> <entry name="UUIDSAT2IP">F02C5B90-3B75-4768-9842-243BD99AD1DB</entry> <entry name="DeviceID">242</entry> <entry name="Enabled">1</entry> </section> <section name="Recording"> <entry name="RecFormat">2</entry> <entry name="RecFormatRadio">1</entry> <entry name="RecAllAudio">0</entry> <entry name="RecDVBSub">1</entry> <entry name="RecTeletext">0</entry> <entry name="RecEITEPG">0</entry> <entry name="Minfree">300</entry> <entry name="Restartrecording">1</entry> <entry name="AutoSplitRecOnChange">1</entry> <entry name="RemoveFiller">0</entry> <entry name="Automode">0</entry> <entry name="MinFolder">25</entry> <entry name="DefAfterRecord">0</entry> <entry name="NameScheme">%event - %title %station</entry> <entry name="InfoFile">0</entry> <entry name="LogFile">1</entry> <entry name="MonitorPDC">1</entry> <entry name="MonitorForStart">2</entry> <entry name="AdjustPATPMT">1</entry> <entry name="UseEventID">2</entry> <entry name="TimeshiftDir">F:\Recorded Video</entry> </section> <section name="RecordingFolders"> <entry name="0">F:\Recorded Video</entry> <entry name="1">C:\Users\Public\Videos\</entry> </section> </settings> Is there something wrong in the entries here that I could/should change? Edited February 17, 2021 by Cian Quote Link to comment
HaraldL Posted February 17, 2021 Share Posted February 17, 2021 From your log: "Monitoring Mode: Start/end update by EPG" for this timer means that after an EPG update the timer is checked if the program times have changed and if yes (and the moved program can be found by ID) the start/stop times are changed. It does NOT mean that recording is controlled by live "... is running" / "... is not running" EPG status messages, those are only listed for information in your log. See the difference in Griga's log above: "Monitoring Mode: Start/stop by running status", here the live running status messages from EPG are used for this timer. This option can only be set for a timer when DVBViewer knows that a channel sends this information. Only then the highlighted option in my screenshot (sorry, in german) is present, otherwise it is not shown. Quote Link to comment
Griga Posted February 18, 2021 Share Posted February 18, 2021 vor 17 Stunden schrieb Cian: It appears that even though I selected Running Status, it is insisting on using Start/Stop as the PDC monitor. Your service.xml indicates "Start/Stop by EPG running status" as timer default setting. However, you also have to check the EPG Search page (if you are using it for timer creation), because it has its own independent set of timer settings. Since Media Server 3.0.1.2 (which was a beta upload) "Start/Stop by EPG running status" automagically turning into "Start/End time update from EPG" is the expected behaviour, if the EPG data for the channel in question is not the usual DVB EPG, but originates from another source. However, there is no clear indication of an external EPG in your recording log . Nevertheless it looks like the issue is caused by this change. But how and when does it happen? How do you create the timers? Did you already check the EPG monitoring setting in the timer dialog after the timer was created / before the recording was executed? See Timers page -> click the pencil (= edit timer) icon that appears on mouse over. Up to now I can't find something in the DMS code that could explain this behaviour (provided only DVB EPG is assigned to the channels). Maybe your svcdebug.log (see configuration folder) can shed more light on it. Please attach it zipped. Quote Link to comment
Cian Posted February 18, 2021 Author Share Posted February 18, 2021 Thanks for looking at this for me Griga. I create my timers using the web interface. My default in the "SearchEPG" is "Running Status", however when I click on a record icon (on the web EPG), the default that pops up is the Start/Stop. I change this to "Running Status" and click save, but when I look at the timer, is has reverted back. All of my "Search EPG" timers are set to "Running" but all the timers it generates are set to "Start/Stop" by EPG. For the purposes of this test, I disabled EPG Collector and XEPG to verify that it had nothing to do with that side of things. My next move will be to delete the service.xml file and re-configure in case there is somehting corrupted in there, but I will wait for your guidance first before I do that. Thanks, C. svcdebug.zip Quote Link to comment
Griga Posted February 18, 2021 Share Posted February 18, 2021 vor 42 Minuten schrieb Cian: when I click on a record icon (on the web EPG), the default that pops up is the Start/Stop. I change this to "Running Status" and click save, but when I look at the timer, is has reverted back. Obviously triggered by external EPG data or by something that the DMS erroneously regards as external EPG data, as soon as the DMS retrieves the corresponding EPG entry. vor 37 Minuten schrieb Cian: For the purposes of this test, I disabled EPG Collector and XEPG to verify that it had nothing to do with that side of things. That doesn't remove already stored external EPG. Additionally you need to stop the DMS, remove the file epg.dat from config subdirectory of the configuration folder, restart the DMS and perform an EPG update. This guarantees that only DVB EPG is present. vor 41 Minuten schrieb Cian: My next move will be to delete the service.xml file and re-configure in case there is somehting corrupted in there, but I will wait for your guidance first before I do that. IMO not necessary. Quote Link to comment
Cian Posted February 18, 2021 Author Share Posted February 18, 2021 (edited) Success!! I'll do some more experiments to see if I can force the issue to happen again, but for now all is good. EPG Collector needed and update, so that may have been a contributing factor (I was on 4.3.25 whereas the current version is 4.3.27). Thanks Griga, C. Edited February 18, 2021 by Cian Quote Link to comment
Cian Posted February 18, 2021 Author Share Posted February 18, 2021 So EPG Collector was the reason that "Running Status" did not work. Instead of just Channel 4 being collected, all of the channels were being collected and the Satellite EPG was being overwritten by the Web EPG, so DVBViewer behaved exactly as intended. I did not really understand the change that happened, but now it makes complete sense. Thanks again, C. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.