Separate names with a comma.
Discussion in 'TiVo Home Media Features & TiVoToGo' started by Yoav, Dec 10, 2008.
Isn't the latest Java 8 Update 71?
I am not technical and have downloaded PyTivo and PyTivoX. I downloaded PyTivo and used the command line after PyTivoX stopped working (Mac OS upgrade?). Ironically, I now have PyTivoX working. Two questions:
1. It asks if I will allow Python... Saying "yes" let's the application work.
2. The resolution isn't great. How do I fix this? I assume something to do with a newer version of FFmpeg.
I am using a Roamio Plus and running El Capitan on a MacBook Pro.
And your question is...?
Nope -- a newer version of pyTivo. The one bundled with pyTivoX is too old to recognize the Roamio as an HD unit, so it falls back to SD transcoding.
Thanks wmcbrine. So my question is how to upgrade the pytivo within pytivox. I like the UI and ability to launch like a "real" Mac app. Not sure where to put which files in which directories, etc.. Like I said, not technical.
I tried upgrading ffmpeg but I'm sure I mangled that attempt.
Oh, yes, the python question. Is there a way to NOT have it prompt me for approval? Just have it happen behind the scenes?
Thank you for help with all of these questions.
I am not technical but have been loving pyTivoX with my Series 2 Tivo for years. I'm running my Mac with El Capitan and it's been working great with mp4 and avi files but it can't seem to handle mkv . Once in awhile it will actually work but usually transfer stops at about 2 min mark and it thinks it's done. Now unfortunately seems that everyone is switching releases to mkv format. Is there anything (simple) I can do that might help it work? Upgrading Tivo is not an option - I'm in Canada where Series 2 is last version supported because our cable companies will not use video cards. Please anything anyone can suggest would be very much appreciated.
You might try a newer ffmpeg.
Hi. I'm still looking for answers to my questions, please.
Is there a way to insert a new version of FFMPEG into a working installation of PyTivoX? Everything works fine but the resolution isn't great.
Also, when I launch PyTivoX I get asked if I want allow or deny python?
Longtime PyTivoX user. But I'm a brand new Tivo Mini owner so you can guess my next question. The Tivo Mini sees my PyTivo shared folders on my Mac, but it says "You cannot watch shows from your computer on this TiVo device" when I try to view any shows from my Mac on the Tivo Mini.
Soooo, question is, is there any workaround?
I just went through this as I transitioned from PC to Mac.
Here's how to put the latest pytivo and ffmpeg to pyTivoX (assuming you've already installed pyTivoX):
1) Download the latest version of wmcbrine's pyTivo:
GitHub - wmcbrine/pytivo: pyTivo is both an HMO and GoBack server. Similar to TiVo Desktop pyTivo loads many standard video compression codecs and outputs mpeg2 video to the TiVo. However, pyTivo is able to load MANY more file types than TiVo Desktop.
a) Download the zip file.
b) Unzip it, it creates folder pytivo-master.
c) Rename pytivo-master to pyTivo-wmcbrine (because this is the folder name that pyTivoX uses).
d) In Finder, locate where you have pyTivoX.app (ie I have it in /Applications). Right-click on pyTivoX.app, and choose "Show Package Contents"
e) Go to the Resources folder.
f) Notice the folder "pyTivo-wmcbrine" - rename it or delete it (that's the old version).
g) Copy the new version of the "pyTivo-wmcbrine" folder from step (c) to that Resources folder.
2) Download ffmpeg for OSX:
I had transport-stream remuxing problems on pulls using the latest version, and from another thread here I used the recommended version 2.2 instead of the latest version.
a) Download the dmg file
b) Open it
c) From the pyTivoX.app/Contents/Resources folder from the pytivo step above, rename or delete the existing ffmpeg and ffmpeg.bin files.
d) Copy the ffmpeg executable from the downloaded dmg to the pyTivoX.app/Contents/Resources folder.
3) Start pyTivoX.app by double-clicking it.
4) Go to the pyTivo config webpage: http://localhost:9032/
5) Click Settings - Global Server Settings, and look at the ffmpeg setting. Update it to the location that you put the new ffmpeg, if it's not already, ie /Applications/pyTivoX.app/Contents/Resources/ffmpeg
6) Save changes, stop pyTivoX and restart it.
FYI if you're familiar with editing the pytivo.conf file manually, for pyTivoX it's located in ~/Library/Application Support/pyTivoX
Thanks for that write-up, @Spenner! Very much appreciated.
Question: Step 2c instructed us to delete or rename both "ffmpeg" and "ffmpeg.bin" files but step 2d did not mention replacing "ffmpeg.bin", and there was no "ffmpeg.bin" in the v2.2 .DMG file. My original Global Server Settings file was showed the full path pointing to "ffmpeg.bin". Is it OK to point it to just the "ffmpeg" file (no ".bin") instead??
Answered my own question...it seems to be working! FYI if anyone else tries this, be sure to check your Mac OS version and be sure to download the correct ffmpeg 2.2 for your particular operating system version.
I deleted the bin file, leaving only the new ffmpeg file, and pyTivo/pyTivoX transfer fine. With your "python quit..." crash, is that with the global server setting saved using the path to the new/plain ffmpeg file AND restarting pyTivo? I'm on macOS Sierra, don't know if that makes a difference.
I'm on an old Mac Mini running 10.7 and I had downloaded an ffmpeg for 10.8 or newer...that's probably why the crash. In my case it was a "DUH" moment! Once I got the correct ffmpeg there it seems to be working OK. Thanks for the fast response!
Thank you so much! I will try! Lately I've been streaming to my Apple TV instead of moving files to my Tivo but I prefer the second.
Thanks Spenner, those instructions worked just fine for me. I did notice the ffmpeg vs ffmpeg.bin issue MacBrian mentions above. I copied ffmpeg to ffmpeg.bin, being that's what the pyTivo config references (ffmpeg is just a shell script that adds that directory to the DYLD_LIBRARY_PATH, but ffmpeg doesn't reference any of the shared libraries in that folder, it looks like they're statically linked). Anyways, everything seems to be working, so thanks!