Page 97 of 99 FirstFirst ... 47879596979899 LastLast
Results 1,441 to 1,455 of 1476

Thread: Mfs_Ftp: extract, archive, restore & transfer recordings

  1. #1441
    Join Date
    Jun 2008
    Posts
    13
    GBill,

    I have found FileZilla to be the best program (over SmartFTP and FTP Commander) with mfs_ftp for me, and have to wait about 1.5 minutes for my directory listings.

    I set it to launch in ACTIVE mode by default and it works reliably, not sure why you are unsure of ACTIVE mode. I set the TIMEOUT on the TRANSFERS settings page to be 0, as you have also tried.

    My HR10-250 has two 500GB drives and therefore about 400 entries in the directory listing.

    One more thing: I have suspected that high transfer speeds can cause me to have disconnects at certain times of day (I have my HR10-250 on a 802.11g game adapter and can get up to 2 MB/sec wirelessly at times) and so have limited the SPEED LIMITS somewhat - you might try that.

    -Sevron

  2. #1442
    Join Date
    Jun 2008
    Posts
    13

    XML - Some explanations

    Here's a follow-up to my own post. Thanks go to rbautch and hichhiker and others for what I have learned about XML and TMF files. Not sure where else this info is or should go but I'll throw it into the pile. Perhaps an example like this exists elsewhere but I cannot find it. Is everyone inserting XML info some other easier way I'm not aware of????

    I'm not using Tivoserver (because I cannot on the HR10-250), I'm using mfs_ftp but I don't know why Tivoserver or other apps to insert videos would not work. I'm not a great script writer, but these work.

    SUMMARY: The attached XML example (must rename it to "showing.xml"!!!) works with .ty files which I converted from MPG to .ty with FFMPEG and upload into my HR10-250 using MFS_FTP.

    MAKE A TMF FILE (see attached example in file splittar.sh):
    a) Cut the video (already in .ty format) into pieces that are no more than 512MBytes in size. I use Cygwin split.
    b) Name these parts "part00.ty", "part01.ty", etc... enough to contain the entire original .ty file.
    c) Create a file "showing.xml" which contains the XML info that you want associated with this video (see below).
    d) Create one .tmf file by using tar. My Tivo is picky about the order, perhaps they all are, I'm not sure: The file showing.xml must go first, then the 'parts' go last in ascending numerical order.

    XML EXPLANATION: Keep the hierarchy as-is (i.e. the stuff in between each OBJECT and /OBJECT is one level) but change just a few values as you need to. Play around with a small file that uploads quickly to learn.

    Explanation of fields that you must/should change per recording you want to upload:

    1) Duration
    Code:
    <Duration>2894</Duration>
    This value should be changed to match the length of the video, in seconds. When playing back the video, this value will appear to the right of the green bar, no matter how long the video really is! If there is less video data than this value, then the green bar will not fill its entire area. NOTE: I don't know what XML entry corresponds to the DURATION field when looking at the INFO for a video on the TV - I can never get this value to be anything other than 0:00 even though the green-bar value is correct.

    2a) Date - Of upload/recording
    Code:
    <Date>14229</Date>
    Change this value (see below) to be whatever date you want for the date the video was recorded. The NPL will sort-by-date on this value. This will also appear in the filename when viewed from mfs_ftp.

    2b) Date - Air date
    Code:
    <OriginalAirDate>14230</OriginalAirDate>
    Change this value (see below) to be whatever date you want for the original air date. It will appear in the INFO field but the NPL doesn't sort by this value. It doesn't have to be before the DATE value. This will also appear in the filename when viewed from mfs_ftp.

    You can get both of these DATE values by entering your date (replace 12/17/2008) into this expression, in a Cygwin or Unix prompt (thanks to Hichhiker for this):

    Code:
    expr $(date -d"12/17/2008" "+%s") / 86400
    3a) Folder / Directory control
    Code:
    <IsEpisode>1</IsEpisode>
    <RootServerId>A0038c22c</RootServerId>
    <ServerId>ATSH848609</ServerId>
    <TmsId>SH848609</TmsId>
    You need these if you want the file to upload into an existing directory (see rbautch's excellent guidance here). These values must be created by doing the steps in his post. Do not change these values, and the uploaded files will go into the right directories/folders. See also this link for more details.

    4) Time of day recorded
    Code:
    <Time>3600</Time>
    This value will be displayed as the time-of-day that the episode was recorded, in units of seconds. The NPL will sort on this value (and the date). This value is offset from midnight-GMT but takes into account your Tivo's TimeZone date. For example, I'm in the U.S. Pacific Time Zone, which is 8 hours behind GMT and so my offset starts at 4pm. So, a value of 3600 (i.e. 1 hour) corresponds to 5pm my Tivo. A value of 79200 (i.e. 22 hours) corresponds to 2pm the next day. This will also appear in the filename when viewed from mfs_ftp.

    5) StreamFileSize
    Code:
    <StreamFileSize>2680962</StreamFileSize>
    This value should be set to match the size of the file being uploaded, in Kbytes. I heard there can be problems when it's set too large (>32 bit integer) but have not tried that nor experienced them.

    Others have found that mfs_ftp updates StreamFileSize when a file is inserted. Not sure about other apps.

    6) Start and Stop time
    Code:
    <StartTime>80000</StartTime>
    <StopTime>82984</StopTime>
    (not too sure about these two) I think the StartTime is somewhat arbitrary, as long as it's larger than the Time value, above. The StopTime value should be set to StartTime plus the value of Duration.

    7) TV Station Call Sign
    Code:
    <CallSign>bmc</CallSign>
    You can put whatever text you like here. Not sure if there is a character limit, but I keep mine to 3 characters.

    8) Title - [2 instances]
    Code:
    <Title>_Folder Name_</Title>
    <Title>Put whatever Title you want</Title>
    When under the SERIES object, this text will be changed by the Tivo to match the folder that the file goes into. When under the PROGRAM object hierarchy, this text will appear in the NPL.

    That's all I know for now (and no, I haven't figured out my FFx1 problem yet).

    -Sevron
    Attached Files Attached Files

  3. #1443
    Join Date
    Jun 2008
    Posts
    13

    Figured out the settings for FFx1 to work on HR10-250 Tivo

    FOLLOW-UP: I figured out how to get the FFx1 to work with my uploaded videos. Without the settings below, hitting the fast-forward button when watching my uploaded video only mutes the sound. The video would not go any faster. However, with the settings below (bf and g) the video goes somewhat faster. Tweak these numbers to find the FF speed you like if you don't like my choice.

    Here's the complete ffmpeg command line I use to make good-looking video for the HR10-250 (probably others). Change filesnames (obviously) as needed:

    Code:
    ffmpeg -y -i "InputFile.mpg" -bf 2 -g 8 -qscale 1 -qmin 1 -r 29.97 -aspect 16:9 -vcodec mpeg2video -s 720x480 -b 5800k -acodec copy "TivoFile.ty"
    For Fast-forward to work, insert some B frames into the video with options -bf and -g.
    • Setting "-bf 2" inserts 2 B frames.
    • Setting "-g 8" creates a GOP size of 8 frames (with 2 B frames each).

    Here are some other explanations of settings:
    • Setting "-r 29.97" sets frame rate to 29.97 fps, good on the HR10-250.
    • Setting "-aspect 16:9" creates wide-screen. Deleting this gives 4:3.
    • Settings "qscale 1" and "qmin 1" looks the best, but makes the files big (~6.5GB for ~50 minutes of video).

    And one other observation:
    • Setting "-deinterlace" should only for YouTube, NOT for video being shown on Tivo.

  4. #1444
    Join Date
    Feb 2009
    Posts
    1

    showing.xml missing Showing and Program information in 9.3.2b

    I'm a Tivo newbie and don't know tcl or what I'm doing, but hopefully this will be useful to someone.

    I noticed that the tmf recordings that I downloaded from my Series 2 SA (v 9.3.2b) with mfs_ftp were missing some important metadata in the showing.xml file. For example, Description, Date, Time, and EpisodeTitle, were nowhere to be found. It appears that the MFS Recording structure changed a little at some point, and now the 'Showing' and 'Program' objects are of type subobject instead of object. I don't have a clue what that means except that the dump_object proc in mfs_ftp.tcl only recurses into objects, not subobjects. So here is a small patch to remedy that problem.

    Code:
     switch $atype {
      object { append output [dump_object $a $attr [expr $depth-1] "$prefix "]; set a "" }
     }
    becomes

    Code:
     switch $atype {
      subobject -
      object { append output [dump_object $a $attr [expr $depth-1] "$prefix "]; set a "" }
     }
    Attached Files Attached Files

  5. #1445
    Join Date
    Dec 2002
    Posts
    65
    Does mfs_ftp work on Series 3/ HDTivo?

  6. #1446
    Join Date
    Aug 2004
    Posts
    4,085
    It should work for extraction. Insertion may require some overhaul, as some of the metadata structures have changed in MFS.

    s3tots can convert un-encrypted ty or tmf streams extracted with mfs_ftp to mpeg transport streams playable by VLC, etc.

    As far as I know there aren't any tools that can take video from other sources and convert them to ty's you can insert on an S3. For insertion of content from other sources, you are probably best off using pytivo et al.

  7. #1447
    Join Date
    Mar 2004
    Location
    Perth, Western Australia
    Posts
    72
    Quote Originally Posted by kmt View Post
    Does mfs_ftp work on Series 3/ HDTivo?
    Just to add to what Jamie said in case you do not realise, to run mfs_ftp on a series 3 you also need to replace the prom chip and kernel.

    It definitely works for extraction, have not tried insertion.

    Peter.
    TiVo Series one, two, and TiVo HD

  8. #1448
    Join Date
    Dec 2002
    Posts
    65
    Well I tried it on my HDTivo and I get

    Not a TiVo super block! (magic=0xebbafeed)

    from mfs_uberexport (called by mfs_stream)

  9. #1449
    Join Date
    Mar 2004
    Location
    Perth, Western Australia
    Posts
    72
    Did you just use the base mfs_ftp or did you apply all the patches?

    It's been a while since I built it fresh, but I think there are about 3 patches in these forums.

    Peter.
    TiVo Series one, two, and TiVo HD

  10. #1450
    Join Date
    Aug 2004
    Posts
    4,085
    Quote Originally Posted by kmt View Post
    Well I tried it on my HDTivo and I get

    Not a TiVo super block! (magic=0xebbafeed)

    from mfs_uberexport (called by mfs_stream)
    You need the 64 bit version of mfs-utils on a TiVoHD: link.

  11. #1451
    Join Date
    Dec 2001
    Posts
    587
    Quote Originally Posted by petestrash View Post
    Just to add to what Jamie said in case you do not realise, to run mfs_ftp on a series 3 you also need to replace the prom chip and kernel.

    It definitely works for extraction, have not tried insertion.

    Peter.
    You do NOT need to replace the kernel. You do need to change the PROM chip, and kill the initrd chain, but a kernel full replace is NOT necessary

  12. #1452
    Join Date
    Dec 2002
    Posts
    65
    The 64 bit mfs-utils was the issue. Extraction seems to be working now on the HDTivo.

    I used the mfs_ftp.tar file in the post which identifies itself as 1.2.9p.

    Besides substituting the 64 bit utils, and a tzoffset.tcl fix, I did no other patching. Again its working for extract, but are the other patches referred to included in "1.2.9p", and if not do I need them for some reason not apparent?

  13. #1453
    Join Date
    Dec 2001
    Posts
    587
    I have the latest allowed patched version, working fine on tivo1 (Tivohd) but having a problem on Tivo2 (Another tivohd).

    I am trying to use SmartFTP in either pasv or active modes.

    I start a transfer, it finishes, and just keeps doing it! This test file has transferred over 2 dozen times and never stops.

    Any ideas?

    Here is the log:
    02:18:56:PM - 502 Command not implemented "MDTM {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:18:56:PM - 502 Command not implemented "MDTM { Recording}{The Young and the Restless}{2010-01-28}{Tucker Reveals His Plans for Chancellor Industries}{01.30 PM Thu Jan 28, 2010}{WBZ}.tmf"
    02:19:26:PM - 200 Command okay.
    02:19:57:PM - 200 Command okay.
    02:20:11:PM - newcsocket: {sock33} "192.168.1.180:58798"
    02:20:11:PM - abortcheck: "newcsocket"
    02:20:11:PM - 220 Mfs_Ftp ver 1.2.9p-patchlevel-20080512 - {sock33} from "192.168.1.180:58798"
    02:20:16:PM - serverip "192.168.1.11"
    02:20:16:PM - 215 UNIX
    02:20:16:PM - 502 Command not implemented "FEAT"
    02:20:16:PM - 200 Type set to I
    02:20:16:PM - REST: "0"
    02:20:16:PM - 350 Restart okay, awaiting file request.
    02:20:16:PM - resume(s) == "0"
    02:20:16:PM - 257 "/" is current directory.
    02:20:16:PM - 250 Directory change successful.
    02:20:16:PM - 257 "/tmf" is current directory.
    02:20:16:PM - 502 Command not implemented "SIZE {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:20:16:PM - 502 Command not implemented "MDTM {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:20:16:PM - 502 Command not implemented "STAT {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:20:16:PM - 200 Type set to I
    02:20:16:PM - PORT 192,168,1,180,229,178
    02:20:16:PM - data channel "sock34" to 192.168.1.180:58802
    02:20:16:PM - 200 PORT command successful.
    02:20:16:PM - NLIST: "LIST -aL" ("" == LIST command)
    02:20:16:PM - 150 Opening ASCII mode data connection for file list.
    02:20:16:PM - list_type is "LIST"
    02:20:16:PM - update_rec_fsids: forced 1
    02:20:30:PM - updating cached recording info
    .02:20:32:PM - recording in progress, don't cache 2523854.xml yet
    .................................................................................................... .................................................................................................... .................................................................................................... ........................................

    02:20:32:PM - build_rec_filenames:
    .................................................................................................... .................................................................................................... .................................................................................................... .........................................

    02:21:35:PM - 226 Transfer complete.
    02:21:35:PM - 200 Command okay.
    02:21:35:PM - 200 Type set to I
    02:21:35:PM - PORT 192,168,1,180,230,12
    02:21:35:PM - data channel "sock34" to 192.168.1.180:58892
    02:21:35:PM - 200 PORT command successful.
    02:21:35:PM - RETR:
    "{Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:21:35:PM - 150 About to open data connection.
    02:21:36:PM - set priorities: mfs_ftp 1 % I/O chan 1 %
    02:27:00:PM - 226 Transfer complete.
    02:27:00:PM - abortcheck: "RETR"
    02:27:00:PM - 502 Command not implemented "MDTM {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:27:00:PM - 200 Command okay.
    02:27:00:PM - abortcheck: "ping_pong"
    02:27:00:PM - 200 Type set to I
    02:27:00:PM - 502 Command not implemented ""
    02:27:00:PM - PORT 192,168,1,180,231,172
    02:27:00:PM - data channel "sock34" to 192.168.1.180:59308
    02:27:00:PM - 200 PORT command successful.
    02:27:00:PM - NLIST: "LIST -aL" ("" == LIST command)
    02:27:00:PM - 150 Opening ASCII mode data connection for file list.
    02:27:00:PM - list_type is "LIST"
    02:27:00:PM - update_rec_fsids: forced 1
    02:27:16:PM - updating cached recording info
    .02:27:17:PM - recording in progress, don't cache 2523854.xml yet
    .................................................................................................... .................................................................................................... .................................................................................................... ........................................

    02:27:18:PM - build_rec_filenames:
    .................................................................................................... .................................................................................................... .................................................................................................... .........................................

    02:28:26:PM - 226 Transfer complete.
    02:28:26:PM - 200 Type set to I
    02:28:26:PM - 502 Command not implemented "SIZE {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:28:26:PM - 502 Command not implemented "MDTM {Red Dawn}{1970-01-01}{}{11.00 AM Thu Jan 28, 2010}{EPIXHD}.tmf"
    02:28:26:PM - 200 Type set to I
    02:28:26:PM - PORT 192,168,1,180,232,18
    02:28:26:PM - data channel "sock30" to 192.168.1.180:59410
    02:28:26:PM - 200 PORT command successful.
    02:28:26:PM - NLIST: "LIST -aL" ("" == LIST command)
    Last edited by philhu; 01-28-2010 at 02:52 PM.

  14. #1454
    Join Date
    Aug 2004
    Posts
    4,085
    It is an issue with SmartFTP. Look for the "continue on error" option.

    Reference: link.

  15. #1455
    Join Date
    Mar 2002
    Posts
    43
    Quote Originally Posted by Jamie View Post
    It is an issue with SmartFTP. Look for the "continue on error" option.

    Reference: link.
    Last time I looked into SmartFTP and mfs_ftp.tcl (probably 3 years ago), the lack of SIZE support didn't bother it. When SIZE came back unsupported it would just do the transfers (or possibly do another LIST to get the size, but wouldn't treat it as gospel, I can't remember the exact sequence). When I tried implementing a primitive SIZE in mfs_ftp, SmartFTP took it as gospel truth and would fail the transfer if the number of bytes transferred didn't equal the number of bytes reported in SIZE, down to the byte (even though the actual transfer was completed). Since the various transfer formats (.tmf, etc.) make exact byte size reporting difficult because of the xml stuff tacked onto the binary, SmartFTP worked better without a SIZE.

    I guess there's a major new version of SmartFTP out recently, I have no idea what it does.

Posting Permissions

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