Advertisements Besides IMMEDIATELY becoming the "Easiest-to-Install " application to move files between TiVos and PCs, and back, a recent update to @Dan203's PyTiVo Desktop added "0x47 every 188" TS Sync Error Checking: Do you use it? Do you know how invaluable it is to you? Did you happen to notice me CHANTING it at every opportunity the past few weeks? As more and more stations switch to H.264, you will find, if you haven't already, that you can no longer use PS / 'Slow' Format Transfer for those shows; you *MUST* use TS / 'Fast' Format Transfer. And, TS / 'Fast' Format Transfer has the 'hidden ' feature of NOT announcing transfer errors that occurred TiVo-to-PC *UNTIL* you attempt to bring back that show from your offline storage, PC-to-TiVo, and the transfer fails. While @Dan203's PyTiVo Desktop also implements "0x47 every 188" checking during its PC-to-TiVo transfers, other programs, like Streambaby for example, don't (at this time); so, Streambaby (I believe) would fail at the TS Sync Error. Up until *I* encountered the H.264 'problem', I've stuck with PS / 'Slow' Format Transfers, since ~66% of the TS / 'Fast' Format Transfers that I performed / archived back in February / March 2016 (when I initially installed kmttg and @wmcbrine's PyTiVo) *FAILED* to transfer back via @wmcbrine's PyTiVo back in the summer of 2016. The purpose of this thread, and its accompanying poll, is to gauge the TCF Community interest in "0x47 every 188" TS Sync Error Checking. If you do use it, you have to set the "Maximum # of Retries" that you're willing to put your equipment (TiVo and PC) through: Set it too low and you may never get a 'glitch-free' copy Set it too high and you may have your equipment running for hours and hours I'm asking Dan to add the "# of Retries" his PyTiVo Desktop application performed to both the ongoing log (where the number will keep incrementing by 1 each time it fails), and the final filename (where you can easily see the 'effort ' involved to get a 'glitch-free' copy). Instead of: The Shakiest Gun in the West (Recorded May 21, 2017, SUNHD-E) (TS) (^46)You'd see: The Shakiest Gun in the West (Recorded May 21, 2017, SUNHD-E) (TS) (^46_2)And, if/when it succeeded, you'd see: The Shakiest Gun in the West (Recorded May 21, 2017, SUNHD-E) (TS) (0_19) It would be 2 or 3 more characters added to the filename, both in the log and in the final filename; an underscore plus a number, either "_9" or "_99". Dan feels that it would 'dirty up' the filename; what do YOU think? Thanks for voting!