Separate names with a comma.
Discussion in 'TiVo Home Media Features & TiVoToGo' started by moyekj, Mar 15, 2008.
I am not getting audio on the Tivo either.
Are you pushing to TiVo using pyTivo (not pulling)? medianfo is a good tool to use to examine the contents of a video file - lists audio and video details which can then easily determine if there is actually an audio stream in your mp4 file. Post the mediainfo information for your mp4 file here if it's not clear what you are looking at.
I am pulling the video using tivo desktop. I'll check out media info and report back.
That explains it. Whenever you pull a video it always transcodes non-mpeg2 video to mpeg2 on the fly. TiVo Desktop can't handle doing that transcode on the fly properly for mp4 files with AC3 audio. The best option is to use pyTivo and do a push, which then avoids having to transcode back to mpeg2 (and associated further quality hit) and transfers much quicker as well.
Another option is to use streambaby to stream the file to your TiVo instead of a pyTivo push.
You will find mediainfo will show you have AC3 audio and VLC player will be able to play it back with audio on your PC.
For Pytivo do I need pytivo and pytivo push? I tried streambaby and was unsatisfied with the results. Not sure if my comptuer or my network is too slow but I got lots of pauses.
I have a hockey game on my tivo that was recorded off of NHLHD. In its raw state, it was in excess of 14GB. I transferred it to my PC and ran it through VRD - both to qsf it and to remove commercials (it was transferred/decrypted with KMTTG). I then used kmttg to encode it to mp4 using the ff_tivo_hd profile - it took 13 hours (when I transcode with VRD, it takes about 4.5 hours - still a big number, but significantly less). The resulting file was playable on my PC (VLC) but could not be pushed with pytivo because of it size - 5.5GB - I had to use qtfaststart to rearrange the atoms before it became pushable.
Now it pushes fine, and transfers in a reasonable amount of time, but the video quality is horrible - it has a "strobe" effect that is quite disconcerting to watch. I can pull it to my tivo, and the transcode quality is just fine, but it again takes about 13 hours to transcode.
I haven't yet tried pushing the VRD encoded version of the file to see how that does, but until I do, I was wondering if anyone has a possible explanation for the poor video quality and long encode times.
Don't understand the question. Once you have pyTivo installed it has the capability to do pushes after you configure it with your tivo.com login & password. You can then initiate the push from pyTivo web page or from kmttg after you set things up correctly. Visit pyTivo thread or pyTivo forums for more details on setting up pyTivo for pushes.
What TiVo model do you have? The original S3 OLED models are pretty bad at H.264 playback compared to Premiere. I'm not sure about THD units as I never owned one. How is playback on the PC? If it is OK there then it suggests the TiVo decoder is the problem.
As far as long encoding times it's not surprising - H.264 encoding is very compute intensive and ff_tivo_hd profile is setup to use a pretty high bit rate and your source file is HD. Not sure which profile you used for VRD, but if you used MP4 File (Generic) then note that you will get 2 channel AAC audio. There's a special non-standard VRD profile that can be used if you want AC3 audio, but after generating it you won't be able to open it in VRD (hence why it's not officially released).
I'm getting an increasing number of videos that can't be played on my tivo or even with VLC. It doesn't matter what profile I use. The hard drive on my tivo was failing. I thought that might be the cause, videos with errors.
Problem still occurs with shows recorded on my new drive. Time to troubleshoot.
Bad files always give me an error with atomic parsley. I'm not sure if atomic parsley is corrupting the files (cause of the problem) or if the error is letting me know there is a problem with the file. Problem seems to occur more often with larger videos (over 4 Gig output file).
AtomicParsley failed (exit code: -1073741819 ) - check command:
I have no idea what that exist code means.
Thanks. I have an original S3 so that probably explains it. For most shows, the ff_tivo_hd isn't bad, but the hockey game, with its fast motion, is particularly annoying.
I guess for something like that that I value, I'm just going to leave it in mpg format. It's big, but I don't have too many of them, and I have 3.6TB on my NAS, so I have plenty of room.
FYI, the latest VRD TVSuite 4 can finally edit mp4 container with H.264 video & AC3 audio.
EDIT: However I haven't yet been able to get QS Fix working via kmttg with this new version...
I'm not enough of a "geek" to understand how you'e interfacing with VRD.
I found this on their website. I don't know if it helps solve the issue.
Haven't had time to dig into it, but I suspect the issue is related to these COM changes outlined in release notes:
(kmttg uses COM functions for running VRD tasks in batch mode)
That was indeed the issue. The latest version has to use newer COM functions for qsfix & adcut tasks. Next kmttg release will support latest VRD TV Suite as well as still be backwards compatible with older releases.
can you please tell me how to keep subtitles when transferring from tivo to computer?
Subtitles are already preserved for TTG transfers.
sorry but im absolutely new to this and i dont know what that means.
does it mean you can transfer the show and keep captions and replay them on computer and/or dvd.
SORRY. WORKED IT OUT.
THANKS FOR YOUR REPLY.
Forgot to add the large file flag to this encoding profile (-4), which will cause issues if the resulting mp4 file is larger than 4GB. Updated and attached.
OK thanks, I've committed this to SVN and will be part of next release.
Thanks, Kevin. If you want to include a version for SD video, you can simply change the -q 21.0 to -q 19.0. At least, that is my recommendation for the value.