1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Installing pyTivo on the Mac for Beginners

Discussion in 'TiVo Home Media Features & TiVoToGo' started by bareyb, Feb 21, 2012.

  1. Feb 24, 2012 #61 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Ah I see... You don't HAVE to create the pyTivo.conf file BEFORE you can launch the Web Interface... So that's certainly better... It launches once you get ffmpeg installed in it... Which brings up ANOTHER question... Actually two...

    1. Why isn't the latest version of ffmpeg simply included with the software download too?

    and secondly,

    2. Why isn't a basic working copy (for video anyway) of the pyTivo.conf file included with the Software download?
     
  2. Feb 24, 2012 #62 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Hey hold on... I just realized. There IS NO COPY of ffmpeg in the latest pyTivo download from wmcbrine... Or at least I never added one to the folder (nor did I have to create a "bin" folder within the main folder to place it in). Does that mean he's including it along with the pyTivo download now? :eek:

    THAT would be awesome... Is it true? All I did was throw the folder into my Applications folder and double clicked the new Launcher App Fofer and I came up with. Is that really all it's gonna take now? If so... :up::up::up:

    I'll have to shoot wmcbrine a PM and see what's going on with this latest version.. It SEEMS like he's made it a lot easier to install... I'd like to think I had something to do with that... :D
     
  3. Feb 24, 2012 #63 of 176
    gteague

    gteague golftango

    520
    0
    Apr 1, 2007
    dfw (euless)
    are you sure you don't have another ffmpeg file or folder somewhere else on your system? it's easy to acquire a half-dozen of these as many video-oriented apps use it and one could be on a shared path for any app to utilize. and a spotlight search might not show all of them.

    as to why some of these things aren't included in the packages, that would mean the author would have to be continually checking for the latest version to include--that's a lot of swapping in and out. this way, the user gets to make sure he or she is getting the latest version of the utility.

    /guy
     
  4. Feb 24, 2012 #64 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    I'm not sure. I definitely have a copy of ffmpeg on my desktop... probably some others too after all this. Do you think it's simply finding the other copy and using it? I PM'd wmcbrine and asked him if it was being included now. If he did that, I could almost get rid of this Tutorial.

    Think about it... If it came with a basic working copy of the pyTivo.conf file AND it came with ffmpeg, then all folks would have to do is simply download the folder and then double click the little Launcher App we came up with. BAM it shows up on their Tivo boxes and they are done. :)
     
  5. Feb 24, 2012 #65 of 176
    Iluvatar

    Iluvatar New Member

    377
    0
    Jul 22, 2006
    1. Why would they want to do this? FFmpeg is free and open source and available to everyone. It is not the easiest to build yourself but is available from others and is only a google search away. Also pyTivo is on multiple platforms. Would we provide a 10MB file for each? Windows, OSX, Linux, others. What about CPU's? x86, x86-64, ARM, others.....pyTivo can literally run on anything that Python can which is very extensive. As it is now pyTivo is less than 500KB packaged. With all those FFmpeg files it could easily be 100MB or more.

    2. Video sample settings among others are already provided in 3 locations with pyTivo: pyTivo.conf.dist, pyTivo WebAdmin page provides examples of every setting, pyTivo Wiki provides examples of almost every setting. Projects like pyTivo seek to maximize capability and customization. You can't satisfy everyone so why not provide the user complete control and only provide samples. There are people out there who don't use pyTivo for video but for music and photos only.
     
  6. Feb 24, 2012 #66 of 176
    Iluvatar

    Iluvatar New Member

    377
    0
    Jul 22, 2006
    FFmpeg is not required for pyTivo to operate. It can go perfectly well transferring .Tivo, .mpg and .vob files to the TiVo without it.
     
  7. Feb 24, 2012 #67 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Yeah, but the guy who's writing this software obviously has to have the right version of ffmpeg for pyTivo to work for HIM, (assuming these guys all have TiVos) so why not just save everyone a lot of hassle and simply put THAT version in the download?

    If someone wants to get fancy, they can go look around for other versions, or make their own custom version. For the vast majority of folks I think having it work out of the box would be a welcome addition.

    Side note: I hope none of what I'm trying to do here is misconstrued as disrespect... quite the opposite. I LOVE pyTivo and I just want to see it more accessible to folks who don't have a Unix background.
     
  8. Feb 24, 2012 #68 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Because it would make it "just work" out of the box. All people would need to do is download the folder and double click the little Launcher we created. I didn't realize there were different versions of ffmpeg for different OS's... I suppose that would make it a lot harder. Didn't know that.. thought it was all just "Unix"....
     
  9. Feb 24, 2012 #69 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Wait. WHAT? Then why are jumping through hoops to download it and install the latest version? No disrespect intended, I'm just trying to wrap my brain around all these steps and if they are all necessary nor not...

    Anyway, I'm not the guys who distributes the Software, so it's not my call. I just need to know how to update this thread... Do I still tell people to get the latest version of ffmpeg and add it to a bin folder inside pyTivo or not? :p
     
  10. Feb 24, 2012 #70 of 176
    Fofer

    Fofer XenForo Rocks! TCF Club

    82,090
    286
    Oct 29, 2000
    Because there's lots of video out there that is not in any of those three formats. Lots of .avi's, for example.
     
  11. Feb 24, 2012 #71 of 176
    Iluvatar

    Iluvatar New Member

    377
    0
    Jul 22, 2006
    Due to a multitude of reasons, FFmpeg will probably not be distributed as you want it with pyTivo but instead remain as an addon. It's not my call either. I could decide to provide a copy of it in my fork but that would help all of the 3 people who probably use it (and it would take at least 2 different copies! One for x86 and one for PowerPC for just OS X). I'm content providing updated FFmpeg builds to everyone else. Its availability is described for each of the major platforms in it's respective installation page on the pyTivo wiki. I provide easy access to the OS X version. rdian06 provided the Windows version. Linux.....is more complicated but are still provided instructions on how to obtain it.

    FFmpeg is greatly useful to pyTivo but not required. 95% of people who use pyTivo will want it. Nearly 100% of MY files are NOT in a .Tivo/.mpg/.vob format so FFmpeg is required for MY use of pyTivo but may not be so for someone who only wants to archive their TiVo recordings.
     
  12. Feb 24, 2012 #72 of 176
    wmcbrine

    wmcbrine Ziphead

    10,364
    22
    Aug 2, 2003
    A compiled binary of FFmpeg does not belong in a source code repository. That's what you're all downloading from. A proper, user-oriented distribution of pyTivo would be platform-specific, and could include a compiled FFmpeg. In the past, people have sometimes offered such distributions -- pyTivoX is an example -- but those people have tended to fall by the wayside over time, and currently, no one is doing it.
     
  13. Feb 24, 2012 #73 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    I can see that now. I thought ffmpeg was Cross Platform. It would be hard enough to keep up with just the Mac side, I can see how that could become cumbersome. I guess I'm just grateful somebody is willing to make one for the Mac. ;)
     
  14. Feb 24, 2012 #74 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Either way, big thanks to wmcbrine as this new version seems to be much easier to install since we can now eliminate "Step Four" which is where a lot of folks run into trouble. :up:

    Is this it in a nutshell now?

    1. Download the latest version of pyTivo

    2. Download the latest version of ffmpeg and stick it in the pyTivo folder

    3. Enter the "launch code" into Terminal

    4. Launch the Webpage and finish up there....

    Does that about sum it up?
     
  15. Feb 24, 2012 #75 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    Yep. That's it. Much easier now... Why did you wait until AFTER I'd done the Tutorial to change this? :D
     
  16. Feb 24, 2012 #76 of 176
    gteague

    gteague golftango

    520
    0
    Apr 1, 2007
    dfw (euless)
    well, i found when i went to install it that the actual steps weren't the problem, my problem (and it could have just been me as i tend to hurry and overlook things in my older years) was that i didn't seem to be able to get all the information i wanted in one location and it was hard to try to synthesize the different web sites and wikis and readmes and faqs into one clear, coherent install path. those problems stem from there being old and new versions of documentation side by side. also, i didn't have a clear understanding what components worked with which other components and which components were optional. i'm sure most of this was me trying to read too fast, but still, i'm an ex-linux admin and i still had difficulty, so i can imagine some mac users are completely overwhelmed.

    but now we have the unified bareyb theory of pytivo install which hopefully allows a newbie to just follow the bouncing ball.

    /guy
     
  17. Feb 25, 2012 #77 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    You summed up my problems in a nutshell. It was chaos trying to get all the right bits and getting them all to work on my computer. In the end, my Mac added an invisible .txt extension to the .conf file (a process that has now been completely eliminated in the new version, thanks to wmcbrine), and I'd downloaded the wrong version of ffmpeg. I completely gave up back in 2008 and it's been sticking in my craw ever since. :D

    I plan to stay on top of both of the threads (at the pyTivo forum too) for as long as I still keep getting replies and it appears that people need it. The new version of pyTivo makes installing about 30% easier because it eliminates the need for people to have to create their own pyTivo.conf file before they can get to the Web GUI. Fofer's Launcher makes it an additional 30% easier by not having people entering command lines into Terminal to launch the program. Between the two, we are definitely moving in the right direction in terms of "user experience" which I think is important consideration too. I'm hoping that people won't be as intimidated by it now that there are step by step instructions.
     
  18. Feb 25, 2012 #78 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    By the way, wanted to let you know I fixed the typos too. I'd simply copied and pasted my instructions from the pyTivo.conf file instructions (which ironically are no longer needed) so as to keep the guide language consistent.

    I'm running pyTivo in the background as we speak. I checked my CPU usage (I'm transferring a Movie to TiVo right now) and it's barely using 8% so I guess I'm not having the CPU "hog" issues some folks were complaining about when pyTivo is transferring. Seems to work perfectly. :up:
     
  19. Feb 25, 2012 #79 of 176
    gteague

    gteague golftango

    520
    0
    Apr 1, 2007
    dfw (euless)
    for most of my external video viewing purposes, i find streambaby to be the nearly perfect solution. streams don't take up hd resources on the tivo and they seem to respond to 'scrubbing' back and forth much better than trying to play a transferred video while it's transferring. and if you transfer a file to the tivo, it gets lost in your playing list unless you go to that link posted above a day or so ago and try to get it into a folder. it sounded like voodoo and chicken blood to get that to work!

    but having pytivo for those times i actually need to transfer a file is invaluable. i've been using (or trying to use) toast tivo transfer and tivo desktop prefpane and both those methods need conversion for nearly every file. so now, for a 1.5gb file you've got an hour conversion process (i even got one of those usb stick accelerators by elgato) and then at least an hour transfer. pytivo has transferred every type of video i've thrown at it so far except for avchd (.mts) files which are an unreasonable expectation for any but a cutting edge video system on top hardware to process. i love to hear the windows guys howl when they get a new camera that shoots this format and they can't do anything with it! perverse of me, i'm sure ... but i have that kind of sense of humor.

    /guy
     
  20. Feb 25, 2012 #80 of 176
    bareyb

    bareyb Under Maintenance TCF Club

    25,942
    5
    Dec 1, 2000
    Silicon Valley
    I haven't had a much chance to really try it out since we went Skiing right when I got it working. Now that I'm home, I'm very impressed with it. I just transferred a 45 minute show in about 20 minutes over Wifi and that was with transcoding. That's not bad at all.

    I don't mind having them reside on my Hard drive for awhile, I can always delete them and transfer them again. I have a total of 4 TB in Hard Drive space between my three TiVos so I'm not all that worried about space.

    ETA: Wow that really sucks about Toast... I was considering going that route if I couldn't get pyTivo to work. I guess I'm glad I got it working...
     

Share This Page