Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27

Thread: Recordings Failing with "No Errors but no Data Delivered" message

  1. #21
    Join Date
    Jun 2015
    Location
    Dutchess County, NY USA
    Posts
    161

    New Information

    I've got some new informatiom about my zero-length problem.

    Many hours of testing has shown the following, on my machine at least:
    - A port(36312-36323) that has had a recording stopped for any reason is never released for re-use. If I try to watch live TV on such a port, I get no video or audio. Escape key exits live TV back to menu.
    - If I stop watching live TV using the escape key. the port is released about 60 seconds later.
    - As shown below, ports 36313, 36314, 36317 and 36320 will produce no video when it's "their turn" to be used.
    - Restarting the recorder service results in errors for port 8968. Un-released ports are released but no further tuner access is possible.
    - System must be rebooted to return to normal operation.

    I can do this every time.

    Logs attached.

    Any help?

    Name:  NextPVR-PortStatus-170526.jpg
Views: 28
Size:  120.8 KB
    Attached Files Attached Files
    Later...JohnC

    System Status: Humming
    Desktop: Intel DX38BT MB - Intel Q9650 3GHz Quad - AMD HD6670 Video
    Software: Win 10 Pro(Creators) - NextPVR - WinTV8 - Total Media Extreme - VLC
    Video: Verizon FiOS - Hauppauge DCR-3250 - Hauppauge HDPVR

  2. #22
    Join Date
    Jun 2015
    Location
    Dutchess County, NY USA
    Posts
    161
    Additional testing verified that a scheduled recording that gets assigned to an un-released port will produce a zero-length file without error.

    I can now "manage" this problem by tracking when all ports a stuck. Then reboot the system.

    Hopefully, a fix can be found.
    Later...JohnC

    System Status: Humming
    Desktop: Intel DX38BT MB - Intel Q9650 3GHz Quad - AMD HD6670 Video
    Software: Win 10 Pro(Creators) - NextPVR - WinTV8 - Total Media Extreme - VLC
    Video: Verizon FiOS - Hauppauge DCR-3250 - Hauppauge HDPVR

  3. #23
    Join Date
    May 2006
    Location
    Canada
    Posts
    25,400
    Have you tried disabling your parallel processing file? https://forums.nextpvr.com/showthrea...791#post514791 I do not really like your method as I feel the /k might leave a thread open.

    Martin

  4. #24
    Join Date
    Jun 2015
    Location
    Dutchess County, NY USA
    Posts
    161
    Problem solved.

    A great call, Martin! I disabled ParallelProcessing.bat as suggested and the ports used for recording are being released for re-use. It also cured that nasty message when I tried to re-start the recording service.

    Now I'm back to my original problem. NextEnd.exe is not getting started when a recording starts or, if it is being started, I can find no evidence that it did. NextEnd.log is not created or updated. NextEnd.exe will run if started from the command line in a command window.

    Can you explain the exact mechanism that NextPVR uses to start the batch file?

    Thanks for your great help.
    Later...JohnC

    System Status: Humming
    Desktop: Intel DX38BT MB - Intel Q9650 3GHz Quad - AMD HD6670 Video
    Software: Win 10 Pro(Creators) - NextPVR - WinTV8 - Total Media Extreme - VLC
    Video: Verizon FiOS - Hauppauge DCR-3250 - Hauppauge HDPVR

  5. #25
    Join Date
    Dec 2005
    Location
    UK
    Posts
    2,378
    Quote Originally Posted by jcole998 View Post
    Can you explain the exact mechanism that NextPVR uses to start the batch file?
    This is probably not exact ... but should be close.

    Firstly ... some context. I can start a Command Prompt. The Command Prompt window will be in my user folder c:\Users\Graham. I can type the command "fabsplat" that contains the command ... notepad bolost.txt ... The command processor will expect the bolost.txt file to be in the current folder ... i.e. c:\Users\Graham

    NextPVR batch files run in the context of the system user account so they are "in" a folder that might be c:\Windows or C:\Windows\System (or whatever). All file references need to be specified in full. Not bolost.txt but c:\Users\Graham\bolost.txt

    The parallelprocessing batch file starts at the same time that the NextPVR Recording Service starts recording the show.

    Thought for the day ... Have you tried a "sleep" command at the top of the batch file to give NextPVR a minute or so to get its act together before the batch file proper starts?

    Edit: Apologies if, as I suspect, I am teaching you to suck eggs.
    AMD A75, 4 Gig, 1000 Gig, Nvidia N210
    1 x Hauppauge WinTV QuadHD DVB-T2
    1 x TBS 6281 dual DVB-T2
    2 x Hauppauge Nova-t PCI

  6. #26
    Join Date
    Jun 2015
    Location
    Dutchess County, NY USA
    Posts
    161
    Nah, no worries, Graham. This stuff ain't rocket science but it can drive one nuts! I'm an old-time programmer and one of my best mantras was "Hack it 'til it wiggles." I shall persevere.

    I'll try your suggestion and see what happens.

    Thanks for your help.
    Later...JohnC

    System Status: Humming
    Desktop: Intel DX38BT MB - Intel Q9650 3GHz Quad - AMD HD6670 Video
    Software: Win 10 Pro(Creators) - NextPVR - WinTV8 - Total Media Extreme - VLC
    Video: Verizon FiOS - Hauppauge DCR-3250 - Hauppauge HDPVR

  7. #27
    Join Date
    Jun 2015
    Location
    Dutchess County, NY USA
    Posts
    161
    No go on the delay. I used "ping 127.0.0.1 -n 6 > nul" to delay 5 seconds.

    I'm hoping sub will pick up on this and add a leeeetle more logging.

    Thanks again for the help.
    Later...JohnC

    System Status: Humming
    Desktop: Intel DX38BT MB - Intel Q9650 3GHz Quad - AMD HD6670 Video
    Software: Win 10 Pro(Creators) - NextPVR - WinTV8 - Total Media Extreme - VLC
    Video: Verizon FiOS - Hauppauge DCR-3250 - Hauppauge HDPVR

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •