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

pyTivo - Transcoding server

Discussion in 'TiVo Home Media Features & TiVoToGo' started by armooo, Nov 25, 2006.

  1. Apr 23, 2007 #361 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    comandercody,

    You still have the outrageously large width and height settings. As I suggested in an earlier post:
    That is unless you have an S3 TiVo with a seriously HD TV attached. :cool:

    Also, you have two different paths in your last video share section, [You Tube].
    I'm not sure what pyTivo does with that but there should only be one path per share.

    I assume you are aware that the pound sign (#) comments out a line, i.e., as far as pyTivo is concerned, the line might as well not be there (?)

    If your TiVo is running software version 8.3, that could explain some of your folder problems on NPL -- Armoo and others are trying to find a solution to this (apparent) bug in that version.
     
  2. Apr 24, 2007 #362 of 5683
    comandercody

    comandercody New Member

    48
    0
    Jun 16, 2002
    Thanks dlfl. I took all the garbage out of the config file. I read that you need an "absolute" path, thats is why that last line was in there, but gone now, thanks again.
     
  3. Apr 25, 2007 #363 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    :D :up:

    Glad I could help out!

    As previously mentioned, the folder "bug" is a known issue now since the 8.3 software update has rolled out. We're all dealing with this in our own way with various workarounds, but none of them are ideal.
     
  4. Apr 25, 2007 #364 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    So I've run into my first transfer problem file with pyTiVo.

    I tried transferring an .avi (Xvid) and I got just a black screen with the audio, no video at all. The audio was fine. I checked and I do have --enable-xvid compiled into ffmpeg. I'm pretty sure I've transfer Xvid before, so maybe it's just this particular file. Any ideas?
     
  5. Apr 25, 2007 #365 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    Yeah, run (at a command prompt):

    ffmpeg -i <avi file name>

    What does it report about the file, in particular the input video stream ?

    If you run pyTivo with debug=true you should get the complete ffmpeg command line used for the transcoding in the debug.txt file. Try running that (modified to have an output file name) and see what warnings you get. The last thing in the command line used by pyTivo is a dash ('-') which causes output to standard output instead of a file. Replace this by your desired output file name (.mpg) or you will have millions of bytes streaming to your command prompt window.

    A different version of ffmpeg may work --- I know this may be a hassle for linux.
     
  6. Apr 25, 2007 #366 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    I can't kick off a transfer from work to try the debug.txt method (will do that tonight) but here's what ffmpeg says about the file:

    Code:
    Input #0, avi, from 'Doctor Who 3x04 - Daleks in Manhattan.avi':
      Duration: 00:46:52.5, start: 0.000000, bitrate: 1042 kb/s
      Stream #0.0: Video: mpeg4, yuv420p, 640x368, 25.00 fps(r)
      Stream #0.1: Audio: mp3, 48000 Hz, stereo, 128 kb/s
    
    I ran this on a file that worked, and it looks about the same:
    Code:
    Input #0, avi, from 'Doctor Who 3x03 - Gridlock.avi':
      Duration: 00:44:59.5, start: 0.000000, bitrate: 1086 kb/s
      Stream #0.0: Video: mpeg4, yuv420p, 640x368, 25.00 fps(r)
      Stream #0.1: Audio: mp3, 48000 Hz, stereo, 112 kb/s
    
     
  7. Apr 25, 2007 #367 of 5683
    ocntscha

    ocntscha New Member

    149
    0
    Oct 22, 2003
    Stupid question, my apology in advance, but sometimes it pays to rule out the obvious..

    Have you played the source file in mplayer or some other video player and verified with your eyes that it does contain usable video?
     
  8. Apr 25, 2007 #368 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    Hmmm... No obvious smoking guns there. Let's see if ffmpeg gives any warnings when you try to run it directly with the command line.

    ocntscha's question is a good one, obviously.
     
  9. Apr 25, 2007 #369 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    Sure, it plays fine in Windows Media Player on my PC. That was the first thing I checked after downloading it. ;)

    I'll try the command-line manual conversion attempt tonight. Thanks guys.
     
  10. Apr 25, 2007 #370 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    Ok, strange.

    I turned on debug and then kicked off the transfer from my TiVo and then stopped it. The debug.txt showed:

    Code:
    video_info:  /home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi  cache hit!
    tivo_compatible:  /home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi  is not mpeg2video it is  mpeg4
    output_video:  /home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi  is not tivo compatible
    video_info:  /home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi  cache hit!
    tsn: 230000080xxxxxx
    aspect169: True
    select_aspect: File= /home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi  Type= mpeg4  width= 640  height= 368  fps= 25.00  millisecs= 2812500  ratio= 173  rheight= 23  rwidth= 40
    select_aspect: 16:9 aspect allowed, file is narrower than 16:9 padding left and right
     -aspect 16:9 -s 1408x720 -padleft 16 -padright 16
    transcode: ffmpeg command is  /usr/local/bin/ffmpeg-i/home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi-vcodecmpeg2video-r29.97-b4096K-aspect16:9-s1408x720-padleft16-padright16-commentpyTivo.py-ac2-ab192K-ar44100-fvob-
    
    Ok, so I took the command-line, put back all the missing spaces (not sure why they were missing) and ran it. Saw normal output:

    Code:
    FFmpeg version SVN-r7788, Copyright (c) 2000-2006 Fabrice Bellard, et al.
      configuration:  --enable-memalign-hack --enable-gpl --enable-pp --enable-xvid --extra-cflags=-I/usr/include --extra-ldflags=-L/usr/lib --enable-mp3lame --enable-x264 --enable-pthreads --enable-faad --enable-faac --enable-a52 --enable-libogg --enable-vorbis --enable-libgsm
      libavutil version: 49.2.0
      libavcodec version: 51.29.0
      libavformat version: 51.8.0
      built on Jan 31 2007 19:16:11, gcc: 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)
    Input #0, avi, from '/home/nas/Videos/Doctor Who 3x04 - Daleks in Manhattan.avi':
      Duration: 00:46:52.5, start: 0.000000, bitrate: 1042 kb/s
      Stream #0.0: Video: mpeg4, yuv420p, 640x368, 25.00 fps(r)
      Stream #0.1: Audio: mp3, 48000 Hz, stereo, 128 kb/s
    Output #0, vob, to 'test.mpg':
      Stream #0.0: Video: mpeg2video, yuv420p, 1440x720, q=2-31, 4096 kb/s, 29.97 fps(c)
      Stream #0.1: Audio: mp2, 44100 Hz, stereo, 192 kb/s
    Stream mapping:
      Stream #0.0 -> #0.0
      Stream #0.1 -> #0.1
    Compiler did not align stack variables. Libavcodec has been miscompiled
    and may be very slow or crash. This is not a bug in libavcodec,
    but in the compiler. Do not report crashes to FFmpeg developers.
    Press [q] to stop encoding
    frame=  155 q=4.1 Lsize=    2914kB time=5.1 bitrate=4645.6kbits/s
    
    Stopped the transcode and played the test.mpg file in Windows Media Player and it was fine! Video and audio ... and yet the file transferred to the TiVo has no video. :confused:
     
  11. Apr 25, 2007 #371 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    windracer
    I see you are encoding to 1440x720. That must be for your S3 right? (This size would not be compatible with other TiVo's and would be overkill also.) As I understand it the Tivo go-back capability is not officially available for S3's. Thus in a way your glass is half full -- i.e., at least some of your go-backs are good. :cool: It is puzzling that two files with apparently identical characteristics behave differently.

    Do you really need the 1440x720 size to get a good picture? Maybe a smaller size would make the difference. Is it known what sizes are native to the S3?

    If I have a problem with an mpeg2, I look at it with mediaInfo, gspot and dgindex, all free programs linked through videohelp.com/tools. mediaInfo is very easy to install and use -- the other two are not quite as easy. Media info and gspot can also be used to look at your AVI files.
     
  12. Apr 26, 2007 #372 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    Actually, I don't think I ever changed those settings in pyTivo.conf and haven't had a problem before. Obviously I'm not sending these to my S3, just to an old S2 (230).

    I'll try playing with those settings tomorrow and see if it helps.
     
  13. Apr 26, 2007 #373 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    First try removing the width and height lines completely. This will default those values to 544 and 480 which seem to be good for most or all TiVo's. I'm impressed your 230 will handle any 1440x720 files. If still a problem enter width=480, then try the other widths listed as compatible in the distributed .conf file. Height should be left at 480 I believe. I recently added to the Wiki section on configuration to try to clarify the width and height settings.
     
  14. Apr 26, 2007 #374 of 5683
    delvxe

    delvxe New Member

    6
    0
    May 28, 2006
    Thank you to everyone who has put together this excellent app. I was skeptical it would work on vista since Tivo Desktop does not and I could not get PipKin's to work either, but pyTivo works perfectly for transferring over my network.

    A couple of questions.

    I have a Humax box with a 595 TSN. It looks like I am having the same transcode problems a few other have had. Transcoded images seem to be overlayed on itself and split into vertal bars and completely whacked (I have a 4:3 television). The videos I have previously transcoded using Videora come across fine. I am going to try altering the config file to 544x480 as inthewoods mentioned in post 173 to see if that works.

    One question, the transferr rate seems to be painfully slow (like 25%-50% of real time). When Tivo Desktop worked before I upgraded from XP, transfer rates were slightly better than 100%.

    Last night I had a copy of a 1hr television show in divx format. When pytivo couldn't transcode it correctly for my tivo I went back to Videora as I have done in the past. When I then tried to transfet it, it was achingly slow. Any thoughts?

    Thanks,
    Terry
     
  15. Apr 26, 2007 #375 of 5683
    etsolow

    etsolow Don't Try

    1,554
    0
    Feb 8, 2001
    Wisconsin
    I had that problem (on a 16:9 TV and a 4:3 TV). Setting aspect169=false fixed it for me.

    E
     
  16. Apr 26, 2007 #376 of 5683
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    That did it! The file is transferring with video now! Thanks!

    I did a little more digging to figure out why this happened. It turns out on 4/19 I "upgraded" to the 187 build. Apparently the pyTivo.conf file has the default height/width lines set to those values and uncommented.
     
  17. Apr 26, 2007 #377 of 5683
    TreborPugly

    TreborPugly Unreal!

    4,542
    0
    May 2, 2002
    Eastern TN
    The default quality setting is fairly high, so you are maybe getting bigger files than videora was making. (What bit rate did you set up videora to do? You can edit the transcode.ty file to give you that bit rate) Look back in the thread where I asked the same question for details.
     
  18. Apr 26, 2007 #378 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    You don't need to edit transcode.py to change the bit rate --- it is a configurable parameter in the pyTivo.conf file, in the [Server] section, e.g.:
    video_br=4096k (or 2048k, etc.)
    If this is not in the file, it defaults to 4096kbps. Unless you have a very slow PC or network, you should be able to transfer faster than real time with this rate.

    Also, check the width and height settings --- see this post.
     
  19. Apr 26, 2007 #379 of 5683
    TreborPugly

    TreborPugly Unreal!

    4,542
    0
    May 2, 2002
    Eastern TN

    Sorry, right, this was added as a config option after my post about this. (I haven't updated, since everything's working fine for me right now - if it ain't broke... :))
     
  20. Apr 28, 2007 #380 of 5683
    dlfl

    dlfl Cranky old novice

    6,997
    17
    Jul 6, 2006
    Near...
    Finally got my "Spring" update last night and sure enough -- subfolders are broken in pyTiVo.

    If you check out the timeline in the wiki you see that Armooo has been attacking this problem and in fact has a version of video.py checked in (Changeset 192) that does seem to handle one level of subfolders -- but note his other comments about it, and it hasn't been included in a "release" download.

    I downloaded this version of video.py and put it in my pyTiVo 187 installation. It did handle one level of subfolders (I don't have any 2-level subs). :cool:

    Thanks Armooo!
     

Share This Page