VNSI Kodi 17 Mac specific channel results in crash

July 6, 2017, 12:57 pm

≫ Next: Recordings list empty from time to time

≪ Previous: Rewind livetv and record from that position

Hello ,

I'm trying to use vnsi plugin with kodi17 on my mac.

If a zap to a program called ZDF HD , Kodi does show one or two pictures from that channel sound work well but than the stream stops and kodi crashes.

Debug log got a lot of these errors.

root@tv-server:~# vdr -V
vdr (2.2.0/2.2.0) - The Video Disk Recorder
vnsiserver (1.5.2) - VDR-Network-Streaming-Interface (VNSI) Server

Quote:21:40:28.603 T:123145501323264 ERROR: ffmpeg[70000BDCB000]: [h264] Missing reference picture, default is 0
21:40:28.603 T:123145501323264 ERROR: ffmpeg[70000BDCB000]: [h264] decode_slice_header error
21:40:28.604 T:123145501323264 ERROR: ffmpeg[70000BDCB000]: [h264] hardware accelerator failed to decode picture
21:40:28.604 T:123145501323264 ERROR: Decode - avcodec_decode_video returned failure
21:40:28.604 T:123145501323264 DEBUG: CVideoPlayerVideo - video decoder returned error
21:40:28.808 T:123145501323264 ERROR: Decode - avcodec_decode_video returned failure
21:40:28.808 T:123145501323264 DEBUG: CVideoPlayerVideo - video decoder returned error
21:40:28.808 T:123145501323264 INFO: CVideoPlayerVideo - Stillframe detected, switching to forced 50.000000 fps
21:40:28.818 T:123145500786688 WARNING: VideoPlayer::Sync - stream player video does not start, flushing buffers
21:40:28.818 T:123145500786688 DEBUG: CVideoPlayer::FlushBuffers - flushing buffers
21:40:28.827 T:123145507225600 DEBUG: CDVDAudio::Flush - flush audio stream
21:40:28.827 T:123145507225600 DEBUG: CDVDAudio::Pause - pausing audio stream
21:40:28.827 T:123145507225600 DEBUG: CVideoPlayerAudio - CDVDMsg::GENERAL_SYNCHRONIZE
21:40:28.827 T:123145501323264 DEBUG: CVideoPlayerVideo - CDVDMsg::GENERAL_SYNCHRONIZE
21:40:28.827 T:123145500786688 DEBUG: CVideoPlayer::SetCaching - caching state 2
21:40:28.827 T:123145500786688 DEBUG: CDVDClock::SetSpeedAdjust - adjusted:0.000000
21:40:28.836 T:123145501323264 INFO: CVideoPlayerVideo - Stillframe left, switching to normal playback
21:40:28.836 T:123145501323264 DEBUG: CVideoPlayerVideo::CalcDropRequirement - hurry: 0
21:40:28.838 T:123145507225600 DEBUG: CDVDAudio::Pause - pausing audio stream
21:40:28.845 T:123145501323264 DEBUG: CDVDVideoCodecFFmpeg - Updated codec: ff-h264
21:40:28.854 T:123145501323264 INFO: CBitstreamConverter::Open annexb to bitstream init
21:40:28.854 T:123145500786688 DEBUG: CVideoPlayer::HandleMessages - player started 1
21:40:28.873 T:123145501323264 DEBUG: CDVDVideoCodecFFmpeg - Updated codec: ff-h264-vtb
21:40:28.878 T:123145501323264 DEBUG: CVideoPlayerVideo::CalcDropRequirement - hurry: 0
21:40:28.880 T:123145501323264 ERROR: ffmpeg[70000BDCB000]: [h264] co located POCs unavailable

Crashlog https://pastebin.com/s0jPPE0L

Anyone interested to dig deeper ?

↧

Recordings list empty from time to time

July 15, 2017, 6:04 am

≫ Next: Kodi, VDR and Slackware [SOLVED]

≪ Previous: VNSI Kodi 17 Mac specific channel results in crash

Hi everyone,

came across this strange behaviour:
-> My libreelec with Kodi 17.3 and VDR VNSI Addon starts, I enter "Recordings", everything fine, all recordings are visible
-> Then I watch some video, TV aso aso.
-> After a while I again enter "Recordings" and the list is completely empty.
-> Restart of libreelec doesn't help
-> De-activating / Activiating of VNSI Addon doesn't help
What helps:
-> In Live TV settings "Delete all data" OR
-> touch .update file in VDR's recordings dir

Any idea?
Thx a lot
Snoopy

↧

Kodi, VDR and Slackware [SOLVED]

August 5, 2017, 8:35 am

≫ Next: Kodi17.3 on Manjaro - Audio only with VNSI client. No video appears

≪ Previous: Recordings list empty from time to time

I hope this is the right place to post this! I'm running Slackware64-current on an Intel platform, which means I have to compile everything from scratch. Gcc version is 7.1.0. Tv hardware is a PCTV usb stick 292e. This works fine with Kaffeine, VLC and the various dvb utilities, so I know the hardware is OK.

Finding all the documentation on how to achieve success has not been easy, but I'm *almost* there! I've successfully compiled Kodi with the vdr plugin. As far as I can tell, anyway! Kodi runs fine and recognises the plugin, so hopefully all is well.

Compiling vdr proved a problem, until Klaus pointed me towards the developer versions. 2.3.8 built fine. However, none of the techniques I found for compiling the vnsi server worked. It all seemed to compile OK (no errors) but nothing in the lib directory either! In the end, I did a git clone of vnsiserver, placed the resulting folder in the PLUGINS/src directory of vdr, and then rebuilt vdr. This seemed to work. There were no errors, and all the expected files were present after compiling.

So, as far as I can tell, everything is built without errors.

However, when I run kodi, and select TV, I get the channels list (yes, I did manage to build a compatible channels.conf!), but as soon as I click on a channel to watch it, I get an error message saying that the connection to the server has been lost. Sometimes I see a few seconds of video in the background before it freezes. After a few seconds, the connection is re-established, but as soon as I click on a channel, it fails again.

Running vdr from a command prompt as root produces the following error:

Code:

runvdr: line 69:  4093 Segmentation fault      /usr/local/bin/vdr -w 60 --lib=/usr/local/lib/vdr --video=/Multimedia/Recordings/vdr --epgfile=/Multimedia/Recordings/vdr/epg --config=/etc/vdr -P vnsiserver

the syslog shows:

Code:

Aug  5 10:13:59 Lightning vdr: [4093] ERROR: no OSD provider available - using dummy OSD!

Aug  5 10:14:16 Lightning last message repeated 2 times

Aug  5 10:14:30 Lightning vdr: [4168] ERROR: no OSD provider available - using dummy OSD!

and dmesg shows:

Code:

[ 5641.512978] cLiveStreamer s[4150]: segfault at 38 ip 00000000004acb40 sp 00007f9f627fbd68 error 4 in vdr[400000+192000]

[ 5651.541471] si2168 8-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'

[ 5651.998607] si2168 8-0064: firmware version: B 4.0.25

I'm now stumped! I've no doubt its something I've done wrong, or configured incorrectly, but I can't see what.

Any help gratefully appreciated!

--
Pete

↧

Kodi17.3 on Manjaro - Audio only with VNSI client. No video appears

August 5, 2017, 10:33 am

≫ Next: Different Recording and Timeshift Directories

≪ Previous: Kodi, VDR and Slackware [SOLVED]

Hello Folks.

I encountered a problem setting up my kodi vnsi combo at home. I have one NUC connected to my TV running a combo of

Manjaro Linux
Kodi 17.3
aur/kodi-addon-pvr-vdr-vnsi 2.6.17-1

Until recently the VNSI server was running on an external Ubuntu machine which is - unfortunately - out of service now. So I added the Geniatec T230C DVB-T2 stick (+firmware files) to the manjaro box above and installed:

aur/vdr-vnsiserver 2:1.5.2-1

After making all necessary config changes, I am able to select my channels in Kodi, but I only get the audio signal, no video. Funny thing is that I can access the vdr-streamdev outside of kodi by VLC directly and happily watch all channels with audio and video. Therefore I guess, there is some incompatibility between the vnsiserver and the addon in Kodi that I am using? Any suggestions what I should do on my platform? Any help would be greatly appreciated.

Here is the system-log of vdr starting and an unsuccessful connection-try:

Code:

Aug  5 19:04:01 shakuras vdr[7000]: [7000] VDR version 2.2.0 started           

Aug  5 19:04:01 shakuras vdr[7000]: [7000] switched to user 'vdr'              

Aug  5 19:04:01 shakuras vdr[7000]: [7000] codeset is 'UTF-8' - known          

Aug  5 19:04:01 shakuras vdr[7000]: [7000] override character table is 'ISO-8859-15'                                                                           

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-client.so.2.2.0                                               

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.2.0                                               

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.2.0                                                     

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/setup.conf     

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/sources.conf   

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/diseqc.conf    

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/scr.conf       

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/channels.conf  

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/timers.conf    

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/svdrphosts.conf                                                                                

Aug  5 19:04:01 shakuras vdr[7000]: [7000] loading /var/lib/vdr/keymacros.conf 

Aug  5 19:04:02 shakuras vdr[7000]: [7000] DVB API version is 0x050A (VDR was built with 0x050A)                                                               

Aug  5 19:04:02 shakuras vdr[7000]: [7000] frontend 0/0 provides DVB-T,DVB-T2,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Silicon Labs Si2168")          

Aug  5 19:04:02 shakuras vdr[7000]: [7000] found 1 DVB device                  

Aug  5 19:04:02 shakuras vdr[7000]: [7000] initializing plugin: streamdev-client (0.6.1-git): VTP Streaming Client                                             

Aug  5 19:04:02 shakuras vdr[7000]: [7000] initializing plugin: streamdev-server (0.6.1-git): VDR Streaming Server                                             

Aug  5 19:04:02 shakuras vdr[7000]: [7000] initializing plugin: vnsiserver (1.5.2): VDR-Network-Streaming-Interface (VNSI) Server                              

Aug  5 19:04:02 shakuras vdr[7000]: [7000] setting primary device to 1         

Aug  5 19:04:02 shakuras vdr[7000]: [7000] device 1 has no MPEG decoder        

Aug  5 19:04:02 shakuras vdr[7000]: [7000] SVDRP listening on port 6419        

Aug  5 19:04:02 shakuras vdr[7000]: [7000] setting current skin to "lcars"     

Aug  5 19:04:02 shakuras vdr[7000]: [7000] loading /var/lib/vdr/themes/lcars-default.theme                                                                     

Aug  5 19:04:02 shakuras vdr[7000]: [7000] starting plugin: streamdev-client   

Aug  5 19:04:02 shakuras vdr[7000]: [7000] starting plugin: streamdev-server   

Aug  5 19:04:02 shakuras vdr[7000]: [7000] loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf                                                   

Aug  5 19:04:02 shakuras vdr[7000]: [7000] starting plugin: vnsiserver         

Aug  5 19:04:02 shakuras vdr[7000]: [7000] VNSI: Starting vnsi server at port=34890                                                                            

Aug  5 19:04:02 shakuras vdr[7000]: [7008] Streamdev: Listening (VTP) on port 2004                                                                             

Aug  5 19:04:02 shakuras vdr[7000]: [7008] Streamdev: Listening (HTTP) on port 3000                                                                            

Aug  5 19:04:02 shakuras vdr[7000]: [7000] VNSI: VNSI Server started           

Aug  5 19:04:02 shakuras vdr[7000]: [7000] VNSI: Channel streaming timeout: 10 seconds                                                                         

Aug  5 19:04:02 shakuras vdr[7000]: [7000] switching to channel 5 (ZDF HD)     

Aug  5 19:04:02 shakuras vdr[7000]: [7010] VNSI: Requesting clients to reload channel list                                                                     

Aug  5 19:04:38 shakuras vdr[7000]: [7009] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf                                                          

Aug  5 19:04:38 shakuras vdr[7000]: [7009] VNSI: Client with ID 0 connected: 192.168.1.58:42180                                                                

Aug  5 19:04:38 shakuras vdr[7000]: [7029] VNSI: Welcome client 'XBMC Media Center' with protocol version '10'                                                 

Aug  5 19:04:42 shakuras vdr[7000]: [7009] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf                                                          

Aug  5 19:04:42 shakuras vdr[7000]: [7009] VNSI: Client with ID 1 connected: 192.168.1.58:42198                                                                

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: Welcome client 'XBMC Media Center' with protocol version '10'                                                 

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: LiveStreamer::Close - close   

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: close video input ...         

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: Successfully found following device: 0x9dac752960 (1) for receiving, priority=0                               

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: Dummy receiver (0x7f3620003950) activated                                                                     

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: activate live receiver: 1     

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: Successfully switched to channel 5 - ZDF HD                                                                   

Aug  5 19:04:42 shakuras vdr[7000]: [7032] VNSI: Started streaming of channel ZDF HD (timeout 10 seconds)                                                      

Aug  5 19:04:42 shakuras vdr[7000]: [7035] VNSI: Created stream for pid=2120 and type=3                                                                        

Aug  5 19:04:42 shakuras vdr[7000]: [7035] VNSI: Created stream for pid=2121 and type=3                                                                        

Aug  5 19:04:42 shakuras vdr[7000]: [7035] VNSI: Created stream for pid=2131 and type=10                                                                       

Aug  5 19:04:42 shakuras vdr[7000]: [7035] VNSI: Created stream for pid=2130 and type=12                                                                       

Aug  5 19:04:42 shakuras vdr[7000]: [7035] VNSI: Audio stream change, pid: 2120, channels: 2, samplerate: 48000                                                

Aug  5 19:04:42 shakuras vdr[7000]: [7035] VNSI: Audio stream change, pid: 2121, channels: 2, samplerate: 48000                                                

Aug  5 19:04:47 shakuras vdr[7000]: [7035] VNSI: exit streamer thread          

Aug  5 19:04:47 shakuras vdr[7000]: [7032] VNSI: LiveStreamer::Close - close   

Aug  5 19:04:47 shakuras vdr[7000]: [7032] VNSI: close video input ...         

Aug  5 19:04:47 shakuras vdr[7000]: [7032] VNSI: activate live receiver: 0     

Aug  5 19:04:47 shakuras vdr[7000]: [7032] VNSI: Dummy receiver (0x7f3620003950) deactivated                                                                   

Aug  5 19:04:47 shakuras vdr[7000]: [7032] VNSI: close video input ...         

Aug  5 19:04:47 shakuras vdr[7000]: [7032] VNSI: cxSocket::read(fd=16): eof, connection closed                                                                 

Aug  5 19:04:47 shakuras vdr[7000]: [7010] VNSI: Client with ID 1 seems to be disconnected, removing from client list                                          

Aug  5 19:04:48 shakuras vdr[7000]: [7029] VNSI: cxSocket::read(fd=15): eof, connection closed                                                                 

Aug  5 19:04:49 shakuras vdr[7000]: [7010] VNSI: Client with ID 0 seems to be disconnected, removing from client list

↧

Different Recording and Timeshift Directories

August 13, 2017, 2:37 pm

≫ Next: Timer based recoding doesn't terminate / kodi and vdr disconnect

≪ Previous: Kodi17.3 on Manjaro - Audio only with VNSI client. No video appears

After some googling I found we can change the default recording directory on linux from /var/lib/video by setting VIDEO_DIR in /etc/default/vdr but it also now places timeshift files in there. Is there a way to specify a different directory for timeshift files?

Thanks

↧

Timer based recoding doesn't terminate / kodi and vdr disconnect

August 22, 2017, 9:21 am

≫ Next: CA_PMT problem with VDR

≪ Previous: Different Recording and Timeshift Directories

I am expereincing a strange issue now for at least the second time. I have not yet been able to reproduce the exact circumstances which triggers the issue, but I believe it is not accidental.

What happened:

Last night I set up a timer based recording for vdr. I did this in kodi by selecting the 'record' entry from the context menu of the highlighted title in the guide.

Timer created:

Code:

Sky Cinema Comedy - Taxi 22.08.2017 from 04:42 to 06:20

As you can see from the attached log vdr starts recording on schedule at 4:42.
It then stops recording at 6:11 (seemingly "due to modification of channel 131 (Sky Cinema Comedy)") and instantly resumes or rather restarts recording a second later.

There is no log entry at 6:20 when the recording was actually supposed to end according to timer settings.
In fact, recording continued until the late afternoon when I noticed it and eventually rebooted the system. Choosing "end recording" didn't give me a result and it looked as kodi was completely disconnect from vdr (system did not react to opening vdr osd from client specific settings).

The errors it threw were:

Code:

Aug 22 17:24:00 localhost vdr: [2775] ERROR: video data stream broken

Aug 22 17:24:00 localhost vdr: [2775] initiating emergency exit

Checking the recoding and the recording folder I found the recording had in fact continued for more than 12 hours:

Code:

kodi@kodi-mc:~/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec$ ls -ls

insgesamt 16762220

1877432 -rw-rw-r-- 1 vdr vdr 1922484804 Aug 22 06:11 00001.ts

8192136 -rw-rw-r-- 1 vdr vdr 8388743112 Aug 22 13:09 00002.ts

6683756 -rw-rw-r-- 1 vdr vdr 6844161432 Aug 22 17:29 00003.ts

   8892 -rw-rw-r-- 1 vdr vdr    9100832 Aug 22 17:21 index

      4 -rw-rw-r-- 1 vdr vdr        666 Aug 22 06:11 info

Although, apparently for everything after 6:11 the recoding shows only a black screen.

I am not sure if this actually a kodi/vnsi issue or if this is more inside vdr. Hence, any guidance is much appreciated.

Here is the syslog for the relevant time interval:

Code:

Aug 22 04:41:01 localhost vdr: [1106] switching device 2 to channel 131 S19.2E-133-3-8 (Sky Cinema Comedy)

Aug 22 04:41:02 localhost vdr: [1455] changing pids of channel 131 (Sky Cinema Comedy) from 1023+1023=27:1024=deu@3,1025=eng@3;1027=deu@106:0:0 to 1023+1023=27:1024=deu@3;1027=deu@106:0:0

Aug 22 04:41:02 localhost vdr: [1455] channel 131 (Sky Cinema Comedy) event Di. 22.08.2017 04:45-06:15 'Taxi' status 4

Aug 22 04:41:02 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 04:41:02 localhost vdr: [1455] changing pids of channel 128 (Sky Cinema +1) from 255+255=27:256=deu@3,257=eng@3;259=deu@106:0:0 to 255+255=27:256=deu@3;259=deu@106:0:0

Aug 22 04:41:02 localhost vdr: [1455] changing pids of channel 88 (Disney XD) from 1279+1279=27:1280=deu@3:0:0 to 1279+1279=27:1280=deu@3,1281=eng@3:0:0

Aug 22 04:41:07 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 04:41:36 localhost vdr: [2307] epg data writer thread started (pid=1106, tid=2307, prio=low)

Aug 22 04:41:36 localhost vdr: [2307] epg data writer thread ended (pid=1106, tid=2307)

Aug 22 04:42:00 localhost vdr: [1106] CAM 1/1: creating new MTD CAM slot

Aug 22 04:42:00 localhost vdr: [1106] CAM 1: assigned to device 2

Aug 22 04:42:00 localhost vdr: [1106] switching device 2 to channel 131 S19.2E-133-3-8 (Sky Cinema Comedy)

Aug 22 04:42:00 localhost vdr: [2310] device 2 receiver thread started (pid=1106, tid=2310, prio=high)

Aug 22 04:42:00 localhost vdr: [1106] timer 1 (131 0442-0620 'Taxi') start

Aug 22 04:42:00 localhost vdr: [1106] Title: 'Taxi' Subtitle: 'Actionkomödie'

Aug 22 04:42:00 localhost vdr: [1106] executing '/usr/lib/vdr/vdr-recordingaction before "/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec"'

Aug 22 04:42:00 localhost vdr: [2311] device 2 TS buffer thread started (pid=1106, tid=2311, prio=high)

Aug 22 04:42:00 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom before recording /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 04:42:00 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R91.custom before recording /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 04:42:00 localhost vdr: [1106] record /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 04:42:00 localhost vdr: [1106] creating directory /home/kodi/Aufnahmen/Taxi

Aug 22 04:42:00 localhost vdr: [1106] creating directory /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 04:42:00 localhost vdr: [1106] recording to '/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec/00001.ts'

Aug 22 04:42:00 localhost vdr: [2332] recording thread started (pid=1106, tid=2332, prio=high)

Aug 22 04:42:00 localhost vdr: [1578] VNSI: Requesting clients to reload timers

Aug 22 04:42:01 localhost vdr: [1578] VNSI: Requesting clients to reload recordings list

Aug 22 04:42:02 localhost vdr: [2332] executing '/usr/lib/vdr/vdr-recordingaction started "/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec"'

Aug 22 04:42:02 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom

Aug 22 04:42:02 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R91.custom

Aug 22 04:42:23 localhost vdr: [1582] SVDRP < 127.0.0.1:41998 client connection accepted

Aug 22 04:42:23 localhost vdr: [1582] SVDRP < 127.0.0.1:41998 server created

Aug 22 04:42:25 localhost vdr: [1582] SVDRP < 127.0.0.1:41998 connection closed

Aug 22 04:42:25 localhost vdr: [1582] SVDRP < 127.0.0.1:41998 server destroyed

Aug 22 04:51:26 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 05:04:27 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 05:05:27 localhost vdr: [1881] VNSI: Video stream change, pid: 167, width: 720, height: 576, aspect: 1,777778

Aug 22 05:17:01 localhost CRON[2444]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 05:17:27 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 05:25:59 localhost vdr: [1455] changing pids of channel 129 (Sky Cinema +24) from 511+511=27:512=deu@3,513=eng@3;515=deu@106:0:0 to 511+511=27:512=deu@3;515=deu@106:0:0

Aug 22 05:26:00 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:30:28 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 05:41:44 localhost vdr: [1106] =====================

Aug 22 05:41:44 localhost vdr: [1106] EPG bugfix statistics

Aug 22 05:41:44 localhost vdr: [1106] =====================

Aug 22 05:41:44 localhost vdr: [1106] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED

Aug 22 05:41:44 localhost vdr: [1106] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs()

Aug 22 05:41:44 localhost vdr: [1106] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT!

Aug 22 05:41:44 localhost vdr: [1106] =====================

Aug 22 05:41:44 localhost vdr: [1106] Fix Hits Channels

Aug 22 05:41:44 localhost vdr: [1106] 3   361  ANIXE HD, RTL Crime HD, Disney Junior, Goldstar TV, Heimatkanal, Sky Atlantic +1 HD, ...

Aug 22 05:41:44 localhost vdr: [1106] 4   24   NDR Info Spez., NDR Info, ARD-alpha, SWR2, BR-KLASSIK, SR 2 KulturRadio, 3sat HD, ...

Aug 22 05:41:44 localhost vdr: [1106] 6   2612 tagesschau24, arte, PHOENIX, ONE, hr-fernsehen HD, MDR Sachsen HD, rbb Berlin HD, ...

Aug 22 05:41:44 localhost vdr: [1106] 7   114  tagesschau24, tagesschau24 HD, NDR FS NDS HD, NDR FS NDS, WDR Event, Eurosport 1 HD, ...

Aug 22 05:41:44 localhost vdr: [1106] 8   1343 Romance TV, DELUXE MUSIC, ANIXE SD, TLC, SIXX, N24 DOKU, kabel eins, N24, ...

Aug 22 05:41:44 localhost vdr: [1106] 9   1343 Romance TV, DELUXE MUSIC, ANIXE SD, TLC, SIXX, N24 DOKU, kabel eins, N24, ...

Aug 22 05:41:44 localhost vdr: [1106] =====================

Aug 22 05:43:28 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 05:46:30 localhost vdr: [1881] VNSI: exit streamer thread

Aug 22 05:46:30 localhost vdr: [1881] cLiveStreamer stream processor thread ended (pid=1106, tid=1881)

Aug 22 05:46:30 localhost vdr: [1879] VNSI: LiveStreamer::Close - close

Aug 22 05:46:30 localhost vdr: [1879] VNSI: close video input ...

Aug 22 05:46:30 localhost vdr: [1879] VNSI: activate live receiver: 0

Aug 22 05:46:30 localhost vdr: [1879] VNSI: Dummy receiver (0x7fbba000b740) deactivated

Aug 22 05:46:30 localhost vdr: [1882] device 1 TS buffer thread ended (pid=1106, tid=1882)

Aug 22 05:46:30 localhost vdr: [1880] buffer stats: 126900 (2%) used

Aug 22 05:46:30 localhost vdr: [1880] device 1 receiver thread ended (pid=1106, tid=1880)

Aug 22 05:46:30 localhost vdr: [1879] VNSI: close video input ...

Aug 22 05:46:30 localhost vdr: [1879] VNSI: cxSocket::read(fd=21): eof, connection closed

Aug 22 05:46:30 localhost vdr: [1879] VNSI Client 5->192.168.178.15:49644 thread ended (pid=1106, tid=1879)

Aug 22 05:46:30 localhost vdr: [1578] VNSI: Client with ID 5 seems to be disconnected, removing from client list

Aug 22 05:46:34 localhost vdr: [1866] VNSI: cxSocket::read(fd=26): eof, connection closed

Aug 22 05:46:35 localhost vdr: [1866] VNSI: Stopping scan plugin not reported back and stop maybe not complete confirmed

Aug 22 05:46:35 localhost vdr: [1866] VNSI Client 2->192.168.178.15:49624 thread ended (pid=1106, tid=1866)

Aug 22 05:46:35 localhost vdr: [1578] VNSI: Client with ID 2 seems to be disconnected, removing from client list

Aug 22 05:51:21 localhost vdr: [1451] changing pids of channel 137 (Sky Arts HD) from 767+767=27:0;771=deu@106,772=eng@106:0:0 to 767+767=27:0;771=deu@106:0:0

Aug 22 05:51:21 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:52:07 localhost /usr/lib/snapd/snapd[1004]: snapmgr.go:422: No snaps to auto-refresh found

Aug 22 05:52:07 localhost snapd[1004]: 2017/08/22 05:52:07.057096 snapmgr.go:422: No snaps to auto-refresh found

Aug 22 05:53:48 localhost vdr: [1451] changing pids of channel 147 (Sky Sport 2) from 1791+1791=27:1792=qae@3,1793=qaf@3:0:32 to 1791+1791=27:1792=qae@3:0:32

Aug 22 05:53:48 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:53:48 localhost vdr: [1451] changing pids of channel 125 (Disney Cinemagic) from 3327+3327=27:3328=deu@3,3329=eng@3:0:0 to 3327+3327=27:3328=deu@3:0:0

Aug 22 05:53:48 localhost vdr: [1451] changing pids of channel 134 (Sky Cinema Hits) from 255+255=27:256=deu@3;259=deu@106:0:0 to 255+255=27:256=deu@3,257=eng@3;259=deu@106:0:0

Aug 22 05:53:53 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:54:51 localhost vdr: [1451] changing pids of channel 83 (A&E) from 1791+1791=27:1792=deu@3:0:0 to 1791+1791=27:1792=deu@3,1793=eng@3:0:0

Aug 22 05:54:51 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:55:12 localhost vdr: [1451] changing pids of channel 110 (Discovery HD) from 1023+1023=27:0;1027=deu@106,1028=eng@106:0:0 to 1023+1023=27:0;1027=deu@106:0:0

Aug 22 05:55:12 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:55:39 localhost vdr: [1455] changing pids of channel 128 (Sky Cinema +1) from 255+255=27:256=deu@3;259=deu@106:0:0 to 255+255=27:256=deu@3,257=@3;259=deu@106:0:0

Aug 22 05:55:39 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:55:40 localhost vdr: [1455] changing pids of channel 128 (Sky Cinema +1) from 255+255=27:256=deu@3,257=@3;259=deu@106:0:0 to 255+255=27:256=deu@3,257=eng@3;259=deu@106:0:0

Aug 22 05:55:44 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:55:54 localhost vdr: [1451] changing pids of channel 161 (Sky Sport 2 HD) from 1023+1023=27:0;1026=qae@106,1027=qaf@106,1028=qtz@106:0:32 to 1023+1023=27:0;1026=qae@106,1027=qaf@106:0:32

Aug 22 05:55:54 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:56:15 localhost vdr: [1451] changing pids of channel 86 (Discovery Channel) from 3327+3327=27:3328=deu@3,3329=eng@3:0:0 to 3327+3327=27:3328=deu@3:0:0

Aug 22 05:56:15 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:56:15 localhost vdr: [1451] changing pids of channel 133 (Sky Cinema Family) from 4095+4095=27:4096=deu@3,4097=eng@3;4099=deu@106:0:0 to 4095+4095=27:4096=deu@3,4097=eng@3:0:0

Aug 22 05:56:15 localhost vdr: [1451] changing pids of channel 135 (Sky Cinema Nostalgie) from 767+767=27:768=deu@3:0:0 to 767+767=27:768=deu@3,769=eng@3:0:0

Aug 22 05:56:20 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:56:29 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 05:56:36 localhost vdr: [1451] changing pids of channel 142 (Sky Cinema +24 HD) from 511+511=27:0;515=deu@106,516=eng@106:0:0 to 511+511=27:0;515=deu@106:0:0

Aug 22 05:56:36 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:57:06 localhost /usr/lib/snapd/snapd[1004]: snapmgr.go:504: DEBUG: Next refresh scheduled for 2017-08-22 14:14:23.268401218 +0200 CEST.

Aug 22 05:58:42 localhost vdr: [1451] changing pids of channel 145 (Sky Cinema Hits HD) from 767+767=27:0;771=deu@106:0:0 to 767+767=27:0;771=deu@106,772=eng@106:0:0

Aug 22 05:58:42 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 05:59:03 localhost vdr: [1451] changing pids of channel 115 (History HD) from 767+767=27:0;771=deu@106,772=eng@106:0:0 to 767+767=27:0;771=deu@106:0:0

Aug 22 05:59:03 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 06:00:10 localhost kernel: [11914.264509] [drm] Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-2"

Aug 22 06:06:44 localhost vdr: [1451] changing pids of channel 137 (Sky Arts HD) from 767+767=27:0;771=deu@106:0:0 to 767+767=27:0;771=deu@106,772=eng@106:0:0

Aug 22 06:06:45 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 06:06:52 localhost systemd[1]: Starting Daily apt upgrade and clean activities...

Aug 22 06:06:54 localhost systemd[1]: Started Daily apt upgrade and clean activities.

Aug 22 06:09:11 localhost vdr: [1451] changing pids of channel 147 (Sky Sport 2) from 1791+1791=27:1792=qae@3:0:32 to 1791+1791=27:1792=qae@3,1793=qaf@3:0:32

Aug 22 06:09:11 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 06:09:29 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 06:10:35 localhost vdr: [1451] changing pids of channel 160 (Sky Sport 1 HD) from 767+767=27:0;770=qae@106,771=qaf@106:0:32 to 767+767=27:0;770=qae@106,771=qaf@106,772=qtz@106:0:32

Aug 22 06:10:36 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 06:10:40 localhost vdr: [1455] channel 131 (Sky Cinema Comedy) event Di. 22.08.2017 06:15-08:05 'The Singing Detective' status 2

Aug 22 06:11:10 localhost vdr: [1455] channel 131 (Sky Cinema Comedy) event Di. 22.08.2017 06:15-08:05 'The Singing Detective' status 4

Aug 22 06:11:10 localhost vdr: [1455] changing pids of channel 131 (Sky Cinema Comedy) from 1023+1023=27:1024=deu@3;1027=deu@106:0:0 to 1023+1023=27:1024=deu@3,1025=@3;1027=deu@106:0:0

Aug 22 06:11:11 localhost vdr: [1578] VNSI: Requesting clients to reload channel list

Aug 22 06:11:11 localhost vdr: [1106] stopping recording due to modification of channel 131 (Sky Cinema Comedy)

Aug 22 06:11:11 localhost vdr: [2332] recording thread ended (pid=1106, tid=2332)

Aug 22 06:11:11 localhost vdr: [1106] CAM 1: unassigned from device 2

Aug 22 06:11:11 localhost vdr: [2311] device 2 TS buffer thread ended (pid=1106, tid=2311)

Aug 22 06:11:11 localhost vdr: [1106] buffer stats: 160552 (0%) used

Aug 22 06:11:11 localhost vdr: [1106] timer 1 (131 0442-0620 'Taxi') stop

Aug 22 06:11:11 localhost vdr: [1106] executing '/usr/lib/vdr/vdr-recordingaction after "/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec"'

Aug 22 06:11:11 localhost vdr: [2310] buffer stats: 90992 (1%) used

Aug 22 06:11:11 localhost vdr: [2310] device 2 receiver thread ended (pid=1106, tid=2310)

Aug 22 06:11:11 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom after recording /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 06:11:11 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R91.custom after recording /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 06:11:11 localhost vdr: [1106] CAM 1/1: reusing MTD CAM slot

Aug 22 06:11:11 localhost vdr: [1106] CAM 1: assigned to device 1

Aug 22 06:11:11 localhost vdr: [1106] switching device 1 to channel 131 S19.2E-133-3-8 (Sky Cinema Comedy)

Aug 22 06:11:11 localhost vdr: [2752] device 1 receiver thread started (pid=1106, tid=2752, prio=high)

Aug 22 06:11:11 localhost vdr: [1106] timer 1 (131 0442-0620 'Taxi') start

Aug 22 06:11:11 localhost vdr: [1106] Title: 'Taxi' Subtitle: 'Actionkomödie'

Aug 22 06:11:11 localhost vdr: [1106] executing '/usr/lib/vdr/vdr-recordingaction before "/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec"'

Aug 22 06:11:11 localhost vdr: [2754] device 1 TS buffer thread started (pid=1106, tid=2754, prio=high)

Aug 22 06:11:11 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom before recording /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 06:11:11 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R91.custom before recording /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 06:11:12 localhost vdr: [1106] record /home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec

Aug 22 06:11:12 localhost vdr: [1106] recording to '/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec/00002.ts'

Aug 22 06:11:12 localhost vdr: [2775] recording thread started (pid=1106, tid=2775, prio=high)

Aug 22 06:11:14 localhost vdr: [2775] executing '/usr/lib/vdr/vdr-recordingaction started "/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec"'

Aug 22 06:11:14 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom

Aug 22 06:11:14 localhost recordingaction: executing /usr/share/vdr/recording-hooks/R91.custom

Aug 22 06:22:30 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 06:25:01 localhost CRON[2857]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))

Aug 22 06:35:30 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 06:36:26 localhost vdr: [1582] SVDRP < 127.0.0.1:42222 client connection accepted

Aug 22 06:36:26 localhost vdr: [1582] SVDRP < 127.0.0.1:42222 server created

Aug 22 06:36:28 localhost vdr: [1582] SVDRP < 127.0.0.1:42222 connection closed

Aug 22 06:36:28 localhost vdr: [1582] SVDRP < 127.0.0.1:42222 server destroyed

Aug 22 06:48:31 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 07:01:31 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 07:14:32 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 07:17:01 localhost CRON[3071]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 07:27:32 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 07:30:01 localhost CRON[3143]: (root) CMD (test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null)

Aug 22 07:30:01 localhost systemd[1]: Started Run anacron jobs.

Aug 22 07:30:01 localhost anacron[3165]: Anacron 2.3 started on 2017-08-22

Aug 22 07:30:01 localhost anacron[3165]: Normal exit (0 jobs run)

Aug 22 07:36:28 localhost vdr: [1582] SVDRP < 127.0.0.1:42308 client connection accepted

Aug 22 07:36:28 localhost vdr: [1582] SVDRP < 127.0.0.1:42308 server created

Aug 22 07:36:30 localhost vdr: [1582] SVDRP < 127.0.0.1:42308 connection closed

Aug 22 07:36:30 localhost vdr: [1582] SVDRP < 127.0.0.1:42308 server destroyed

Aug 22 07:40:33 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 07:53:33 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 08:06:34 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 08:17:01 localhost CRON[3356]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 08:19:34 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 08:32:35 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 08:36:30 localhost vdr: [1582] SVDRP < 127.0.0.1:42390 client connection accepted

Aug 22 08:36:30 localhost vdr: [1582] SVDRP < 127.0.0.1:42390 server created

Aug 22 08:36:32 localhost vdr: [1582] SVDRP < 127.0.0.1:42390 connection closed

Aug 22 08:36:32 localhost vdr: [1582] SVDRP < 127.0.0.1:42390 server destroyed

Aug 22 08:45:35 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 08:58:36 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 09:11:36 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 09:17:01 localhost CRON[3627]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 09:24:36 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 09:36:32 localhost vdr: [1582] SVDRP < 127.0.0.1:42476 client connection accepted

Aug 22 09:36:32 localhost vdr: [1582] SVDRP < 127.0.0.1:42476 server created

Aug 22 09:36:34 localhost vdr: [1582] SVDRP < 127.0.0.1:42476 connection closed

Aug 22 09:36:34 localhost vdr: [1582] SVDRP < 127.0.0.1:42476 server destroyed

Aug 22 09:37:37 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 09:50:37 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 10:03:38 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 10:16:38 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 10:17:01 localhost CRON[3887]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 10:29:39 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 10:36:34 localhost vdr: [1582] SVDRP < 127.0.0.1:42562 client connection accepted

Aug 22 10:36:34 localhost vdr: [1582] SVDRP < 127.0.0.1:42562 server created

Aug 22 10:36:36 localhost vdr: [1582] SVDRP < 127.0.0.1:42562 connection closed

Aug 22 10:36:36 localhost vdr: [1582] SVDRP < 127.0.0.1:42562 server destroyed

Aug 22 10:42:39 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 10:55:40 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 11:08:40 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 11:17:01 localhost CRON[4148]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 11:21:41 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 11:34:41 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 11:47:42 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 11:47:56 localhost vdr: [1582] SVDRP < 127.0.0.1:42668 client connection accepted

Aug 22 11:47:56 localhost vdr: [1582] SVDRP < 127.0.0.1:42668 server created

Aug 22 11:47:58 localhost vdr: [1582] SVDRP < 127.0.0.1:42668 connection closed

Aug 22 11:47:58 localhost vdr: [1582] SVDRP < 127.0.0.1:42668 server destroyed

Aug 22 12:00:42 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 12:13:43 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 12:17:01 localhost CRON[4410]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 12:26:43 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 12:28:01 localhost CRON[4471]: (root) CMD (   test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond)

Aug 22 12:39:44 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 12:40:29 localhost dhclient[1203]: DHCPREQUEST of 192.168.178.12 on eth0 to 192.168.178.13 port 67 (xid=0x235dda3d)

Aug 22 12:40:29 localhost dhclient[1203]: DHCPACK of 192.168.178.12 from 192.168.178.13

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2674]   address 192.168.178.12

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2674]   plen 24 (255.255.255.0)

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2674]   gateway 192.168.178.1

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2674]   server identifier 192.168.178.13

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2674]   lease time 86400

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2675]   hostname 'Kodi-MC'

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2675]   nameserver '192.168.178.13'

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2675]   domain name 'internal'

Aug 22 12:40:29 localhost NetworkManager[991]: <info>  [1503398429.2675] dhcp4 (eth0): state changed bound -> bound

Aug 22 12:40:29 localhost dbus[927]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Aug 22 12:40:29 localhost systemd[1]: Starting Network Manager Script Dispatcher Service...

Aug 22 12:40:29 localhost dbus[927]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Aug 22 12:40:29 localhost systemd[1]: Started Network Manager Script Dispatcher Service.

Aug 22 12:40:29 localhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: new request (1 scripts)

Aug 22 12:40:29 localhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: start running ordered scripts...

Aug 22 12:40:29 localhost dhclient[1203]: bound to 192.168.178.12 -- renewal in 39072 seconds.

Aug 22 12:47:58 localhost vdr: [1582] SVDRP < 127.0.0.1:42754 client connection accepted

Aug 22 12:47:58 localhost vdr: [1582] SVDRP < 127.0.0.1:42754 server created

Aug 22 12:48:00 localhost vdr: [1582] SVDRP < 127.0.0.1:42754 connection closed

Aug 22 12:48:00 localhost vdr: [1582] SVDRP < 127.0.0.1:42754 server destroyed

Aug 22 12:52:44 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 13:05:45 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 13:09:16 localhost vdr: [2775] recording to '/home/kodi/Aufnahmen/Taxi/2017-08-22.04.42.131-0.rec/00003.ts'

Aug 22 13:11:46 localhost vdr: [1451] read incomplete section - len = 18, r = 846

Aug 22 13:17:01 localhost CRON[4682]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 13:18:45 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 13:22:59 localhost kernel: [38485.332345] perf interrupt took too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 50000

Aug 22 13:25:03 localhost vdr: [1451] read incomplete section - len = 419, r = 252

Aug 22 13:31:46 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 13:44:46 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 13:48:00 localhost vdr: [1582] SVDRP < 127.0.0.1:42832 client connection accepted

Aug 22 13:48:00 localhost vdr: [1582] SVDRP < 127.0.0.1:42832 server created

Aug 22 13:48:02 localhost vdr: [1582] SVDRP < 127.0.0.1:42832 connection closed

Aug 22 13:48:02 localhost vdr: [1582] SVDRP < 127.0.0.1:42832 server destroyed

Aug 22 13:57:47 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 14:10:47 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 14:17:01 localhost CRON[4945]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 14:17:07 localhost /usr/lib/snapd/snapd[1004]: snapmgr.go:422: No snaps to auto-refresh found

Aug 22 14:17:07 localhost snapd[1004]: 2017/08/22 14:17:07.000542 snapmgr.go:422: No snaps to auto-refresh found

Aug 22 14:22:06 localhost /usr/lib/snapd/snapd[1004]: snapmgr.go:504: DEBUG: Next refresh scheduled for 2017-08-22 19:56:49.657804097 +0200 CEST.

Aug 22 14:23:48 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 14:32:48 localhost vdr: [1455] read incomplete section - len = 811, r = 15

Aug 22 14:36:48 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 14:48:02 localhost vdr: [1582] SVDRP < 127.0.0.1:42920 client connection accepted

Aug 22 14:48:02 localhost vdr: [1582] SVDRP < 127.0.0.1:42920 server created

Aug 22 14:48:04 localhost vdr: [1582] SVDRP < 127.0.0.1:42920 connection closed

Aug 22 14:48:04 localhost vdr: [1582] SVDRP < 127.0.0.1:42920 server destroyed

Aug 22 14:49:49 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 14:59:54 localhost vdr: [1451] read incomplete section - len = 1778, r = 799

Aug 22 15:00:53 localhost vdr: [1455] read incomplete section - len = 718, r = 327

Aug 22 15:02:49 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 15:15:50 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 15:17:01 localhost CRON[5210]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 15:28:50 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 15:41:51 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 15:48:04 localhost vdr: [1582] SVDRP < 127.0.0.1:43002 client connection accepted

Aug 22 15:48:04 localhost vdr: [1582] SVDRP < 127.0.0.1:43002 server created

Aug 22 15:48:06 localhost vdr: [1582] SVDRP < 127.0.0.1:43002 connection closed

Aug 22 15:48:06 localhost vdr: [1582] SVDRP < 127.0.0.1:43002 server destroyed

Aug 22 15:54:51 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 16:07:52 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 16:17:01 localhost CRON[5466]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 16:20:52 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 16:27:55 localhost kernel: [49581.170447] [drm] Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-2"

Aug 22 16:29:43 localhost vdr: [1463] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.conf

Aug 22 16:29:43 localhost vdr: [1463] VNSI: Client with ID 6 connected: 127.0.0.1:37300

Aug 22 16:31:00 localhost systemd[1]: Started Session 59 of user kodi.

Aug 22 16:33:53 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 16:46:53 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 16:48:06 localhost vdr: [1582] SVDRP < 127.0.0.1:43126 client connection accepted

Aug 22 16:48:06 localhost vdr: [1582] SVDRP < 127.0.0.1:43126 server created

Aug 22 16:48:08 localhost vdr: [1582] SVDRP < 127.0.0.1:43126 connection closed

Aug 22 16:48:08 localhost vdr: [1582] SVDRP < 127.0.0.1:43126 server destroyed

Aug 22 16:59:54 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 17:12:54 localhost systemd[1]: Started CUPS Scheduler.

Aug 22 17:17:01 localhost CRON[5836]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Aug 22 17:17:29 localhost systemd[1]: Started Session 63 of user kodi.

↧

CA_PMT problem with VDR

August 29, 2017, 4:45 am

≫ Next: KODI, VDR and H.265 (5.1 Audio) and VNSI Plugin

≪ Previous: Timer based recoding doesn't terminate / kodi and vdr disconnect

I am using the latest version of VDR, vdr-plugin-dvbapi and VNSI. Everything works great with unencrypted channels. But when I try to zap to an encrypted channel I get the following log in VDR :

https://pastebin.com/FA68a5MJ

I asked the author of the vdr-plugin-dvbapi and he told me that the problem is in the following line :

"CA_PMT doesn't contain CA descriptors"

When I use TVHEADEND, it works : it connects to my OSCAM and succesfully decodes the stream. But the same OSCAM with VDR doesn't work. Actually this is not a problem of VDR/OSCAM connection. The problem is way before that : VDR has a problem decoding the CA_PMT stuff. The author of vdr-plugin-dvbapi that maybe the signal is bad. But I am using the same antenna in both cases (VDR and TVHEDEND), so this is not the problem.

Any idea please ?

↧

KODI, VDR and H.265 (5.1 Audio) and VNSI Plugin

August 31, 2017, 1:19 pm

≫ Next: "Unexpected error" when manually terminating a recording

≪ Previous: CA_PMT problem with VDR

I have the following setup: A small PC with VDR 2.3.8 as the server. As the client I tested a Vero4K and Linux Clients. On both clients with KODI 17.x (I tried several versions) there are dropouts in Sound when the Sound is 5.1. (Stereo sound works without problems).
This behaviour is found when playing Live TV or recordings from Live TV.
When I play the same over vlc, the sound is ok. So I think it's a problem with the plugin.
Has anyone experiences with this setup?

Thanks

Holger

↧

"Unexpected error" when manually terminating a recording

September 8, 2017, 5:49 pm

≫ Next: We need some options under vnsi client settings - Timeshift and Recording directory

≪ Previous: KODI, VDR and H.265 (5.1 Audio) and VNSI Plugin

I am experieicng a strange effect when starting/ending a recording by simply pushing the rec button on my remote while the channel is playing.
After the first press, the recording starts normally. After the second press, the recording stops but I am getting the "An unexpected error occured" message on the scrren.

In the kodi log I am seeing the below two errors.

Quote:02:34:06.544 T:140332280768256 ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 3 seconds
02:34:06.544 T:140332280768256 ERROR: PVR - DeleteTimer - addon 'VDR-Network-Streaming-Interface (VNSI) Server:127.0.0.1:34890' returned an error: unknown error

Except for the message and errors in the log everything seems to work fine.

I am using kodi 17.4 un Ubuntu 16,04.3 with vdr-2.3.8 and latest vniserver plugin from git repository.

Any advise?[/quote]

↧

We need some options under vnsi client settings - Timeshift and Recording directory

October 9, 2017, 12:31 am

≫ Next: No audio streams - Kodi 17.4 VNSI / VDR backend on Ubuntu 16.04

≪ Previous: "Unexpected error" when manually terminating a recording

Hello @FernetMenta

we need more configurable options under the vnsi client settings.

[Image: 1JWWQoC.png]

The users ask for these settings in different forums.

Here I described what I mean: https://forum.kodi.tv/showthread.php?tid...pid2631858

Is it possible to get some options to configure the timeshift and the recording directory?

1. Timeshift Mode - Off / RAM / HDD

If I choose "RAM" or "HDD" it should be possible to configure these settings:

1a. Timeshift Buffer Directory - option to configure the specific path at the server
1b. Timeshift Buffer File Size for this vdr client - option to configure the file size in kb, mb or gb

These settings have to be written to "/var/lib/vdr/setup.conf" of the vdr server.

2. Recording Directory - option to configure the specific path at the server or maybe at the local machine if the local machine is the vdr server

This setting has to be written to "/etc/vdr/conf.d/00-vdr.conf" of the vdr server.

At least these are the settings vor latest stable vdr 2.2.0. I don't know if the path' changed with vdr 2.3.x.

3. Path to channel icons

I don't know if the setting under vnsi client settings somehow works. I only use the way under kodi.

[Image: FCELEmH.png]

If it doesn't work, the option could be removed.

What do you think about this?

Thanks and Greetings Hoppel

↧

No audio streams - Kodi 17.4 VNSI / VDR backend on Ubuntu 16.04

October 14, 2017, 4:26 am

≫ Next: Send notification to addon when recordings starts/ends

≪ Previous: We need some options under vnsi client settings - Timeshift and Recording directory

Kodi Endpoints:
Asus CBOX LE8.1.2 (kodi 17.4) / also tested on LE8.0.2 - passtrought audio
RPI3 LE8.1.2

DVB-T2 stick: Mygica T230C usb (Silicon Labs Si2168)
Ubuntu: 16.04 LTS
Kernel: 4.13.6-041306-generic (manually upgraded to support Mygica t230c usb stick)
Backend versions and the issue:
VDR 2.2.0/VNSI from main ubuntu repo - DVB-T channels are streamable and audio is working / T2 channels are not streamable from Kodi
VDR 2.2.0/VNSI from ppa:yavdr/unstable-vdr - DVB-T channels are streamable - no audio streams / T2 channels are not streamable from Kodi
VDR 2.3.1/VNSI 1.5.1 from ppa:aap/vdr - DVB-T channels are streamable - no audio streams / T2 channels are streamable but no audio streams except 1 channel with Dolby-digital 5.1 audio
VDR 2.3.8 from seahawk1986-hotmail/vdr-2.3.8 - vdr running without vnsi-server plugin - didn't investigate.

Other tests:
scanning with w_scan into vlc playlist - audio working with all channels (just to verify that the usb stick isn't faulty)

Logs:
rpi3 kodi debug
https://pastebin.com/d8XCkQp5

vdr log (sudo vdr -l 3 -P"vnsiserver -p 34890")
https://pastebin.com/jGiuNKtq

im open to any suggestions, any version of vdr/vnsi server

↧

Send notification to addon when recordings starts/ends

October 15, 2017, 5:54 am

≫ Next: vdr xmltv

≪ Previous: No audio streams - Kodi 17.4 VNSI / VDR backend on Ubuntu 16.04

I am currently working on a small programm to switch a LED connected to a seral header on my motherboard on or off depending on the current recording state. My first idea was to make use of the recording-hooks of VDR which provides an easy method to detect if a recording has begun or ended.

Then I thought it would be nice to extend the use case and create an addon which uses JSON-RPC API to query kodi if a recording is currently active. However, the query must be repeated with an appropriately small time interval to react shortly after a state change has occcured. Thus, I was looking for a method to watch out for an active notification if a recording has started/ended which can be received via xbmc.Monitor - yet to no avail so far.

Anyone has an idea how to achieve this or is the JSON RPC query the only possible way?

↧

vdr xmltv

October 29, 2017, 7:40 am

≫ Next: Openelec: Nothing works anymore

≪ Previous: Send notification to addon when recordings starts/ends

Hi Fernetmenta,

Since a few time, my epg doesnt work anymore with my vdr system. I m pretty sure i didnt change anything and i just spent a few hours trying to make it work again, without success... no error in the log, nothing.
Since it has broken, i have used streamdev + iptvsimple plugin which provides an easy way to get epg inside kodi with xmltv.
As a side effect, i cant record channel anymore with the iptvsimple plugin... well nothing is perfect, you"ll tell me ^^.

I wonder if it would be possible to get the xmltv logic from iptvsimple inside vdnsi plugin ?

Bibi

↧

Openelec: Nothing works anymore

November 8, 2017, 9:59 am

≫ Next: Cannot create a timer rule for 'any channel'

≪ Previous: vdr xmltv

Hey,

I managed to install Kodibuntu on a Raspberry Pi 2 and got it to work as PVR and player for videos on my NAS. Since a few days, nothing works any more. I am sorry for this description, but that is, what it looks like. When I plug the Raspberry in, it starts to boot, shows the Openelec-Icon, and then it stops doing nothing any more. Any idea, what I can do?

Thanx,

Joker

↧

Cannot create a timer rule for 'any channel'

November 23, 2017, 2:28 pm

≫ Next: Trouble with recordings list when starting Kodi box

≪ Previous: Openelec: Nothing works anymore

One of my favorite movies is randomly re-aired on various channels. I've never ever actually managed to schedule a recording in advance. Hence, I was going to create a timer rule for this movie title to be searched in epg and with channel 'any channel'. Unfortunately this does not create a timer rule - unless I specify a discrete channel.

Not sure if this a genral kodi issue or just an issue with vdr/vnsi. I am using KODI 17.6 on Ubuntu 16.04.3

I'd be happy for any suggestion on how to work around this issue or - even better - if this could be fixed in the upcoming KODI 18 releases.

↧

Trouble with recordings list when starting Kodi box

November 30, 2017, 2:24 am

≫ Next: Raspberry Kodi as TV backend (server) and Windows Kodi as TV frontend (client)

≪ Previous: Cannot create a timer rule for 'any channel'

Hello,

I have trouble with the recordings list when starting my Kodi box. It is just empty. I need to restart Kodi, then it appears - most of the times.

My setup: yaVDR newest version based on Ubuntu trusty (VDR 2.2.0, vdr-plugin-vnsiserver 2:1.5.2+git20171022-17-63d8151-0yavdr0~trusty), Kodi 17.3 on LibreELEC 8.0.2 x86_64, VDR VNSI Client 2.6.23.1.

The hard drive for the recordings goes into sleep after some time and I think that this might be related with the problem. I noticed the following log lines on LibreELEC:

Code:
11:07.296 T:139790364763904   ERROR: AddOnLog: VDR VNSI Client: Login - failed to read greeting from server

11:08.298 T:139790364763904  NOTICE: AddOnLog: VDR VNSI Client: Logged in at '1512033057+3600' to 'VDR-Network-Streaming-Interface (VNSI) Server' Version: '1.5.2' with protocol version '12'

11:17.146 T:139791981602560   ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 10 seconds

11:17.146 T:139791981602560   ERROR: AddOnLog: VDR VNSI Client: SupportChannelScan - Can't get response packed

11:30.003 T:139790624212736   ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 10 seconds

11:30.003 T:139790624212736   ERROR: AddOnLog: VDR VNSI Client: GetRecordingsList - Can't get response packed

11:30.003 T:139790624212736   ERROR: PVR - GetRecordings - addon 'VDR-Network-Streaming-Interface (VNSI) Server:172.27.0.20:34890' returned an error: unknown error

I already changed the timeout of the VNSI Client from 3 to 10 seconds (which should be enough time for the hard drive to wake up) but it did not help. Should I even put the timeout to more than 10 seconds?

Any more ideas?

On the VDR I noticed this:

Code:
Nov 29 22:51:07 yavdr vdr: [32376] VNSI: Requesting clients to reload recordings list

If I cannot solve this issue on the client side, is it possible to send this request to the clients after they connect. Lets say 30 seconds after they connect?

Cheers,
Roi

↧

Raspberry Kodi as TV backend (server) and Windows Kodi as TV frontend (client)

December 4, 2017, 11:35 pm

≫ Next: automatic shutdown despite active client connection

≪ Previous: Trouble with recordings list when starting Kodi box

Hi

I downloaded the latest Kodi yesterday and installed it on my Raspberry. With a USB DVB-T TV tuner. Am using VDR as the backend service and VDR/VNSI as the front end. It works well.

However on my Windows PC with Kodi I want to be able to access the Raspberry TV tuner service simply by also using the VDR/VNSI client - getting the source off the Raspberry. Is this not possible?

I used to do this with TVHeadEnd but it does not seem to be available with Kodi 17.

Anyone with any ideas? (How do I access the log and paste it here?)

Thanks!

↧

automatic shutdown despite active client connection

December 21, 2017, 1:40 am

≫ Next: VDR + 2x diseqc hotbird 13 and astra 19.2

≪ Previous: Raspberry Kodi as TV backend (server) and Windows Kodi as TV frontend (client)

I'm using a HTPC running libreelec 8.2.1 with vdr backend. I'm watching TV via a raspberry3 with vnsi. Everything is working just fine. Now I tried to enable power saving and configured the server to shut down after 15 minutes of inactivity. The server will happily wake up for planned recordings and the client will wake up the server as well via WOL. But if the server is idle and I'm watching TV from the raspberry, the server still will shutdown after 15 minutes (it does not matter whether I'm watching live TV or some recording). There must be some mechanism for vdr to tell kodi to NOT shut down as recordings during absence are working just fine. But this mechanism seems to be missing for remote clients. Does anybody know how vdr is telling kodi that it is active and that the system should not be shut down automatically?

↧

VDR + 2x diseqc hotbird 13 and astra 19.2

December 24, 2017, 7:42 am

≫ Next: VDR on LibreELEC with Wetek play2

≪ Previous: automatic shutdown despite active client connection

Hello

This is my satellite installationtuner 1 -- diseqc1 A/A - twin LNB1 (hotbird 13E)
+- diseqc1 A/B - twin LNB2 (astra 19.2E)

tuner 2 -- diseqc2 A/A - twin LNB1 (hotbird 13E)
+- diseqc2 A/B - twin LNB2 (astra 19.2E)

I added such an entry in diseqc.conf:

S13E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t
S13E 99999 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T
S13E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t
S13E 99999 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T

S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t
S19.2E 99999 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T
S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t
S19.2E 99999 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T
setup.conf

DiSEqC = 1

It does not work for me. Can someone say how to set it well?

↧

VDR on LibreELEC with Wetek play2

December 25, 2017, 11:34 pm

≫ Next: ERROR: SQL: [TV29] Successful result

≪ Previous: VDR + 2x diseqc hotbird 13 and astra 19.2

Please point out any guide, How I setup VDR on Wetek Play2 running on official LibreELEC

↧