The reported error in this case is a bit misleading. I'd have to see more of the log to nail it down, but generally -- assuming that you had it working before, and have made no changes to your configuration -- push errors are due to problems with mind.tivo.com, which arise every so often. And there's nothing we can do about those, except to be patient, and wait for TiVo Inc. to fix their servers. Or switch to pulls.

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Is there any way to get pyTivo to stop issuing the beacon messages every minute? I need to see the status of my pushes to a remote TiVo and things get scrolled off so quickly that I have no idea what happened.

But I have worked it out. Looks likes has something to do with having no valid shares for a TiVo. I run two copies of pyTiVo, one on port 9032 which I use strictly for kmttg pushes to a remote TiVo and I had set it up with Share=none for all of the TiVos. The other copy is on port 9034, which I use for everything else. I do that because any other transfer activity on the one doing the push can cause the push to fail.

Anyway, yeah, in this situation, you might as well disable the beacon altogether. You can set zeroconf = off and beacon = listen.

Zeroconf is off anyway since I specify the shares. I tried setting beacon to listen and got an error. Will work with it some more tomorrow. Its in the process of transferring a movie that is @2h11m. Been at it for @1h17m. At current rate, at will be another 11 to 12 hours.

That must be one high, high, high definition show. How large is the file?

Not all that big but:

It is an mp4 and is going to a TiVo 2 so must be trans-coded by a fairly slow computer running Win2K and thus an old version of ffmpeg and is going over the inter-webz. All that results in a transfer time of about 6x runtime.

For "listen" to work, pyTivo has to be able to bind port 2190, which might already have been seized by TiVo Desktop, or the other instance of pyTivo. But you don't really need "listen"; that's just the easiest way to turn off the beacons. As an alternative, I guess you could just put... beacon = some address that you know won't ping you pack, but is actually resolvable. (I was gonna say localhost, but that might not work if something else is binding port 2190, because it will probably respond.)

Actually you can just put "beacon =".

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

For "listen" to work, pyTivo has to be able to bind port 2190, which might already have been seized by TiVo Desktop, or the other instance of pyTivo. But you don't really need "listen"; that's just the easiest way to turn off the beacons. As an alternative, I guess you could just put... beacon = some address that you know won't ping you pack, but is actually resolvable. (I was gonna say localhost, but that might not work if something else is binding port 2190, because it will probably respond.)

Actually you can just put "beacon =".

Not seeing the issue with things as currently configured. If it comes up again, I'll try "beacon = ". Thanks for all of the help. I'm probably the only person who actually care about this particular issue.

Because I still have trouble pulling through shows that are AVI and sometimes MKV (even ones I transcoded), I finally decided to go and get the latest "ffmpeg build". To my surprise it messed-up on me on the first mp4 file I tried to push/bring over to my series 2 TiVo.

Here is what I am seeing: (I believe, I anonymized the files properly enough, taking out passwords and TSNs -- let me know if I forgot something.)

I do have a question about these two specific errors:

Quote:

error: [Errno 10053] An established connection was aborted by the software in your host machine

Thinking of adding a mini to work with the new Roamio and replace one of my Premieres that is in the kitchen.

Anyway, can a mini see PyTivo shares and pull video like the full TiVo it is connected to?

No. To where would you expect it to be pulled? The shares would have to visable to the mini in the NPL of the Premiere being browsed and then pulled to that Premier from whence they could be streamed to the mini. At this point, the only thing I can think of that doesn't involve directly accessing the Premiere would be to use the pyTivo browser interface to push the recording to the Premiere and wait for the xfer to complete.

No. To where would you expect it to be pulled? The shares would have to visable to the mini in the NPL of the Premiere being browsed and then pulled to that Premier from whence they could be streamed to the mini. At this point, the only thing I can think of that doesn't involve directly accessing the Premiere would be to use the pyTivo browser interface to push the recording to the Premiere and wait for the xfer to complete.

So the mini cannot stream the video from the Tivo while it is transferring from the PC to said Tivo?

If not, no minis for me except maybe in a workout room or kitchen where I would never need to watch my movie shares.

__________________Tivo Fanatic since '99!

Roamio Pro
Premiere Elite4
Premiere XL
(3) Minis
Running To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. with To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. and To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

I'm a new user to pyTivo and have watched a few shows I've transferred without issue. But, I transferred one the other day that plays fine but will not let me fast forward. I had stopped the show 1/4 of the way into it and came back to find it was back at the beginning. So, I tried to FF but it doesn't work. This a common issue with some shows and is there a fix for it? Thanks.

I'm a new user to pyTivo and have watched a few shows I've transferred without issue. But, I transferred one the other day that plays fine but will not let me fast forward. I had stopped the show 1/4 of the way into it and came back to find it was back at the beginning. So, I tried to FF but it doesn't work. This a common issue with some shows and is there a fix for it? Thanks.

I transferred one the other day that plays fine but will not let me fast forward. I had stopped the show 1/4 of the way into it and came back to find it was back at the beginning. So, I tried to FF but it doesn't work. This a common issue with some shows and is there a fix for it? Thanks.

This is a common issue with MPEG-1 files (VCD, etc.). pyTivo will generally remux those before sending them; but if you have MPEG-2 video in an MPEG-1 container, pyTivo can't detect the need to remux. The solution in that case is to force pyTivo to remux, by giving the file a bogus container type, via the metadata file:

Override_container: foo

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

This show plays very choppy, meaning when you see fast movement in a frame it appears very jerky like freeze frames. You can also hear garble in the sound. Do you see anything in my ffmpeg that might be causing this? The show plays fine on my laptop.

This is a common issue with MPEG-1 files (VCD, etc.). pyTivo will generally remux those before sending them; but if you have MPEG-2 video in an MPEG-1 container, pyTivo can't detect the need to remux. The solution in that case is to force pyTivo to remux, by giving the file a bogus container type, via the metadata file:

Override_container: foo

Sorry, how do I do that? I tried adding that to Global settings but it threw some error and wouldn't transfer.

EDIT: Nevermind. I deleted it and transferred it again, and now the FF is working properly.

No. But, you might want to try a transfer method that won't reencode the video -- either a push, or a pull with the "ts = on" option added to your pyTivo.conf.

Quote:

Originally Posted by monkeydust

Sorry, how do I do that?

A pyTivo metadata file is a text file with the name of the video file (including the extension), in the same directory*, with the added extension ".txt". This is one of the most fundamental things to know about when operating pyTivo. See: http://pytivo.sourceforge.net/wiki/index.php/Metadata

Quote:

EDIT: Nevermind. I deleted it and transferred it again, and now the FF is working properly.

They say that the definition of insanity is doing the same thing, and expecting a different result. For that to actually work, something is very wrong.

* There are other possible locations, but I'm keeping it simple.

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

I put "ts = on" in the server section of the pyTivo.conf file and no difference detected.

I also found this old thread http://pytivo.sourceforge.net/forum/...und-t1245.html that suggested reincoding the audio to ac3 using MKV2AC3. That worked for the audio. It's clear as a bell but the video is still choppy. I will keep searching to see if there is a fix for the video but I have to wonder why ffmpeg can't make these fixes???

I would hate to have to recode all these files since I have all seven seasons.

Thanks for the help.

ps....

i think from looking at this the ts = on didn't stop it from being encoded. The ac3 is passing strait through but the video is being converted from h264 to mpeg2video from my guess.

Now I can't get pushes to work. They queue but never send to the Tivo. I think this is the problem, any idea what this is saying?

Code:

ERROR:pyTivo.video.video:<urlopen error [Errno -2] Name or service not known>

Edit...

I think I figured it out, I'm not able to resolve mind.tivo.com so I change it to 204.176.49.65 and it worked.

I also noticed I can't use "git pull" to update pyTivo. This obviously has to do with my recent update to ipv6. I can do nslookup and it resolves fine so I wonder if there is a way to force pyTivo to use ip4 instead of ip6?

Edit...

never mind, figured it out, my router had again lost it's ipv6 address. I'm not happy with Comcast and ipv6 and don't know why the router doesn't use ipv4 when it looses the ipv6 address. They got some work to do before the general roll out.

Pushing to the TivoHD didn't make a difference with "ts = on". Looks like it still converted the file.