PDA

View Full Version : Direct Insertion?


wkozun
10-26-2003, 01:08 PM
I see a sticky thread for direct extraction with a TiVo hard drive in a PC. Can you do direct insertion or do you have to use mfs_ftp running on the TiVo. The reason I ask is that I get VERY SLOW insertions.

AlphaWolf
10-26-2003, 01:25 PM
you could...but that would involve doing each step manualy, which would be a pain in the ass.

cwingert
10-26-2003, 06:48 PM
I actually have been working on doing this over NFS. I have an SA1 without any performance enhancements, ie I have not done any setpri, ideturbo, hdparm enhancements. Just a stock install.

I have inserts of 875 KBytes/Sec and extraces of 690 KB/Sec. I was thinking of putting a package together, but wanted to assess interest.

AlphaWolf
10-26-2003, 07:44 PM
I think he is refering to having the drive out of the tivo, where you can't run tivosh.

My thought on that would be that he has to create the objects and the stream parts using 'mfs streamcreate', note the FSIDs somewhere, then re-compile mfs_import for i386 (or whatever platform he is using), and manualy split apart the stream and insert each part one by one.

No matter how you do it, you are going to have to make use of tivosh, unless somebody writes a complete set of libraries that can write to not only the FS itself, but the database as well.

rc3105
10-26-2003, 07:53 PM
finding & fixing the mfs_ftp insert bottleneck is a LOT less work than building 1 recording by hand

if you just want to insert from an nfs / samba mount use mbm's import.tcl

cwingert
10-26-2003, 08:15 PM
My program inserts and extracts tar files, so it basically makes the same types of files as mfs_ftp.

AlphaWolf
10-26-2003, 08:36 PM
would indeed be nice to have NFS handling of TMF files though (well, samba would actualy be more convenient for me as I use that for my network, but NFS works :) )

cwingert
10-26-2003, 09:04 PM
The program is share agnostic (ie doesn't care if it Samba). The file runs on the PPC and expects to see the TMF as a file. The performance numbers I quoted were based on certain rsize/wsize in NFS.


Originally posted by AlphaWolf
would indeed be nice to have NFS handling of TMF files though (well, samba would actualy be more convenient for me as I use that for my network, but NFS works :) )