I'm hoping someone has time to develop a new version of pyTivo called pyHDtivo. The limited testing I did seems to indicate that the maximum safe video bitrate HD capable tivo's can handle is 16mbps and maximum safe audio rate is 384kbps. I'd like to have a pyHDtivo server that checks the video and audio bitrates of the source files and only transcodes mpg files if the bitrates are above 17mbps and 448kbps for video and audio respectively. If the bitrates are at or below these levels, it should pass the file untouched. For other types of video files that have to be transcoded no matter what, pyHDtivo should check the video bitrate of the source and use a transcoding bitrate that matches the source rather than use a predetermined bitrate. Since this will result in the occasional mpg that gets passed but will not play on the tivo for whatever reason, a subfolder can be created where the recordings are stored called "force_transcode". The user could then place non-compatible videos in this folder to tell pyHDtivo that you want the video transcoded. I suppose a quick fix alternative to making pytivo check bitrates might be to create serveral subfolders within the tivo recordings folder using bitrate as the folder name. For example \\tivo_recordings\4096\video1.mpg \\tivo_recordings\8192\video2.mpg \\tivo_recordings\16384\video3.mpg or \\tivo_recordings\1080p\video1.mpg \\tivo_recordings\720p\video2.mpg \\tivo_recordings\480p\video3.mpg Then modify the config files to make pytivo obtain the desired bitrate and/or resolution from the folder name instead on using one preset value for all transcoding. This way we could put our videos in whichever folder best defines the bitrate we want to use for transcoding. MPEGValidator could be used to analyze the mpeg stream and then we could drop the video in the folder thats closest to the current bitrate.