1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

New program for 1 step TTG downloads, decryption, encoding - kmttg

Discussion in 'TiVo Home Media Features & TiVoToGo' started by moyekj, Mar 15, 2008.

  1. Oct 23, 2012 #4361 of 10412
    lrhorer

    lrhorer Active Member

    6,924
    0
    Aug 31, 2003
    San...
    Yes.
     
  2. Oct 23, 2012 #4362 of 10412
    lrhorer

    lrhorer Active Member

    6,924
    0
    Aug 31, 2003
    San...
    OK, I've had my fun beinhg a smart-ass for the day. The best answer is there are plenty of discussions on the board concerning coding for a TiVo.

    If you are strictly pulling videos, then the only supported formats are both MPEG-II coding: .mpg and .TiVo.

    If you are pushing videos, h.264 in a .mp4 containder with AAC (stereo only) or up to 5.1 AC3 audio at 384 Kbps is also supported. These are not only usually significantly smaller than MPEG-II files, they also transfer much, much faster with no transcoding.

    (Come to think of it, I've never tried to push a .TiVo file. I don't know whether it will work, or not.)
     
  3. Oct 23, 2012 #4363 of 10412
    Test

    Test Active Member

    3,725
    0
    Dec 8, 2004
    Thanks ill look for a profile that matches that
     
  4. Oct 23, 2012 #4364 of 10412
    moyekj

    moyekj Well-Known Member

    11,141
    31
    Jan 23, 2006
    Mission...
    hb tivo hd profile is already compatible. The key is you have to PUSH to your TiVo using pyTivo, not PULL. Push means using pyTivo webserver to initiate a push (or indirectly via kmttg). If you PULL it will transcode back to mpeg2 which is very slow and will be much larger than the mp4 file size.
     
  5. Oct 30, 2012 #4365 of 10412
    Jimf1234

    Jimf1234 New Member

    21
    0
    Feb 11, 2009
    I have been a member for quite awhile but just got a new macbook pro and I'm having this issue.

    >> DECRYPTING /Users/jim/Desktop/American_Restoration_Hammered_550 HSTRYHD_1351128600.TiVo ...
    Failed to start command: /Applications/kmttg_v0p8v/tivodecode/tivodecode --mak MAK --no-verify --out "/Volumes/750/kmttg/American_Restoration_Hammered_550 HSTRYHD_1351128600.mpg" "/Users/jim/Desktop/American_Restoration_Hammered_550 HSTRYHD_1351128600.TiVo"
    Cannot run program "/Applications/kmttg_v0p8v/tivodecode/tivodecode": error=86, Bad CPU type in executable
     
  6. Oct 30, 2012 #4366 of 10412
    moyekj

    moyekj Well-Known Member

    11,141
    31
    Jan 23, 2006
    Mission...
    You probably need the Mac OSX Intel binary for tivodecode:
    http://kmttg.googlecode.com/files/tivodecode_MacOSX_intel.zip
     
  7. Oct 30, 2012 #4367 of 10412
    Jimf1234

    Jimf1234 New Member

    21
    0
    Feb 11, 2009
    Thank you that worked
     
  8. Nov 1, 2012 #4368 of 10412
    elprice7345

    elprice7345 Member

    145
    0
    Sep 28, 2009
    Houston, TX
    I noticed after getting the fall update, that any shows pulled to my TiVos show the transfer date in kmttg instead of the OAD.

    The OAD appears correctly on the TiVo.

    Has anyone else noticed this?
     
  9. Nov 1, 2012 #4369 of 10412
    cherry ghost

    cherry ghost Active Member

    5,277
    5
    Sep 13, 2005
    Chicago
    same here
     
  10. Nov 1, 2012 #4370 of 10412
    lpwcomp

    lpwcomp Active Member

    8,078
    2
    May 6, 2002
    John's...
    AFAIK, kmttg has always shown the record date/time, not the OAD. TiVo has done something odd here as the record date/time still displays properly on the TiVo.
     
  11. Nov 1, 2012 #4371 of 10412
    moyekj

    moyekj Well-Known Member

    11,141
    31
    Jan 23, 2006
    Mission...
    That's right, kmttg has always used <CaptureDate> from the NPL XML as the date, so I guess for pulls <CaptureDate> is being set to the time the show is pulled? For those seeing this are you pulling with pyTivo and associated pyTivo metadata file?
     
  12. Nov 1, 2012 #4372 of 10412
    lrhorer

    lrhorer Active Member

    6,924
    0
    Aug 31, 2003
    San...
    I'm not sure I follow exactly what you are saying. Where are you looking in kmttg to find this date, and how can the date be both correct and incorect on the Tivo?
     
  13. Nov 1, 2012 #4373 of 10412
    elprice7345

    elprice7345 Member

    145
    0
    Sep 28, 2009
    Houston, TX
    I'm pulling with pyTivo and an associated pytivo metadata file. I'm also using the default.txt pyTivo option to force the OAD to be used.

    Shows pulled before the update show the OAD in kmttg. Shows pulled after the update show the pull date in kmttg. In both cases, the OAD is correctly displayed in the NPL.
     
  14. Nov 1, 2012 #4374 of 10412
    lrhorer

    lrhorer Active Member

    6,924
    0
    Aug 31, 2003
    San...
    Show where in kmttg? I requested a feature that would allow kmttg to pull the OAD off a video without having to transfer from the TiVo to the PC some months ago, but was shot down. Again, where are you seeing the OAD in kmttg?
     
  15. Nov 1, 2012 #4375 of 10412
    moyekj

    moyekj Well-Known Member

    11,141
    31
    Jan 23, 2006
    Mission...
    And you're saying that was working fine before 20.2.2 software right? Which implies something changed in metadata handling for pulls (and apparently pushes as well since seriesId handling for grouping purposes seems to have changed). I think this topic is more relevant in pyTivo thread by the sound of it.
     
  16. Nov 1, 2012 #4376 of 10412
    lrhorer

    lrhorer Active Member

    6,924
    0
    Aug 31, 2003
    San...
    Except that he is seemingly saying everything is fine on the TiVo for content transferred both pre- and post-upgrade, but that something in kmttg is now not showing the OAD. If kmttg ever shows the OAD, I would like to know about it.
     
  17. Nov 1, 2012 #4377 of 10412
    moyekj

    moyekj Well-Known Member

    11,141
    31
    Jan 23, 2006
    Mission...
    No I think he's saying he setup pyTivo pulls such that the <CaptureDate> would get set to OAD and that used to work fine, but now CaptureDate is being set to the time of transfer instead of OAD in the metadata file with the new TiVo software.
     
  18. Nov 1, 2012 #4378 of 10412
    elprice7345

    elprice7345 Member

    145
    0
    Sep 28, 2009
    Houston, TX
    moyekj is correct.

    Both before and after the TiVo update OAD shows correctly in the NPL and sorts by OAD as desired. The dates on the TiVo are displayed correctly.

    The kmttg date that is displaying differently is on the kmttg list of shows. This date displays the OAD for shows pulled before the update, if I used the default.txt when I pulled the shows, and the transfer date for shows pulled after the update.
     
  19. Nov 1, 2012 #4379 of 10412
    cherry ghost

    cherry ghost Active Member

    5,277
    5
    Sep 13, 2005
    Chicago
    here's the same show pulled yesterday and again today(in progress), same metadata. Notice the date is different. The OAD is 9-4-12, which I know won't show in kmttg. The transfer date is showing.


    [​IMG]
     
  20. Nov 1, 2012 #4380 of 10412
    lpwcomp

    lpwcomp Active Member

    8,078
    2
    May 6, 2002
    John's...
    Once again, kmttg does not display the OAD in the list, it displays the capture date/time, which used to be the same as the record date/time. Apparently, with the latest update, the Premieres are differentiating between the two. The TiVo displays the OAD ( as first aired) and the record date/time. It does not display the capture date.

    Having time : OAD in the metadata simply tells pyTivo to use the OAD as the record date/time that it puts in the XML for the transfer.
     

Share This Page