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

Streambaby stops working after Pytivo video push

Discussion in 'TiVo Home Media Features & TiVoToGo' started by atomarchio, Jun 21, 2013.

  1. atomarchio

    atomarchio Member

    716
    0
    Sep 24, 2006
    I've had Streambaby working for several weeks on new computer until this evening.

    It starts up as a service and is running. However, it sees the folder, sees the MP4 files fine.

    Then when I attempt to play the file I get "please wait" until a V01 error (service unavailable) appears after several minutes.

    I do have port 7290 open as TCP. This has worked fine for weeks until now.

    Is the issue related to Pytivo push of videos? I am wondering if there could be a conflict between the 2 apps somehow?

    Please help. Thanks.
     
  2. wmcbrine

    wmcbrine Ziphead

    10,364
    22
    Aug 2, 2003
    No, there is no connection.
     
  3. atomarchio

    atomarchio Member

    716
    0
    Sep 24, 2006
    I get that. If I see the Streambaby app "running" as a service and I can view the files, how do I troubleshoot the connection?
     
  4. atomarchio

    atomarchio Member

    716
    0
    Sep 24, 2006
    I tried reinstalling but the issue remains. Here is copy of log file.

    06/22/13 08:04:57 StreamBabyMain$BshLogger: Download ffmpeg for first-run...
    06/22/13 08:04:57 StreamBabyMain$BshLogger: Connecting: http://streambaby.googlecode.com/files//ffmpeg-r15986-gpl-shared-win32.tar.bz2
    06/22/13 08:04:58 StreamBabyMain$BshLogger: Downloading...
    06/22/13 08:04:59 StreamBabyMain$BshLogger: Finished downloading, begin extract.
    06/22/13 08:05:00 StreamBabyMain$BshLogger: extracting: avcodec-52.dll (bin/avcodec-52.dll)
    06/22/13 08:05:00 StreamBabyMain$BshLogger: extracting: avdevice-52.dll (bin/avdevice-52.dll)
    06/22/13 08:05:00 StreamBabyMain$BshLogger: extracting: avformat-52.dll (bin/avformat-52.dll)
    06/22/13 08:05:01 StreamBabyMain$BshLogger: extracting: avutil-49.dll (bin/avutil-49.dll)
    06/22/13 08:05:01 StreamBabyMain$BshLogger: extracting: ffmpeg.exe (bin/ffmpeg.exe)
    06/22/13 08:05:01 StreamBabyMain$BshLogger: extracting: ffplay.exe (bin/ffplay.exe)
    06/22/13 08:05:01 StreamBabyMain$BshLogger: extracting: SDL.dll (bin/SDL.dll)
    06/22/13 08:05:01 StreamBabyMain$BshLogger: extracting: swscale-0.dll (bin/swscale-0.dll)
    06/22/13 08:05:01 StreamBabyMain$BshLogger: Retrieval of ffmpeg complete
    06/22/13 08:05:01 FFmpegJavaVideoModule: Unable to load FFmpeg native libraries
    06/22/13 08:05:01 Listener: added factory
    06/22/13 08:05:01 Main: streambaby ready & listening.
     
  5. moyekj

    moyekj Well-Known Member

    11,140
    29
    Jan 23, 2006
    Mission...
    Start simple and run streambaby in a console instead of as a service and make sure it works that way 1st. Read debugging_problems Wiki for how to get more debug information in streambaby.log.

    If you've updated to Java 7 recently there are some issues running streambaby there according to streambaby thread posts, so you are better off running 32 bit Java 6 version instead.
     
  6. atomarchio

    atomarchio Member

    716
    0
    Sep 24, 2006
    I just followed your instructions.

    The error still appears to be something about "pegJavaConfig$1: Error attempting toload ffmpeg libraries: Unable to load library 'avutil-49': The specified module could not be found."

    I am running Java 6 update 34. 64 bit

    Any suggestions on what I can do at this? I am not sure how to proceed from here.






    06/22/13 13:56:17 StreamBabyConfig: WorkingDir: "C:\Users\streambaby-20120828-2030"
    06/22/13 13:56:17 StreamBabyConfig: StreamBabyDir: C:\Users\streambaby-20120828-2030
    06/22/13 13:56:17 StreamBabyConfig: CurDir: C:\Users\streambaby-20120828-2030\native
    06/22/13 13:56:17 StreamBabyConfig: CoverDir:
    06/22/13 13:56:17 FFmpegJavaConfig$1: Loading avutil, default: avutil-49
    06/22/13 13:56:17 FFmpegJavaConfig$1: Error attempting toload ffmpeg libraries: Unable to load library 'avutil-49': The specified module could not be found.

    06/22/13 13:56:17 FFmpegJavaVideoModule: Unable to load FFmpeg native libraries
    06/22/13 13:56:17 FFmpegExeVideoModule: FFmpegPath: C:\Users\streambaby-20120828-2030\native\ffmpeg.exe
    06/22/13 13:56:17 FFmpegExeVideoModule: FFmpegExeModule: Loaded
    06/22/13 13:56:17 StreamBabyMain: STARTING StreamBaby v20120828-2030...
    06/22/13 13:56:17 Main: args= start=true
    06/22/13 13:56:17 Main: args= loader=sun.misc.Launcher$AppClassLoader@1a45a877
    06/22/13 13:56:17 Listener: config=com.tivo.hme.host.util.Config@787bb290 logger=com.unwiredappeal.tivo.utils.Log$ILoggerImpl@10849bc
    06/22/13 13:56:17 Listener: factoryList=[StreamBabyStreamFactory[/streambaby/,Stream, Baby, Stream]]
    06/22/13 13:56:17 Listener: factory=StreamBabyStreamFactory[/streambaby/,Stream, Baby, Stream]
    06/22/13 13:56:17 Listener: name=/streambaby/
    06/22/13 13:56:17 Listener:
    06/22/13 13:56:17 Listener: added factory
    06/22/13 13:56:17 Main: factory=StreamBabyStreamFactory[/streambaby/,Stream, Baby, Stream]
    06/22/13 13:56:17 Main: MDNS: http://192.168.1.106:7290/streambaby/
    06/22/13 13:56:17 Main: streambaby ready & listening.
    06/22/13 13:56:17 Main: mdns_type=_tivo-hme._tcp.local. factory=StreamBabyStreamFactory[/streambaby/,Stream, Baby, Stream] port=7290
    06/22/13 13:56:23 TiVoListener: addService: BASEMENT
    06/22/13 13:56:23 TiVoListener: Updating service: _http._tcp.local. (BASEMENT)
    06/22/13 13:56:23 TiVoListener: resolveService: _http._tcp.local. (BASEMENT)
    06/22/13 13:56:23 TiVoListener: jmDns found TiVo: BASEMENT, tsn: 746000190AAB5CB
    06/22/13 13:56:23 TiVoListener: addService: HEARTH ROOM
    06/22/13 13:56:23 TiVoListener: Updating service: _http._tcp.local. (HEARTH ROOM)
    06/22/13 13:56:23 TiVoListener: resolveService: _http._tcp.local. (HEARTH ROOM)
    06/22/13 13:56:23 TiVoListener: jmDns found TiVo: HEARTH ROOM, tsn: 746000190729927
    06/22/13 13:56:23 TiVoListener: addService: myrouter
    06/22/13 13:56:23 TiVoListener: Updating service: _http._tcp.local. (myrouter)
    06/22/13 13:56:23 TiVoListener: resolveService: _http._tcp.local. (myrouter)
    06/22/13 13:56:23 TiVoListener: addService: Photosmart Prem C410 series [09818F]
    06/22/13 13:56:23 TiVoListener: Updating service: _http._tcp.local. (Photosmart Prem C410 series [09818F])
    06/22/13 13:56:23 TiVoListener: resolveService: _http._tcp.local. (Photosmart Prem C410 series [09818F])
    06/22/13 13:56:23 TiVoListener: addService: BEDROOM
    06/22/13 13:56:23 TiVoListener: Updating service: _http._tcp.local. (BEDROOM)
    06/22/13 13:56:23 TiVoListener: resolveService: _http._tcp.local. (BEDROOM)
    06/22/13 13:56:23 TiVoListener: jmDns found TiVo: BEDROOM, tsn: 7460001909BD3A5
     
  7. moyekj

    moyekj Well-Known Member

    11,140
    29
    Jan 23, 2006
    Mission...
    Try 32 bit version of Java 6 instead of 64 bit - the ffmpeg dll files are 32 bit AFAIK.
     
  8. atomarchio

    atomarchio Member

    716
    0
    Sep 24, 2006
    That fixed my Streambaby problem. Thanks.

    But now I can't get Pytivo to push video files. It worked fine just prior to this.

    Did the change in Java now cause a problem with Pytivo? I submitted a request to push video files which seems to worked fine. I got the refresh in 5 seconds screen and checked the log. I don't see any errors there.

    Where I can start to find the this problem?
     
  9. atomarchio

    atomarchio Member

    716
    0
    Sep 24, 2006
    Everything else in Pytivo works fine including music, pictures, and I can see the video folders on the Tivo.

    I just read the troubleshooting page and can't see any issues. I am wondering if this java change now caused the problem with Pytivo push?
     
  10. moyekj

    moyekj Well-Known Member

    11,140
    29
    Jan 23, 2006
    Mission...
    They are not at all related - pyTivo uses Python, not Java. You should probably post your pyTivo related issue in the main pyTivo thread along with the pyTivo console output with "debug=on" in your pyTivo.conf file. Unless somehow you configured to use same ports in streambaby and pyTivo there should not be any conflicts between them.
    Note that streambaby has a "push" option as well (though not as robust as pyTivo). See:
    http://code.google.com/p/streambaby/wiki/PushConfiguration
     

Share This Page