Separate names with a comma.
Discussion in 'TiVo Home Media Features & TiVoToGo' started by moyekj, Mar 15, 2008.
Thanks, I have admin rights on my machine. I did try it, however, to no avail.
For reporting VRD crashes your best bet is the VRD Forums and uploading a sample for VRD folks to take a look.
I have Kmttg set this way. The tivo files goes in a folder that is named to be deleted. I have the MPG files going to a folder named for Videoredo auto processor. In the configuration it is set to delete the tivo files. I use the Kmttg help to do the updates. With Kmttg v1pOp it not encoding the tivo files to mpg but it not deleting the tivo files.
What could be the problem with this now? The only thing I changed was the use RPC to get the NPL when possible.
I tracked down the problem preventing 2nd Atomic run and it is fixed in next release. Associated with this problem, atomic jobs were unnecessarily being queued behind other jobs, but now they launch right away without waiting for other jobs to complete.
Don't understand what you wrote. Please clarify your post and include any kmttg log messages.
Think he means that KMTTG is not decrypting to .mpg from .tivo and said encode instead.
Awesome! Thanks for looking into this. I'll look forward to checking out the next release.
Another possibility: You do have TiVo Desktop installed, correct? At least the parts needed by VRD.
Good point - strong possibility that is the issue. A partial install of VRD is needed such that TiVoDirectShowFilter.dll is installed so VRD can use it for handling .TiVo files.
With the semi-frequent C133 error problem lately, I noticed that the RPC connection doesn't work when in that situation.
Could kmttg fall back to the non-RPC method if it gets an error? That way it would "just work" even in the situations where Tivo can't keep their !@#$ servers running, and we wouldn't have to change our prefs back and forth..
That's odd, for series 4 and later units I didn't think MyShows listings were affected. Things like Guide and Search used to be affected. Recently, however I changed the RPC calls related to MyShows so it's possible something was affected, though I wasn't having problems last night. If you still have associated error message can you post it here?
That's odd, for series 4 and later units I didn't think MyShows listings were affected. middlemind server is not used directly for MyShows retrieval, though it's possible indirectly the TiVo relies on servers for some of that information. Things like Guide and Search used to be affected since they do use middlemind servers indirectly. Recently, however I changed the RPC calls related to MyShows so it's possible something was affected, though I wasn't having problems last night. If you still have associated error message can you post it here?
Sorry, I knew I should have kept it.. I don't suppose it keeps the log?
I'll post it the next time I see it. (Also, I did have a couple of other java errors trying something else during the C133 time, but I didn't figure out reproducible steps for that part -- it was AFTER this part I was able to repro though.)
I don't seem to be having networking problems at the moment, but RPC is failing on my Roamio, but succeeding on my Premiere 4.. one's sitting on the other, connected to the same switch that my laptop is.. I'm fairly sure this is the kind of error I was seeing last night too:
Remote getURLs - JSONObject["title"] not found.
Remote getURLs - failed to retrieve mfs URLs
and remember, the old style connection is working and I already downloaded a bunch of recordings (making room for more Olympics).
That's interesting - the above failure seems to be because you have 1 or more shows that don't have a title for some reason which I didn't think was possible. That failure is at a point beyond which all RPC data is already collected for a show and kmttg is just trying to find/construct the URLs needed for metadata and download.
Try the kmttg.jar in this zip file which accounts for that possibility and I think should solve your issue:
pdc, above kmttg.jar has the atomic related fix in it too if you want to test it out.
I am trying to transfer a program from Roamio to TiVoHD. The program is h.264 (recorded on Universal Sports on FiOS). I can transfer directly to the HD using MRV, but i get only audio and no video.
I spent some time getting kmttg to transfer to PC until I found this post http://www.tivocommunity.com/tivo-vb/showthread.php?p=9793380#post9793380.
That solved the first problem, but now I can't transfer the show back to the TiVoHD (or even back to the Roamio for that matter).
Series 3 units don't support H.264 cable channel recordings (in TS container). If you REALLY want to transfer to your HD unit you will need to remux to use mp4 container instead of mpeg2 TS container and then PUSH back to your HD using pyTivo. Since that requires decrypting and you can't use tivodecode on H.264, only something like VideoRedo TVSuite will work to do that.
You should be able to pull H.264 .TiVo files (in TS container) back to your Roamio using latest TiVo Desktop or recent pyTivo.
Thanks for the quick reply. For this particular program, I don't REALLY want to go to that much effort. Maybe in the future.
I would like to figure out why the program won't transfer back to the Roamio via pyTivo. It is marked with a red X and says "Transferring prohibited by the copyright holder." and a duration of 0:00. Other (non h.264) files in the share transfer fine.
I set up TiVo desktop and pointed it to the same share. It's transferring now and I get video and audio on the Roamio.
I must have something set up wrong with pyTivo. I just installed it today. Not sure which version it is, but it is the wmcbrine fork. kmttg is v1p0p. TiVo desktop is 2.8.3.
I could just use TiVo desktop, but I would like to get pyTiVo working.
Should post in pyTivo thread for pyTivo help, but 1st thing I would suspect is what ffmpeg.exe you are pointing pyTivo configuration to - you should use a recent version. (pyTivo uses ffmpeg to analyze video files including .TiVo files, and is probably not able to read the H.264 .TiVo file properly).
I tried 3 different ffmpeg files (one "older build of FFmpeg known to work well with pyTivo" I downloaded today, one that came with kmttg dated December, and the latest from zeranoe I got tonight), using either the Restart or Shutdown buttons from the pyTivo browser settings page after each change. No luck. Then I shut down everything and restarted from pyTivo.py and now it's working like it's supposed to. Yay! It's possible one of the other ffmpeg files might also work, but I'm not that curious tonight.
Interestingly, even the TiVoHD will let me try to transfer the file now, but the blue light only flashes for a second before it gives up.