Posts by Rene

  • [ANNOUNCE] xmltv4VDR 0.4.3 - 0.4.11

    Hi,

    I will send you a link to the logfile

    When i clear all settings, 0x0 get's saved correctly in the config file. When i change the setting to "use only ext. epg events", it changes it correctly to the selected channel. Copy to all, updates this setting to all channels: Works as it should. I can't reproduce the 0x100000000000, but if i figure out that, then i inform you about it.

    I did a manual "start import" for the myepgdata with all channels, but that resulted in about 350 entries in the syslog. When i do the same with the channels spread out on individual configs, all get's imported. So probably something when looping over to the next channel?

    What i meant with the sorting of channels, this was the main setup view.

    The content cannot be displayed because you do not have authorisation to view this content.


    Would be easier to find aroud with the list sorted numerically

    Or maybe we could use the name from the xmltv-config file, which would be easier to find around in the list of channels.

    Code
    file;00:00;0;0
60
1.iltapulu.fi;Yle TV1
2.iltapulu.fi;Yle TV2
3.iltapulu.fi;MTV3
4.iltapulu.fi;Nelonen

  • [ANNOUNCE] xmltv4VDR 0.4.3 - 0.4.11

    It is possible that i did not hit ok, and got that row after a reset. You could maybe add a "ok saves" button? :)


    I did now a more throughout test. I have for each channel a separate configuration, all with the same config (0x100000004900). This approach imported for all channels more or less everything. With one single config, it imports just less than one week worth of data.. The single config setup also misses for some channels the epg

    ps. could you btw change the way the channel-list is sorten: alpha-numeric. Now it's as text, so it sorts like 1, 10, 106, 11, 13, 2 etc instead of 1,2,3,4,5,6

  • [ANNOUNCE] xmltv4VDR 0.4.3 - 0.4.11

    Quote from FireFly

    Hi, you are telling to use only ext. EPG events but not which fields 0x100000000000. You should select in the menu for each channel at least title, shorttext and description to be imported into VDR.
    The easiest way to do this for all channels is to select the desired fields for one channel and copy them to all other channels with the blue button (which is only available while the cursor is on one of the EPG source options like 'title')

    The 3 fields are grayd out with the text "Always", so i can't change these.

    I tried one other approach. I created one config for one channel with data till 26.8. This was imported properly. I wonder now that could there be some kind of limitation in how mych data is processed? The original xml-file with 20 channels, and 14-50 days of xmltv-data per channel is about 6,5 mb large.

  • [ANNOUNCE] xmltv4VDR 0.4.3 - 0.4.11

    Hi!

    I have trouble configuring the plugin, and i think i have probably missed some basic settings. I pull max data with tv_grab_fi, and eg one channel has programmes with start="20260822203000". The problem is that this is not saved into vdr, Instead i get data for about one week, and some channels do end up empty. My EPG source looks like this

    Code
    file;00:00;0;0
60
1.iltapulu.fi;Yle TV1
2.iltapulu.fi;Yle TV2
3.iltapulu.fi;MTV3
..
..
etc

    my xmltv4vdr.conf looks like this

    Code
    channel.1.iltapulu.fi = myepgdata;0x100000004900;C-42249-101-1501
channel.2.iltapulu.fi = myepgdata;0x100000000000;C-42249-101-1502
channel.3.iltapulu.fi = myepgdata;0x100000000000;C-42249-101-3291

    which is ext. EPG events -> use only ext. EPG events

    The log looks like this when doing a manual import

    But the xml-file has a bit more entrys

    Code
    # xmllint --xpath 'count(/tv/programme)' myepgdata.xmltv
14106


    I wonder what could be limiting the import?

  • softhddevcie artifact smudge

    Ah, i have missed the noble-main part. That did though not give any big changes to what i had til now installed.

    I have to have to check out the ansible scripts. I have not realized that this project existed :) In work i use puppet, but for this kind of configurations, ansible is a great tool! :)

  • softhddevcie artifact smudge

    I did some more testing

    -v vdpau + -w use-possible-defect-frames get's stuck for a bit when playing through the cut + pixelschmudge
    -v vdpau without use-possible-defect-frames gives a smooth play, but with pixelsmudge

    I can't get the switches to work. A restart of the whole linux server fixes it, but only for the first start. Second restart of vdr, and I'm back again with a blank screen til nex reboot..

    Is it btw normal that restarting the VDR process takes up to 1-2 minutes? Killing the process with kill -9, and starting it again takes only 15-20 sec..

  • softhddevcie artifact smudge

    Heh.. I have been using my vdr so long with barely no updates for over 13 years until last summer when i got myself the GT 1030, and all worked basically straight with my previous settings, so did not check if any swithced had to be updated.

    I tested with -v cuvid, and there was no artifact smudge at all, but after second resart of vdr, i just got a black screen with sound. The other options had the same thing. just sound, no picture. Jumping back to vdpau got my picture back, and the artifacts.. Pobably some setting messed up..

    What are the differences between cuvid and nvdec? What does the egl do?

  • softhddevcie artifact smudge

    Hi,

    The cutting of recordings seems to work better, and the artifact smudge that comes when viewing over the cut is less, but still there. Jumping into the cutmark, and starting to watch from here gives a flawless image, but watching "over the cut" gives still some artifacts. Is there something I could do to help debugging this?

    The content cannot be displayed because you do not have authorisation to view this content.

  • VDR version 2.7.9 freigegeben

    Here is an example how i get the pixelschmudge after cutting. This occurs when watching "over the cut mark", but if i jump tino the cutmark with 7 or 9, the picture clear is as it should be

    The content cannot be displayed because you do not have authorisation to view this content.

  • VDR 2.7.9: Cutting clean HD recording generates tons of errors

    Hi,

    I have a strange problem when cutting clean hdtv recordings with the latest 2 or 3 release versions of vdr. I have recordings without errors (according to VDR Live status of a recording), but when i cut them, i get a ton of errors. One example is a clean 1920x1080 dvb-c recording that after cutting gets 32304 errors and cutting points are getting artifacts. I do not see any errors in the lots either.

    This has actually got worse since i switched from SD to HDTV last autumn (finland swithced from sd to hd last year).

    Does anyone know why this happens?

  • Monitoring if vdr is runninng

    I was planning for a oneliner in cron

    Code
    [[ $(/usr/bin/svdrpsend ping |grep 'is alive' |wc -l) -ne 1 ]] && service vdr restart

    I'm not familiar with mapfile, so i try to stick to grep. When i noticed that vdr hanged, i forgot svdrpsend.. If it ever happens again, i'll check what svdrpsend is returning..