yavdr64 0.5.0-beta clean install - video stuttering

    I've just done a clean install of yavdr64 0.5.0-beta on my ATSC enabled box (basic cable, am in the USA) and am getting intermittent video stuttering. About every 5-10 seconds, the video pixelates severely, loses about 2-3 seconds and then catches up with itself. It looks like the signal has dropped for a few seconds. But, weird thing is, there are no messages at all in /var/log/syslog, dmesg or /var/log/Xorg.1.log.


    I've been running yavdr64 0.4.0 for about a year with no such problems. If I switch back to the 0.4.0 partition, there's no problems - so it doesn't appear to be hardware related.


    I've tried the following front-ends:
    vdr-sxfe@vdr-plugin-xineliboutput


    xine@vdr-plugin-xine


    vdr-plugin-softhddevice (experimental)


    but get the same experience each time.


    Any ideas??

    I guess your hardware meets the minimum criterias for yavdr ?


    Got a Vdpau capable Nvidia grafic card installed?


    Why stay with the original install and not perform an update to get the latest version ?


    Code
    sudo apt-get update
sudo apt-get dist-upgrade


    It almost sounds like your screen refreshrate could be the problem.
    Connect by browser to webinterface and select and appropriate refreshrate (i guess 60 Hz or 24 Hz should make it good for you in the US )


    If this does not help you pls provide log-files (syslog, dmesg).



    KR,
    Joe

    Sorry, forgot to mention. Yes I did do a 'apt-get update' and 'apt-get dist-upgrade', but this problem is still occurring.


    My VGA card is an NVIDIA GeForce 8400 GS - which worked with VDPAU on yavdr-0.4. I'm using a 19" VGA attached LCD monitor.




    02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS] (rev a2) (prog-if 00 [VGA controller])
    Subsystem: ZOTAC International (MCO) Ltd. Device 3158
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 18
    Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
    Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
    Region 3: Memory at da000000 (64-bit, prefetchable) [size=32M]
    Region 5: I/O ports at ec00 [size=128]
    [virtual] Expansion ROM at dfd80000 [disabled] [size=512K]
    Capabilities: [60] Power Management version 3
    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
    <snip>



    I think I am running 24Hz on the display screen:


    02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS] (rev a2) (prog-if 00 [VGA controller])
    Subsystem: ZOTAC International (MCO) Ltd. Device 3158
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 18
    Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
    Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
    Region 3: Memory at da000000 (64-bit, prefetchable) [size=32M]
    Region 5: I/O ports at ec00 [size=128]
    [virtual] Expansion ROM at dfd80000 [disabled] [size=512K]
    Capabilities: [60] Power Management version 3
    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)



    The video pixelation happens on all channels, HD and SD, and is also visible on the yavdr-remote as per the attached picture. It also happens when playing recorded video.


    Attached also are the syslog and dmesg files.


    One other, perhaps relevant, thing - I'm not seeing the OSD overlaid on live TV. When I hit "menu" the OSD opens on a black screen. When I close the OSD, live TV comes back.



    Any ideas?

    I would try to force a 60Hz rate - maybe this helps!


    The syslog has some kerrnel message related to your atsc card.


    You could try to update the kernel to 3.5 - that one should be available directly from ubuntu for precise.
    The other option you can try before updating the kernel would be to install the latest media build dvb drivers.


    Code
    sudo apt-get install linux-media-dkms


    is the grafics card well cooled ? New driver version sometimes run the card at higher frequency and generate more heat...


    I have no other idea but maybe one of the yavdr developers can help...


    joe

    Zitat von baxternz

    02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS] (rev a2) (prog-if 00 [VGA controller])


    Hehe, this line is strange. Chip typ GT218 is a Tesla 2nd Gen GPU (16 CUDA cores) used in GeForce G210, Quadro NVS 300 or ION2 devices. A Nvidia GeForce 8400GS has been based on a chip typ G98, a Tesla 1st Gen GPU (8 CUDA cores)


    Either of them should run with yaVDR. A GT218 even better, temporal as deinterlacing for all HD channels and temporal_spatial for SD channels. Depending on the design or overall implemention of the 8400GS it may be a good idea to step down a bit in these setting, so "Bob" for HD, "temporal" for SD. Wrong settings here could cause stuttering video. Could you please do a:


    Code
    #/> sudo update-pciids


    And then please re-check the "lspci" output? What does "/var/log/Xorg.1.log" say, what Nvidia graphics it does find?


    Looking to your "syslog" the VDR seems also to struggle with the DVB devices:


    Code
    ...Apr 15 07:45:54 ubuntu vdr: [1656] frontend 0/0 lost lock on channel 2, tp 711Apr 15 07:45:54 ubuntu vdr: [1656] frontend 0/0 regained lock on channel 2, tp 711Apr 15 07:46:12 ubuntu vdr: [1656] frontend 0/0 lost lock on channel 2, tp 711Apr 15 07:46:12 ubuntu vdr: [1656] frontend 0/0 regained lock on channel 2, tp 711Apr 15 07:46:41 ubuntu vdr: [1656] frontend 0/0 lost lock on channel 2, tp 711Apr 15 07:46:41 ubuntu vdr: [1656] frontend 0/0 regained lock on channel 2, tp 711Apr 15 07:47:11 ubuntu vdr: [1656] frontend 0/0 lost lock on channel 2, tp 711Apr 15 07:47:11 ubuntu vdr: [1656] frontend 0/0 regained lock on channel 2, tp 711...


    This seems to be a valid cause for your problems, connection or driver issues. Did you install any additional driver package with [0.4]? v4l-dkms, linux-media-dkms ... ?


    Regards
    fnu

    HowTo: APT pinning

    2 Mal editiert, zuletzt von fnu ()

    OK, did as instructed:


    root@ubuntu:~# update-pciids
    Downloaded daily snapshot dated 2013-04-04 03:15:01
    root@ubuntu:~# lspci
    00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
    00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
    00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
    00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
    00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
    00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
    00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
    00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
    00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
    00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
    00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
    00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
    00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
    00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
    00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
    00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
    00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
    00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
    00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
    00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
    02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2)
    02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
    03:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04)


    no change - still problems front-end locking, and video quality on yavdr-0.5-beta.


    I did install "linux-media-dkms", as per the previous recommendation, but was having problems before that and still am after. In fact now, I can't seem to lock onto any channel or see any live video (as per the attached syslog).


    Running FEMON from the OSD, I'm getting a signal up in the green (am ATSB cable connected, not aerial), but it drops down to the red every 3-5 seconds. But, now, no live video at all.

    Zitat von baxternz

    no change - still problems front-end locking, and video quality on yavdr-0.5-beta.


    Well that is IMHO one problem, your receivers don't lock to any frequency and therefore the video does stutter. That is what you also describe from "femon" view, tune to frequency with any signal level, green, don't get lock, dropping down to red ...


    No rocket science on the graphics card, despite the fact I'm struggeling with the information of the typ, even the X Nvidia driver does find:


    Code
    [    15.747] (II) NVIDIA dlloader X Driver  304.88  Wed Mar 27 14:28:14 PDT 2013
[    15.747] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs 
...
[    16.385] (II) NVIDIA(0): NVIDIA GPU GeForce 8400GS (GT218) at PCI:2:0:0 (GPU-0)


    Interessting, haven't seen this before ... but as I already said, either should work, and Xorg.1.log does look like there is no issue here.


    I don't see messages regarding the used output frontend in syslog. What frontend have you configured with yaVDR WFE?


    Regards
    fnu

    HowTo: APT pinning

    3 Mal editiert, zuletzt von fnu ()

    Something else has gone wrong now - I can't get any of the front-ends to connect - and can't even get the OSD up.


    I've tried all combinations of front-ends in the WFE. All I get is a little arrow in the screen!


    VDR back-end is still working - I can telnet to port 6419.


    Maybe openbox has broken?


    [PS. thanks for the help troubleshooting this. I used a custom VDR install for years on Fedora - still working out how to navigate ubuntu and yavdr somewhat!]

    baxternz


    Ok, at least vdr-sxfe or xine should show a "No signal" picture, softhddevice doesn't start if there is no video stream. Since you may still not receive any ATSC (?) signal, this will prevent the start of VDR with softhdddevice as frontend.


    So, I would still assume your main problem is the missing signal, which cause the other issues. Until you get a stable video signal, vdr-sxfe or xine should be the output frontends, because they do start w/o any video stream from DVB/ATSC.


    Regarding frontend, we may check the "/var/log/upstart/vdr-frontend.log", hopefully I do have that right in my mind ... :)


    Regarding TV signal, from where did you get the channels.conf entries? From the former yaVDR 0.4 installation? Did you use that a longer time? How did the receivers look like there, e.g. in syslog? I ask to get some more information, because it's not possible to test ATSC devices for me ... 8o


    Regards
    fnu

    HowTo: APT pinning

    Einmal editiert, zuletzt von fnu ()

    Hi,


    Zitat von baxternz

    I did install "linux-media-dkms", as per the previous recommendation, but was having problems before that and still am after. In fact now, I can't seem to lock onto any channel or see any live video (as per the attached syslog).


    Maybe you should "sudo apt-get remove linux-media-dkms" if it worked better before.
    Can you replay a recording from your 0.4.0 installation, which is known to be good? If that works we know that the output is working and it's a problem on the receiving side.


    Lars.

    Yes, the channels.conf was copied from 0.4, and still works 100% in that version


    At this stage, It's not even opening the display:
    Can't open display :1.1


    I've attached some logs from the same machine 0.4 and 0.5 - what's going on?!??

    In the syslog from yavdr 0.5 this line does not look good from my understanding:


    Code
    lgdt3305_read_status: error -22 on line 943


    This is the dvb driver having a problem to get carrier, signal, viterby or sync


    Is the


    And 0.4 is still working without problems?


    Your card is a WinTV-HVR1270 ?


    BR,
    Joe

    Yes - 0.4 works fine no problems on the same hardware.


    My card is a WinTV-HVR-1250 running on Comcast cable with ATSC.


    I have 2 problems with YAVDR 0.5-beta
    1) on a clean install, live TV was intermittently pixelating with what looked like dropped frames and the video "catching up". Same hardware - no such problems on YAVDR 0.4.
    2) in the process of troubleshooting this, I've somehow broken the display output - VDR backend is running, but I'm only getting a mouse arrow on the screen
    2a) Because of 2, I can't get any front-end to run (xine, xineliboutput, softdevice, etc)


    UPDATE: If I switch to XBMC as the output in the yavdr webinterface, XBMC runs - but still won't play live TV. Buffering stays at 0%.


    help! :rolleyes:

    I just have seen that you were the one having troubles with the atsc channel scan in 0.4 Getting yavdr-0.4 working with ATSC


    In that case I would reinstall 0.5 to be sure to start from clean system.
    And by the way there is no 0.5 beta anymore. It is stable since many month meanwhile :)
    Maybe downloading the final iso and checking the md5 hash before cd burning would be adviseable


    http://www.yavdr.org/download/


    perform the update + dist-upgrade, reboot and than


    Stop vdr and try a new channel scan:
    http://linuxtv.org/wiki/index.…es.2C_digital_cable_TV.29


    Maybe something has changed in the way the driver tunes the channels in newer kernels?


    BR,
    Joe

    OK - so something is completely wrong here.


    I re-installed, from scratch, yavdr-0.5-beta. First boot, I stopped VDR, ran an apt-get update/dist-upgrade and got the following error message from a CLEAN INSTALL:


    Errors were encountered while processing:
    /var/cache/apt/archives/vdr-plugin-dvbhddevice_2.0.1-0yavdr0~0.5~precise_amd64.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)


    If I try apt-get dist-upgrade again, I get:
    apt-get dist-upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    You might want to run 'apt-get -f install' to correct these.
    The following packages have unmet dependencies:
    vdr-plugin-dvbhddevice : Depends: vdr (= 1.7.27-5yavdr1~precise) but 2.0.1-0yavdr0~0.5~precise is installed
    E: Unmet dependencies. Try using -f.



    Any ideas?

    Zitat von DocViper

    And by the way there is no 0.5 beta anymore. It is stable since many month meanwhile :)
    Maybe downloading the final iso and checking the md5 hash before cd burning would be adviseable

    I am quoting myself.... :(


    Get the yavdr 0.5 final and install again from that cd.
    http://ftp5.gwdg.de/pub/linux/yavdr/yavdr64-0.5.0.iso


    The 0.5 beta is not recommended for installation!


    Otherwise troubleshooting is impossible.


    KR,
    Joe

    Can you tell me why you again install the beta?


    Gerald


    HP Proliant MicroServer Gen8, Xeon E3-1230, 12 GB RAM, 3xWD red 2TB im RAID 5, 2xSundtek MediaTV Home DVB-C/T, L4M TWIN-C/T, Ubuntu Server 14.04.1, Plex Media Server
    Samsung UE55H6470

    Well, this is my development box and I thought -beta was the latest. Looking back at the timestamps again now, looks like it's older!


    I was having video quality issues with 0.5.0 final - will reinstall that and report back.....!

    Zitat von baxternz

    Well, this is my development box and I thought -beta was the latest. Looking back at the timestamps again now, looks like it's older!


    Since when is a beta later than a non beta?


    Gerald


    HP Proliant MicroServer Gen8, Xeon E3-1230, 12 GB RAM, 3xWD red 2TB im RAID 5, 2xSundtek MediaTV Home DVB-C/T, L4M TWIN-C/T, Ubuntu Server 14.04.1, Plex Media Server
    Samsung UE55H6470

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden