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

Streambaby - new streaming application

Discussion in 'TiVo Home Media Features & TiVoToGo' started by kearygriffin, Jan 20, 2009.

  1. Jan 30, 2009 #301 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    Is this only the case with transcoded files? (In particular transcoded using a quality other than SAME). Or do you get the distortion with "Same" transcoding? (With qualities other than same I specify a scaling. For SAME I don't tell ffmpeg anything about the aspect/scaling)

    I know moyekj reported something similar with some WMV files, and I never did figure out what was happening.
     
  2. Jan 31, 2009 #302 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    It would help if you could isolate this to galleon->streambaby interaction or a bug in streambaby... Can you run streambaby manually? do you still get the error?
     
  3. Jan 31, 2009 #303 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    This is entirely for transcoded files (I don't have many movies that are streamed, but I can try to track down some h264/ac3 mp4s to test it with).

    This is true for both 'same' and 'high/medium/etc'. i.e. If you don't supply a resolution to scale it to, the original movie resolution is still being stretched. when you do supply a resolution, you're always using 'original resolution' or a 'constant multiple for both x and y', so it's still stretched the same way.

    The files I'm toying with are mkv files h264/ac3. Although it doesn't seem like the container format matters...

    I'm wondering if a 'fix' might involve doing something like:
    high = 1920x1080
    medium = 720 x 400
    low = 640x360

    (or something like that) and always rescaling to those values?
    Out of interest.. are you not seeing this at all? not even 16:9 movies getting letterboxed?
     
  4. Jan 31, 2009 #304 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    I mostly have MP4 files. Even the MPG&AVI files that I use for testing are transcoded from my MP4 originals.

    And just to make sure, is the ffmpeg -i information you put in your post from the same ffmpeg that streambaby is using?

    The reason I ask is I have an anamorphic wmv file, and my older ffmpeg prints out the correct info, but a new (mid december version) doesn't print out the aspect ratio. I'm compiling todays ffmpeg SVN to see what it says.

    And just to note, streambaby calculating the wrong aspect is not critical, as it is only currently used to generate a correct aspect thumbnail, but it could be a clue as to the problem.
     
  5. Jan 31, 2009 #305 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    Wow, ok my bad!

    It looks as if the tivo had the output display set to "smart (SD=4:3, HD=16:9)" and that was causing both 4:3 to fill the output (and the amp would stretch it) and made 1.66 show up squished. When ffmpeg was expanding everything to 1080, then of course it was always using 16:9 and always looked right...

    So, everything is 'working as it should be'... My bad for taking so long to realize this, and sorry :)
     
  6. Jan 31, 2009 #306 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    Thanks, downloading now. I'll take a look in the morning.

    I fixed the issue with streambaby not calculating the correct aspect ratio, it had to do with different versions of ffmpeg. (Just pushed that version to SVN). But like I said, that was a bit of a side issue. (but having streambaby calculate the correct aspect ratio may help in eventually solving the issue, because I can force ffmpeg to do what I want)

    I think TiVo does the correct thing when it gets the correct information. I have various videos that work correctly in 4:3, 16:9 and whatever it is that movies are shown at, even when I transcode them.

    I think the problem with just specifying various resolutions to ffmpeg, is that I am pretty sure we will find that videos that would have played correctly will start having the wrong aspect ratio. (So playing a 640x480 movie with a pixel aspect ratio of 1:1 which used to play correctly will start getting stretched to 16:9, for instance)
     
  7. Jan 31, 2009 #307 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    YIKES! My bad!!!

    The program is working as intended.

    Long explanation: The whole stretching stuff was entirely my fault. I had my video/TV aspect ratio set to "Smart (16:9 hd, 4:3 SD)", which made some streams use a 4:3 display (causing 1.33 to fill the whole screen, and 1.66 to add bars above/below). Those were then stretched by my amp to fill up my 16:9 display. When I rescaled using ffmpeg to 1920x1080, it was using the HD half, and so was getting sideboxed/letterboxed correctly.

    So.. Gah. Sorry to waste your time. Hopefully this will catch some other people's worries about unexpected stretching.

    Also, while debugging this, I noticed that the 'aspect' button does not work while viewing a stream (nothing you can do about it -- but it does mean when we tell people to make sure they have aspect set to 'panel' we tell them to do it while watching live TV or something).
     
  8. Jan 31, 2009 #308 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    I think you edited a previous message instead of posting the first time. It really confused me when I saw that post. Couldn't figure out why in one message you were saying it was OK and in the next still having problems (and how could I possibly have missed a post hours ago about things working ;-)

    From looking into this I think the one problem that may crop up (but I think it will be rare) is that mpeg-2 only supports:
    1:1
    4:3
    16:9
    221:100

    So any other aspect ratios will be scaled to the closest in that list. I probably won't bother trying to work-around this (I could probably figure out a way tell ffmpeg to generate letterboxing/pillarboxing for off-aspect videos), as most videos will be close enough to one of these ratios that it wouldn't even be noticeable. (for instance your 1.85 or 1.66 both get scaled to 1.77). I have a feeling that my work-arounds would end up being more problematic than the original issue.

    EDIT: I think I'm wrong. I have no idea what aspect mpeg-2 supports, but a quick test shows it's more than I thought. (I was going by my reading the ffmpeg mpeg encoding code, but I must be misinterpreting it)
     
  9. Jan 31, 2009 #309 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    In some 'good' news. Can you please add '.mov' as yet another valid default file extension? I changed the config file to add it as an extension and it's working fine. (it's transcoding although it ID's it as an mpeg-4 container, so I suspect if I had a h.264/ac3 .mov file, it would try to stream it instead).
     
  10. Jan 31, 2009 #310 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    Either way not much to worry about. It doesn't have to be perfect. stretching 4:3 to 16:9 would be bad, but that's not what we're talking about here :)

    Thank you again btw..
     
  11. Jan 31, 2009 #311 of 3405
    Sicklybutsexy

    Sicklybutsexy New Member

    179
    0
    May 5, 2007
    I've noticed a problem in fast-forwarding within an mpeg (a streamable one). I went to go to the movie at the 25 minute mark and it did, the frame was the 25 minute mark. However, the seek bar shows that it is at the 1 hour and 2 minute mark. Seems as if the bar is incorrectly displaying the actual point in the video we're actually watching.
     
  12. Jan 31, 2009 #312 of 3405
    Sicklybutsexy

    Sicklybutsexy New Member

    179
    0
    May 5, 2007
    Not only that, the seek bar was saying the movie was 2 hours and 25 minutes long when it is actually 1 hour 48 minutes long.
     
  13. Jan 31, 2009 #313 of 3405
    Emillion

    Emillion New Member

    24
    0
    Oct 19, 2007
    The error occurs when trying to play a file (mp4, mpg, avi - same error)...
     
  14. Jan 31, 2009 #314 of 3405
    windracer

    windracer joined the 10k club

    11,580
    3
    Jan 3, 2003
    St. Pete, FL
    I had this too the first time I tried too and it was because I mistyped my path for the streambaby.dir setting. if you check the wrapper.log, you'll probably see something about it not being able to find blue.jpg (the background image which is under the assets folder).
     
  15. Jan 31, 2009 #315 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    Hmm, I really don't know- I just tried 0.20a on Vista agin, and didn't seem to have any problems.

    It might (and might not...) help if you could do the following.
    edit simplelog.properties and change the first line to:
    com.unwiredappeal=debug

    Then rerun streambaby, try to play a video. After the crash if you could somehow get me the log streambaby.log file, that would be great.

    Thanks
     
  16. Jan 31, 2009 #316 of 3405
    jasa

    jasa New Member

    23
    0
    Nov 5, 2008
    Earth
    kearygriffin I just wanted to know when will you upload newer fixed version of.20 ???

    I just saw on google code that there has been some changes in somefiles
     
  17. Jan 31, 2009 #317 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    There are no major changes in the SVN version, just a couple of bug fixes for determining aspect ratio. (And streambaby doesn't really use the aspect ratio it calculates, so no one but me will really know the difference)

    What problem are you looking to get fixed? If you are talking about funny voices in the FLV, I can take a look, and it's possible I am doing something wrong, but I have a feeling there is not much I am going to be able to do. (Either ffmpeg transcodes it OK, or it doesn't).

    If it is getting more filetypes supported, just add this line to streambaby.ini:
    extensions=mp4,mpeg,vob,mpg,mpeg2,mp2,avi,wmv,asf,mkv,tivo,m4v,m4a,raw,3gp,mov

    and add whatever additional extensions you want. (In the list above 3gp and mov are new and not in the current default)

    I don't check anymore if i think ffmpeg can convert it, I just throw the file at it, so you should be able to add any extension you think ffmpeg can handle.

    Keary
     
  18. Jan 31, 2009 #318 of 3405
    Yoav

    Yoav New Member

    1,048
    0
    Jan 12, 2007
    'fixed' version? 0.20 isn't broken for me... (it has bugs, but that's normal for anything under active development). If you want the latest code as he's editting it, you can always follow the instructions at http://code.google.com/p/streambaby/source/checkout
    Then build it by running 'ant' in the toplevel...
     
  19. Jan 31, 2009 #319 of 3405
    westside_guy

    westside_guy Annoyingly ephemeral

    462
    1
    Mar 13, 2005
    The soggy...
    Quick question - is there any reason I can't run two instances of streambaby on the same computer, as long as they're outputting to different ports? I'm comparing some issues I have with 0.20beta against how things worked in 0.19a, and it'd go faster if I could run them simultaneously - but I know apps don't always handle that situation gracefully.

    Right now I am killing one instance before launching the other, just to be safe...
     
  20. Jan 31, 2009 #320 of 3405
    kearygriffin

    kearygriffin New Member

    346
    0
    Jan 31, 2008
    Shouldn't be a problem as long as you change ports (and changing title= would make things a bitter easier also).
     

Share This Page