Only with FX

Discussion in 'DIRECTV HD DVR/Receiver Discussion' started by toobs, Apr 9, 2014.

  1. Jul 3, 2015 #81 of 164
    pappasbike

    pappasbike Godfather

    573
    6
    Sep 19, 2006
    To be honest it didn't occur to me that the "watch from the beginning" was an internet connection feature. If I disconnect the box I would also disconnect the 22 and apparently wouldn't have the feature available on either. Recording the episode would not then recreate the issue.

    If the two issues are related then what may be happening with the F/X and other networks is that for some reason the genies are being triggered to begin recording early thus cutting off early. And of course the broadcasters aren't helping with all this scheduling of 1,2,3 or 5 minutes longer than an hour broadcast. But for some reason my non genies don't get flummoxed by this while both my genies always do.

    When I had my 34 at that time I had an HR 21. The early cut off only happened on the 34. I don't know if that "watch from the beginning" feature was enabled back then. Both machines were subsequently replaced with the 44 and 22 respectively and the issues continued in an identical manner along with the addition of watch from the beginning. I no longer bother with that feature because I got burned so many times when I had gotten into a movie or other program and really wanted to see the end of it. If it cut off part of the beginning I wouldn't be so annoyed but cutting off the end of something I'm really into - *##**#*##!!
     
  2. Jul 3, 2015 #82 of 164
    TomCat

    TomCat Broadcast Engineer

    4,153
    101
    Aug 31, 2002
    You might be on to something here.

    Not only is data being downloaded constantly, it is being indexed constantly. That is a process that creates a new single data point from the 13 or so different data points regarding the air time/show title/length of any episode. It does this so that accessing that data on the fly (such as when you ask the guide to display a time and date grid for a group of channels for a particular 90 minutes) can happen quicker, for one thing. It is a method of offloading CPU tasks into times when there are not a lot of commands so that when you do send a command it happens quickly. A large professional media database sometimes has an entire rack of servers just for indexing media, so that they can search it quickly once indexed.

    Its a powerful tool; Adobe PPCC has a plugin that can search 30,000 hours of recorded video/audio for a two-word phrase in a millisecond and display a list of every media clip containing that phrase, because indexing actually "listens" to every word via voice-to-text and keeps a record of where it is, ahead of time. So the NSA can also record billions of phone calls and their computers would instantly know every time you used the word "pipe" and "bomb" in the same sentence. Not that they would ever do that, of course.

    And it is a slow, relatively CPU-intensive background task competing for CPU cycles. So if a company like FX sends late updates through Tribune regarding start times or end times or even episode changes, that data can be in the pipeline for awhile, and if a consumer DVR is indexing 500 channels of data, it might not get through in time. FX may have an intern responsible for this that does it at the last minute, just like Comedy Central can't seem to update program info until the last minute.

    So if you buy that theory, one way to counteract this is to reduce the amount of indexing. Indexing is also done for the conflict resolution. If you have a lot of SLs, reducing that by deleting old ones might have the effect of reducing the CPU load. Conflict resolution is also exponential, so adding one SL can double the entire load, which means removing even a few can have a significant effect on reducing CPU load. This is also why we only get 50 SLs.

    When there is a guide data dump, the DVR then has to compare every program you have set an SL for against every program title in that data dump for every channel, looking for matches, and then create a plan for resolution if there are conflicts found. Over and over again. While folks think a new DVR is snappier because it has less content on the HDD, the real reason is because there are few or no SLs to constantly perform conflict resolution against 500 other channels on in the background, competing for CPU cycles on an underpowered CPU. You can prove this by deleting all SLs, and leaving all the content on the HDD. The result is a DVR that acts snappy. Or snappier.

    Might help, might not. But it also might explain why one DVR does this and another doesn't, based on how fast that particular CPU is, and on how many tasks it is juggling at any moment. A client-server DVR like a 44 has added CPU tasks that a 24 doesn't have, and a 24 has a faster CPU that a 22.

    And while this might be coincidental with the ads at the end, it is not likely causal. Two of the data points I was talking about are start time and end time in the time code track. Typically for an hour show that will be 00:00:00:00, and 01:00:00:00, or 00:59:59:29. The end time is what triggers the end of the recording, and what triggers the "do you want to delete?" screen on playback (as the DVR parses the metadata for TC in each decoded packet during playback).

    But the DVR knows nothing else other than what the current time code is telling it. It uses this to know where it is in the recording and playback, and on how to build the time-bar graphic, and on how to know how to skip 30 seconds (or more accurately, 60 GOPs).
     
  3. Jul 12, 2015 #83 of 164
    Laxguy

    Laxguy Honi Soit Qui Mal Y Pense.

    15,541
    617
    Dec 2, 2010
    Monterey...
    Thanks, TC. Makes a lot of sense, and gives me an extra reason to keep my SLs pruned at all times. I've never had a problem with shows terminating early. Usually I FF through the commercials, and "what's coming next week"then hit Delete. I don't watch much on FX, which I guess also helps.
     
  4. Jul 12, 2015 #84 of 164
    Blackloz

    Blackloz New Member

    62
    3
    Aug 23, 2011
    I've had this same issue and for safety's sake I set all my FX shows to record on my HR24 & Bell instead of the 44
     
  5. Jul 29, 2015 #85 of 164
    prushing

    prushing Active Member

    966
    34
    Feb 14, 2007
    Happened last night on Tyrant. Recording showed 1:12 minutes, but stopped right at 1:05. Not sure why FX can't update its guide sooner, but looking at next week, it shows 1 hour in the guide.
     
  6. Jul 29, 2015 #86 of 164
    toobs

    toobs Legend

    564
    15
    Oct 10, 2012
    The exact same thing happened to me also last night with Tyrant.
     
  7. Jul 29, 2015 #87 of 164
    Bill Broderick

    Bill Broderick Icon

    2,680
    254
    Aug 25, 2006
    Long Island
    I decided to avoid this problem by padding all FX recording by 15 minutes on the back end. Since most (but not all) of the FX programming that I watch is in the 10:00 block, this has not caused contention with any other recordings yet. I have not experienced the problem since making this modification (this includes last night's episode of Tyrant).
     
  8. Jul 29, 2015 #88 of 164
    gpg

    gpg Well-Known Member

    2,057
    51
    Aug 19, 2006
    Long Island
    My HR34 recorded last night's Tyrant episode in full. I have had an issue with FX recordings from time to time. It is puzzling about how randomly the problem occurs.
     
  9. Jul 31, 2015 #89 of 164
    coolman302003

    coolman302003 2014 NBA CHAMPIONS!

    1,813
    96
    Jun 2, 2008
    Southeast
    Just checked my recording and it did the same as well. HR44-700
     
  10. Aug 2, 2015 #90 of 164
    peds48

    peds48 Genius.

    20,073
    1,075
    Jan 10, 2008
    NY
    Just watched the last episode of Tyrant recorded on my HR44, I was able to watch completely.
     
  11. Aug 2, 2015 #91 of 164
    gpg

    gpg Well-Known Member

    2,057
    51
    Aug 19, 2006
    Long Island
    So it looks like a couple of us in the NY area got full recordings. I don't know where the three of you who reported the problem live, but I'm thinking that geography plays some role in the issue.
     
  12. Aug 4, 2015 #92 of 164
    prushing

    prushing Active Member

    966
    34
    Feb 14, 2007
    let's see if FX changes the runtime now, right now it is at 1:01 and is right in my guide, but when was the last time FX ran for only 1:01?
     
  13. Aug 5, 2015 #93 of 164
    toobs

    toobs Legend

    564
    15
    Oct 10, 2012
    I'm in California. I can't believe that this thread is ongoing. So far there is no solution.
     
  14. Aug 5, 2015 #94 of 164
    gpg

    gpg Well-Known Member

    2,057
    51
    Aug 19, 2006
    Long Island
    Last night's episode recorded completely agin here in the NYC area on my HR34. Let's see if there were problems elsewhere.
     
  15. Aug 5, 2015 #95 of 164
    gpg

    gpg Well-Known Member

    2,057
    51
    Aug 19, 2006
    Long Island
    Last night's episode recorded completely agin here in the NYC area on my HR34. Let's see if there were problems elsewhere.
     
  16. Aug 5, 2015 #96 of 164
    toobs

    toobs Legend

    564
    15
    Oct 10, 2012
    No problems with Tyrant last night and I'm in So Ca.
     
  17. Aug 5, 2015 #97 of 164
    prushing

    prushing Active Member

    966
    34
    Feb 14, 2007
    no problems, but looks like the guide data didn't change
     
  18. Aug 6, 2015 #98 of 164
    coolman302003

    coolman302003 2014 NBA CHAMPIONS!

    1,813
    96
    Jun 2, 2008
    Southeast
    No problems here either with Tyrant.
     
  19. Aug 9, 2015 #99 of 164
    toobs

    toobs Legend

    564
    15
    Oct 10, 2012
    Last week's Strain for me. The same crap.
     
  20. Aug 9, 2015 #100 of 164
    Blackloz

    Blackloz New Member

    62
    3
    Aug 23, 2011
    To play it safe I record all my FX shows on the HR24 and not the 44. It seems to work fine this way.
     

Share This Page

spam firewall

Advertisements