Separate names with a comma.
Discussion in 'TiVo Home Media Features & TiVoToGo' started by kearygriffin, Jan 20, 2009.
I don't think the TiVo can handle 15 fps. You might have to force it to be transcoded.
wow, this is nice. I liked tivostream, but the transcoding and positioning take it to the next level.
Should it be possible to transcode and play mjpeg avi files? I tried a few clips from my digital camera but I just get an stream failed message on the tivo and no error messages on the streambaby console or log.
Also, I got a couple of crashes when trying to play some wmv files with the JIT complaining about something. I have not be able to reproduce it since, but will capture the exception if I see it again.
Still can't get this to run on my desktop, yet was able to get it going on my laptop. When I run the application the window opens and closes quickly yet never scans video directory with ffmpeg as it did on my laptop. I checked my firewall and made sure the port was open(TCP Outgoing). In my task manager it shows StreamBaby is running. I have Java 1.6 on both computers. I am running Galleon and Pytivo on my desktop though and not on my laptop. Any ideas.
Works for me now.
The play bar is noticeably off-center.
Edit streambaby.ini and change port from 7288 to something else as on your desktop that port is likely already in use. If still not running then start "cmd" window and start streambaby.bat script from there so you can see the error messages.
How should the script be typed in the command window?
At a DOS prompt from the directory you've installed streambaby to, just type streambaby.bat and press Enter.
Thanks for all your efforts- If it makes sense and you are still willing it may make sense to hold off and get on IM at some point while your testing and I can make changes on the fly as necessary for debugging/trying new things etc. I'll also put together an initial version that dumps out lots more information about trying to load the libraries. Right now a lot of the exceptions are trapped, as not being able to load the native libraries is considered a normal (although not optimal) thing. It may help for me to dump the stack traces.
The other option you mention of just shipping with ffmpeg and forgetting about the native-libraries is also a very acceptable option.
I'll have to add checking (after I fix the fact that streambaby often doesn't parse the fps correctly) to force streambaby to transcode videos with incompatible FPS. I haven't tested it, but I am guessing the tivo can basically handle all of the standard mpeg-2 frame rates(?)
One other currently incompatible video type that people might notice (the symptom is getting audio-only, no video) is MP4's marked as H264 Level 5.1. The tivo only supports upto level 4.1. I'm debating what to do about this, but my gut reaction tells me to just patch the moov header to lie to the TiVo and tell it is a Level 4.1 stream. My guess is that 99% of all H264 MP4 files that are marked as Level 5.1 really don't need to be.
Question to any mac user who has tried streambaby:
Are you successfully loading the dynamic libs?
(I'm trying to figure out if/what I'm doing wrong)
This may be a dumb question - what would be the symptoms if my streambaby was NOT loading the dynamic libs? Would it not run at all, or would there be some specific error/warning reported? I'm asking because, as far as I know, streambaby is working for me - but I'm mostly streaming mp4s that don't need transcoding.
It would work fine (it would use ffmpeg the binary to generate the FF images), but if you enable the full logging you would see that it is not using the libraries.
To change the logging, edit the file 'simplelog.properties' in the streambaby directory, and change
Then look at streambaby.log. In there it somewhere in the first twenty lines you should see "FFmpeg-Java module loaded"...
Okay, I've done this - and the libraries are not being loaded in my case either.
I assumed I needed to add the following lines to my config, so it knew where to find my fink libraries:
yeah I think that's the intent. Ok so I guess it's time to go in and debug the code as opposed to my configuration/build of ffmpeg... Thanks
Once thing I've noticed with both tivostream and streambaby - for the first 10 seconds or so of a video I'll see either colored blocks or else pieces/entire scenes from a previous stream I'd been watching.
If I use pyTivo to view any of the videos, there are no problems at the beginning or anywhere else.
I see the same thing ... almost like the stream isn't "all there" but eventually it all "fills in."
That's only the case for .mp4 files from what I've seen. I think the Tivo mp4 decoder hardware has it's own buffer that is not cleared out and still contains data from previous stream and that needs to empty out before it starts showing the new content properly. I could be wrong but this effects seems to be worse in 11.x versus 9.x software.
That would fit what I've seen - I hadn't noticed it with other streamed media (does that get transcoded to mpeg2 rather than mp4?), but most of my stuff is already mp4 so I see it a lot.
Windracer - glad to hear it's not just me!
So maybe we need the option to pad the beginning of every stream with ~ 10 seconds of black screen?
pyTivo transcodes any non-mpeg2 to mpeg2 which is why you wouldn't see this issue with it.
Sorry I wasn't clear - what I meant was: Does streambaby (and tivostream) transcode non-mp4 materials to mpeg2 rather than mpeg4? I'm just wondering why, if the problem is at the Tivo end, we only see it if we're streaming mp4s.