Jump to content

Log file of recording


jirim100

Recommended Posts

I have the following problem:

- My first broadcaster broadcast channel "CT 1" in encoding H264, but with very bad EPG informations - especially start and end program is very bad.

- My second broadcaster broadcast channel "CT 1" in encoding H265 with very good EPG informations - especially start and end program.

 

And I need to record channel "CT 1" in encoding H264, not in encoding H265.

 

Is it possible to record into .ts file only EPG data without audio and video or only create .log file where is stored start and end program?

My idea is record channel "CT 1" in encoding H264 plus record EPG data (or create only .log file) from the second mux where is "CT 1" broadcasted in encoding H265.

 

From EPG data I am automatically creating (postprocess task) .vprj file for sw Videoredo for editing recording.

 

And at the end - is it possible to write times into .log file with precision to the nearest hundredth of a second? For example:

20:37:00.12 / 00:00:00.00 (~ 0,00 MB) Start Recording

20:37:01.45 / 00:00:01.33 (~ 0,47 MB) PID 451: H.264 Video, 16:9, 1920x1080, 25 fps
...

 

Link to comment

The current bugfix uploads for DVBViewer and the Media Server contain experimental code that allows to copy the EPG of a source channel to a target channel. Originally it is intended for copying EPG data from DVB channels to IPTV channels, but maybe it is also applicable in your case.

 

Basically it works like this: The user provides a text file EPGPairingList.txt in the DVBViewer configuration folder, that defines the source and target channels. DVBViewer & DMS load it when they are started. When DVB EPG data arrives, both check if it is from one of the source channels. If yes, it is copied to the target channel. So the source channel (or its frequency) must be tuned to supply the target channel with the EPG. In your case the H.265 channel would be the source and the H.264 channel the target.

 

Currently there is a discussion about this topic in the German forum. However, I have posted the main points in English there. Give it a try, if you like. If something is not clear, please ask here...

 

Link to comment

DMS 3.0.1.0 with fix 3.0.1.2:

 

- Channel (frequency) with source EPG have to be tuned explicitly - DMS did not it automatically. Then the definition in EPGPiringList.txt seems partly working (in created .txt file with EPG detail information is stored correct source EPG).

- In log file created with recording is missing lines about  EPG1 running/ EPG2 not running - lines about EPG present/following.

- In .ts file is written old EPG, not EPG from source EPG channel (test with TS doctor).

- Maybe detail - when I manually create timer in web interface, for example with name "ct1 test" then in list of timers is not showed "ct1 test", but instead it the title of source EPG (for example "Tajemství Vatikánu: Umění a věda"). But the filename is correct: "ct1 test.ts".

 

DVBViewer is 7.0.1.3

Edited by jirim100
Link to comment

Thanks for feedback.

 

Am 10.1.2021 um 14:59 schrieb jirim100:

Channel (frequency) with source EPG have to be tuned explicitly

 

As already said in the German thread: "The source channel frequency must be tuned for supplying the target channel with EPG data. Tuning the target channel won’t do it.". With other words: The DMS will not perform additional tuning (besides the usual tuning) just because you have paired the target with the source channel.

 

Am 10.1.2021 um 14:59 schrieb jirim100:

In log file created with recording is missing lines about  EPG1 running/ EPG2 not running - lines about EPG present/following.

 

This is unexpected and will be checked. The expected result is the original present/following EPG from the recorded channel. The present/following logging always needs a broadcasted "live" EPG. It can't be retrieved from an imported or copied EPG.

 

Am 10.1.2021 um 14:59 schrieb jirim100:

In .ts file is written old EPG, not EPG from source EPG channel (test with TS doctor).

 

A recorded EPG is always the original EPG from the recorded channel, not the copied EPG. That can't be changed.

 

Am 10.1.2021 um 14:59 schrieb jirim100:

when I manually create timer in web interface, for example with name "ct1 test" then in list of timers is not showed "ct1 test", but instead it the title of source EPG (for example "Tajemství Vatikánu: Umění a věda").

 

This is intended. Beginning with DMS 3.0 EPG information (the title and complete subheading) is stored additionally in timer data sets and used in this case. Previously only the timer name was stored, which can be composed of the EPG title and subheading (the latter shortened, if too long), but also be user defined. Thus timers did not contain reliable EPG information, which caused problems particularly when automatically creating timers from EPG seach results (auto-timers) and comparing them with already existing timers. This is different now.

 

Link to comment
19 minutes ago, Griga said:

A recorded EPG is always the original EPG from the recorded channel, not the copied EPG. That can't be changed.

Hm. This is sad for me. I need information EPG present/following from source channel.

 

19 minutes ago, Griga said:

This is intended. Beginning with DMS 3.0 EPG information (the title and complete subheading) is stored additionally in timer data sets and used in this case. Previously only the timer name was stored, which can be composed of the EPG title and subheading (the latter shortened, if too long), but also be user defined. Thus timers did not contain reliable EPG information, which caused problems particularly when automatically creating timers from EPG seach results (auto-timers) and comparing them with already existing timers. This is different now.

 

Ok.

Link to comment
vor 1 Minute schrieb jirim100:

I need information EPG present/following from source channel.

 

The only solution I know ATM is to always record both channels and then drop the HEVC recording, but keep the logged information.

 

Link to comment
vor 1 Stunde schrieb Griga:

 

Am 10.1.2021 um 14:59 schrieb jirim100:

In log file created with recording is missing lines about  EPG1 running/ EPG2 not running - lines about EPG present/following.

 

This is unexpected and will be checked. The expected result is the original present/following EPG from the recorded channel.

 

The present/following info seems to be generally missing in the log file if the timer is created manually in the Web Interface with Timer -> New Timer (will be fixed). However, it should be present if a timer is created from one of the EPG pages. Can you confirm this?

 

Link to comment

- Yes, when is manually created then EPG present/following in log missing (what means these multiple lines with audio format? - my reception is bad)  :

Spoiler



CT 2 HD T2 12.1.2021
W:\For The Record\poslední oběť; ; ; ; vysíláno 2021-01-12.ts
Naming Scheme: %name; ; ; ; vysíláno %year-%m-%d
Device: AVerMedia TD310 BDA Filter (4)
Timer Name: poslední oběť
Timer Start: 12.1.2021 12:50:00
Timer Duration: 01:00:00 (60 min.)
Timer Options: Teletext=1, DVB Subtitles=1, All Audio Tracks=1, Adjust PAT/PMT=1, EIT EPG Data=1, Transponder Dump=0
Timer Source: Web

13:05:25 / 00:00:00 (~ 0,00 MB) Start Recording
13:05:26 / 00:00:01 (~ 0,83 MB) PID 2220: LATM AAC Audio Stereo, 48 khz, 158 kbps
13:05:26 / 00:00:01 (~ 0,83 MB) PID 2221: LATM AAC Audio Stereo, 48 khz, 148 kbps
13:05:26 / 00:00:01 (~ 0,83 MB) PID 2222: AC3 Audio Stereo, 48 khz, 448 kbps
13:05:26 / 00:00:01 (~ 0,83 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 64 kbps
13:05:26 / 00:00:01 (~ 0,83 MB) PID 2130: Videotext
13:05:27 / 00:00:02 (~ 2,26 MB) PID 2210: HEVC Video, 16:9, 1920x1080, 50 fps
13:05:32 / 00:00:06 (~ 7,60 MB) PID 2223: ADTS AAC Audio 7.1, 8 khz, 498 kbps
13:05:33 / 00:00:07 (~ 9,10 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 66 kbps
13:06:02 / 00:00:37 (~ 36,46 MB) PID 2223: LATM AAC Audio 10.0, 64 khz, 84 kbps
13:06:04 / 00:00:39 (~ 38,20 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 65 kbps
13:06:12 / 00:00:47 (~ 44,90 MB) PID 2223: LATM AAC Audio 10.0, 64 khz, 84 kbps
13:06:13 / 00:00:48 (~ 45,43 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 67 kbps
13:06:37 / 00:01:12 (~ 63,11 MB) PID 2250: DVB Subtitles
13:07:28 / 00:02:03 (~ 87,26 MB) PID 2223: LATM AAC Audio 5.1, 64 khz, 84 kbps
13:07:29 / 00:02:04 (~ 87,71 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 66 kbps
13:07:48 / 00:02:23 (~ 96,11 MB) PID 2223: ADTS AAC Audio 5.1, 64 khz, 1674 kbps
13:07:49 / 00:02:24 (~ 96,57 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 64 kbps
13:08:26 / 00:03:01 (~ 117,92 MB) PID 2223: LATM AAC Audio 10.0, 64 khz, 91 kbps
13:08:27 / 00:03:02 (~ 118,42 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 67 kbps
13:09:00 / 00:03:34 (~ 138,87 MB) Errors: 18
13:09:00 / 00:03:34 (~ 138,87 MB) PID 2223: ADTS AAC Audio Stereo, 24 khz, 1110 kbps
13:09:01 / 00:03:35 (~ 139,28 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 64 kbps
13:09:11 / 00:03:45 (~ 144,15 MB) PID 2223: LATM AAC Audio 10.0, 64 khz, 84 kbps
13:09:12 / 00:03:46 (~ 144,58 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 69 kbps
13:09:30 / 00:04:05 (~ 161,06 MB) PID 2223: LATM AAC Audio 10.0, 64 khz, 84 kbps
13:09:31 / 00:04:06 (~ 162,22 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 66 kbps
13:10:19 / 00:04:53 (~ 185,76 MB) PID 2223: ADTS AAC Audio 5.1, 64 khz, 205 kbps
13:10:20 / 00:04:54 (~ 186,13 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 64 kbps
13:11:32 / 00:06:06 (~ 223,32 MB) PID 2223: ADTS AAC Audio 7.1, 24 khz, 978 kbps
13:11:34 / 00:06:08 (~ 224,73 MB) PID 2223: LATM AAC Audio Mono, 48 khz, 66 kbps
13:11:40 / 00:06:14 (~ 229,57 MB) PID 2223: LATM AAC Audio 10.0, 64 khz, 83 kbps

 


 

- From search preset - EPG present/following is included:

Spoiler



CT :D 11.1.2021
W:\For The Record\Emoce v umění (1. díl) - Extáze; vysíláno 2021-01-11.ts
Naming Scheme: %name; vysíláno %year-%m-%d
Device: Professional DVB Digital TV DVB-T2 (1)
EventID: 1378595936
Timer Name: Emoce v umění (1. díl) - Extáze
Timer Start: 11.1.2021 22:20:00
Timer Duration: 01:27:00 (87 min. incl. 15 min. lead time, 22 min. follow-up time)
Timer Options: Teletext=1, DVB Subtitles=1, All Audio Tracks=1, Adjust PAT/PMT=1, EIT EPG Data=1, Transponder Dump=0
Timer Source: Search:Emoce v umění

22:20:00 / 00:00:00 (~ 0,00 MB) Start Recording
22:20:01 / 00:00:00 (~ 0,00 MB) Emoce v umění: Extáze (1. díl) not running | EventID: 13811 PDC: 0x00000
22:20:01 / 00:00:00 (~ 0,00 MB) EventID change 1378595936 to 13811
22:20:01 / 00:00:01 (~ 0,41 MB) PID 1501: MPEG2 Video, 16:9, 720x576, 25 fps
22:20:01 / 00:00:01 (~ 0,41 MB) PID 1502: MPEG Audio Stereo, 48 khz, 128 kbps
22:20:01 / 00:00:01 (~ 0,41 MB) PID 1503: MPEG Audio Mono, 48 khz, 64 kbps
22:20:01 / 00:00:01 (~ 0,41 MB) PID 1504: MPEG Audio Stereo, 48 khz, 128 kbps
22:20:01 / 00:00:01 (~ 0,41 MB) PID 1505: Videotext
22:20:02 / 00:00:01 (~ 0,41 MB) Hašler... running | EventID: 13812 PDC: 0x00000
22:20:30 / 00:00:29 (~ 15,12 MB) PID 1506: DVB Subtitles
22:34:48 / 00:14:47 (~ 486,29 MB) Emoce v umění: Extáze (1. díl) running | EventID: 13811 PDC: 0x00000
22:34:49 / 00:14:48 (~ 486,61 MB) Posledná bosorka not running | EventID: 13807 PDC: 0x00000
23:10:00 / 00:50:00 (~ 1674,01 MB) Emoce v umění: Extáze (1. díl) running | EventID: 13811 PDC: 0x00000
23:10:02 / 00:50:01 (~ 1674,62 MB) Posledná bosorka not running | EventID: 13807 PDC: 0x00000
23:24:48 / 01:04:47 (~ 2151,24 MB) Posledná bosorka running | EventID: 13807 PDC: 0x00000
23:24:49 / 01:04:48 (~ 2151,88 MB) Cesty Zdeňka Mácala not running | EventID: 13878 PDC: 0x00000
23:47:00 / 01:26:59 (~ 2952,20 MB) Stop

Average Data Rate: 0,566 MB/s
Total Size: 2952,2 MB (3095603112 Bytes)


 

 

Edited by Griga
Spoiler Tags added
Link to comment

Thanks for testing! :)It saved me some work.

 

vor 4 Stunden schrieb jirim100:

what means these multiple lines with audio format?

 

The recorder format detection desperately tries to get in sync with the audio frame structure, but can't for some reason. That's why it reads random audio data as frame headers (containing format information), which are no frame headers.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...