1. Update to latest version (not required but recommended)
2. Since you have a series 3 unit make sure that under Configure->Tivos that "Enable iPad style communications with this Tivo" is turned off. Sounds like you have that setting enabled.

That's what the problem was...Thanks moyekj.

I did notice another issue after adding a Premiere and later changing its name through the Tivo menus, if "look for Tivos on network" is checked, kmttg will show both the old and the new names as two units with the same IP address. How would I get rid of the old name for good?

I did notice another issue after adding a Premiere and later changing its name through the Tivo menus, if "look for Tivos on network" is checked, kmttg will show both the old and the new names as two units with the same IP address. How would I get rid of the old name for good?

If you haven't rebooted your TiVo since changing its name then you need to do that. There's an old TiVo bug where a TiVo with a changed name will announce itself as both old and new name until rebooted. Once that is done then in kmttg under config-Tivos tab you can just remove from there and since rebooted TiVo won't broadcast old name it won't show up again in kmttg.

If you haven't rebooted your TiVo since changing its name then you need to do that. There's an old TiVo bug where a TiVo with a changed name will announce itself as both old and new name until rebooted. Once that is done then in kmttg under config-Tivos tab you can just remove from there and since rebooted TiVo won't broadcast old name it won't show up again in kmttg.

I have rebooted the Tivo after the name change by the Tivo menu, it also rebooted just two days ago after receiving the new update and still both names appear. Would a reboot by unplugging make a difference?

I did notice another issue after adding a Premiere and later changing its name through the Tivo menus, if "look for Tivos on network" is checked, kmttg will show both the old and the new names as two units with the same IP address. How would I get rid of the old name for good?

I had that issue once, and you simply go into the Configuration and under the Tivos tab, select and delete the Tivo listed with the old name.

When I have "Allow only 1 download at a time" checked, shouldn't it be for just 1 download at a time and allows other jobs such as decrypt, QSFix, encode to execute?

I find it will do 1 job (decrypt, or qsfix, etc.) then a downloads starts and afterwards, it will not do another job until the download completes.

Yes looking at the code I see that if you have more than 1 download queued up and have that option turned on that all queued up jobs are prevented from starting until current download completes which is behavior you are seeing. I'll have to modify the logic to apply it to download jobs only as it should be.

If you haven't rebooted your TiVo since changing its name then you need to do that. There's an old TiVo bug where a TiVo with a changed name will announce itself as both old and new name until rebooted. Once that is done then in kmttg under config-Tivos tab you can just remove from there and since rebooted TiVo won't broadcast old name it won't show up again in kmttg.

I have rebooted the Tivo after the name change by the Tivo menu, it also rebooted just two days ago after receiving the new update and still both names appear. Would a reboot by unplugging make a difference?

I have rebooted the Tivo after the name change by the Tivo menu, it also rebooted just two days ago after receiving the new update and still both names appear. Would a reboot by unplugging make a difference?

When you login to your tivo.com account does it show the same name new name you changed it to? There must still be 2 different MDNS broadcasts with different names & same IP happening on your network. Maybe under kmttg config-Tivos tab try enabling "Detect with TiVo Beacon instead of Bonjour" instead to see what happens. Or if you have static IP settings for you TiVos you can just disable "Look for Tivos on the network" completely for now so you don't have to deal with it.

Note that starting with this version you can now update kmttg installation directly from kmttg using Help->Update kmttg... menu entry.

For Windows and Mac platforms you can also install the latest tools zip file from kmttg using Help->Update tools... menu entry.

In addition to the ability to self update there are a few bug fixes and changes included in this version.

NOTE: I'm transitioning kmttg from googlecode to sourceforge since Google Downloads are scheduled to be shut down for any new downloads. So in the future please use the new kmttg home to look for information & files:http://sourceforge.net/projects/kmttg/

I've updated Google site also to contain this version for the benefit of those that don't know about the sourceforge site yet and so they can get this new version of kmttg with self updating capabilities to make it easy to get new versions going forwards.

Did something change with Atomic Parsley? --TVEpisode and --TVEpisodeNum used to have the same value. This is from a recent encode

--TVEpisode 424 --TVEpisodeNum 24 --tracknum 424 --TVSeasonNum 4

In the past, --TVEpisodeNum would also be 424

Yes. By request from AppleTV users (plus logically matching what that atom represents). From release notes:
"Updated AtomicParsley run such that --TVEpisodeNum argument is just the episode # without season # for correct display by AppleTV and the like."

Yes. By request from AppleTV users (plus logically matching what that atom represents). From release notes:
"Updated AtomicParsley run such that --TVEpisodeNum argument is just the episode # without season # for correct display by AppleTV and the like."

Ugh, now I have to rerun AP on everything I've encoded so that it sorts properly in iTunes

It's a nasty bug for series 4 TiVos since not only do transfers not work, but it puts TiVo http server in "server busy" mode perpetually until rebooted. Since it's badly broken with 20.3.1 software I've updated code for next release to just ignore 'Resume Downloads' option for series 4 units (with a warning to that effect). Still useful to have for those with series 3 units which is why I didn't remove the option completely.

It's a nasty bug for series 4 TiVos since not only do transfers not work, but it puts TiVo http server in "server busy" mode perpetually until rebooted. Since it's badly broken with 20.3.1 software I've updated code for next release to just ignore 'Resume Downloads' option for series 4 units (with a warning to that effect). Still useful to have for those with series 3 units which is why I didn't remove the option completely.

Actually, I'm not sure about that server busy issue.. That it's perpetual that is.

My P4 rebooted last night (after getting into a weird 'hung' situation a few times.. it would keep recording of course, and DID at least once eventually go back into Live TV.. then would react to some remote presses -- but eventually got back into hung mode -- and like many Tivos, if you hit enough remote keys when it's hung, it eventually reboots).. But ANYWAY.. Before that, I'm *almost* positive that over a few days, I was able to transfer a few things from my P4 *on the same boot* as trying resume from paused point in kmttg. I'd say I'm even MORE sure that it was the same boot as trying to resume from paused point from my TivoHD too.

Though I also remember that I *did* get some kind of error shown in kmttg (maybe it was server busy).. the kind that you THINK will just keep repeating.. But on the retry, it started downloading fine.

When I tested yesterday with my 2 tuner Premiere with 20.3.1 software I tried both Java and Curl modes and could no longer download anything after attempting Resume Downloads. After multiple reboots and tries without any luck I concluded it's best to turn off that feature for series 4 units since even if it does not kill the http server it doesn't work anyway.
From my experiments it looks like MRV resume between series 4 units still works OK and MRS resume I use all the time and know it works fine. I don't have a series 3 unit plugged in anymore to test with.

Take a look at VideoRedo_configuration Wiki page.
2 important things:
1. Make sure kmttg service is running using your account, not default Windows account
2. Make sure you bring up the VideoRedo GUI at least once using same account (with Admin privileges) so it registers itself so WScript can find it.

Take a look at VideoRedo_configuration Wiki page.
2 important things:
1. Make sure kmttg service is running using your account, not default Windows account
2. Make sure you bring up the VideoRedo GUI at least once using same account (with Admin privileges) so it registers itself accordingly.

When I tested yesterday with my 2 tuner Premiere with 20.3.1 software I tried both Java and Curl modes and could no longer download anything after attempting Resume Downloads. After multiple reboots and tries without any luck I concluded it's best to turn off that feature for series 4 units since even if it does not kill the http server it doesn't work anyway.
From my experiments it looks like MRV resume between series 4 units still works OK and MRS resume I use all the time and know it works fine. I don't have a series 3 unit plugged in anymore to test with.

I was just wondering if you or anyone else have actually downloaded a "partial" file since the 20.3.1 upgrade. Does the Tivo still have this glitch, or might that have been corrected at the source?