Relative path seems to work fine - I think the problem might (just a guess) be the windows formatted path "\" instead of "/" ... just a guess. I had no problems at all getting images to display on ubuntu box using image : images/my_image.jpg (my images are in subfolder named "images" below the actual video file.)

Click to expand...

Okay, I still haven't been able to get the images to work with a .txt metadata file, and the .html file doesn't display anything at all - the info screen is blank.

Can someone please post or email me a real metadata file, txt or html (preferrably both), that they *know* works? Streambaby is running on an XP box, if that matters.

I am still trying to wrap my head around the metadata usage with streambaby. I have a pretty good understanding of how the tivo.xml and pytivo.txt metadata files work and even a basic understanding of what happens with the xml transformations.

What I want to do is manually generate an html metadata document for each video file and use that as my metadata file. The reason I want to this is that my streambaby is running on a very old PC running Ubuntu 9.0.4 and I like to optimize as much as possible the processes. When using a standard pytivo.txt or tivo.xml metadata file - there is a significant pause before generating the Info screen displaying the metadata. I can only assume this is from the overhead required to parse and transform the raw metadata to the html for used by streambaby. Hence the reason I want to manually create the html metadata files - thereby skipping the xml transformations occurring in streambaby.

The problem I am having is nothing to do with streambaby - but more with the xml transformations. I can't seem to get a grip on writing the xslt required to transform the raw metadata into a finished html format I can use on the server. I have been scouring the internet for xslt tutorials etc, but still am having no luck.

Does anyone have any suggestions on how I might go about converting the raw metadata (either tivo.xml or pyTivo.txt) into a usable static html metadata file.

...there is a significant pause before generating the Info screen displaying the metadata. I can only assume this is from the overhead required to parse and transform the raw metadata to the html for used by streambaby.

Click to expand...

Before you get too deep into this I would just make sure the pause is really caused by the XSLT transformation and not the HTML->jpg transformation. It could be either or both that is causing the pause. (Most likely both...)

If I remember correctly the XSLT transformation is pretty slow the the first time it generates the info screen, but is quicker for the next movie info screen. The XSLT is compiled the first time around and then is cached and used for all subsequent info screen metadata operations.

Before you get too deep into this I would just make sure the pause is really caused by the XSLT transformation and not the HTML->jpg transformation. It could be either or both that is causing the pause. (Most likely both...)

If I remember correctly the XSLT transformation is pretty slow the the first time it generates the info screen, but is quicker for the next movie info screen. The XSLT is compiled the first time around and then is cached and used for all subsequent info screen metadata operations.

To create hb2.html from hb2.xml, where /tmp/hb2.xml is TiVo format XML metadata. It does print some warnings but the resulting HTML seems OK. (I didn't look into the warning it was giving, but it's probably some XSLT feature that is not supported by xlstproc)

The first transform (tivo-pyxml.xsl) transform the TiVo format XML into a pseudo pyTivo format XML (if you look at the output you will see what I mean). The second transform (pytivo-html.xsl) takes the pseudo-pyTiVo XML and transforms it to HTML.

You can copy the xsl files to something else (so you don't break streambaby ;-) and then edit it to be more in line with what you are looking for.

As far as the actual XSLT I probably can't help too much-- It's a miracle I got what I did working for streambaby (with a lot of help from the thread...)

If you do use this method and slowness does not end up being a problem (so you don't need the static HTML files) you can just replace pytivo-html.xsl with your new versions to get a customized info screen.

Sorry if I am answering a part of the process you already knew the answer to-- I think the key to the process above is the first transform simplifies the TiVo format XML into something a little easier to deal with (the pseudo pyTivo format XML)

Thanks kearygriffin. I was alreayd working with that process a bit but for some reason - must be an xslt error - only partial data is transformed (Title and description). I have been playing around with editing the pytivo-html.xsl (the tivo-pyxml.xsl is fine), but am having a heck of a time (xml/xslt is not my forte). I was hoping someone more knowledgable in xml/xslt might chime in here and offer some help. Well maybe someone will see the post and chime in. Thanks for the suggestions.

To create hb2.html from hb2.xml, where /tmp/hb2.xml is TiVo format XML metadata. It does print some warnings but the resulting HTML seems OK. (I didn't look into the warning it was giving, but it's probably some XSLT feature that is not supported by xlstproc)

The first transform (tivo-pyxml.xsl) transform the TiVo format XML into a pseudo pyTivo format XML (if you look at the output you will see what I mean). The second transform (pytivo-html.xsl) takes the pseudo-pyTiVo XML and transforms it to HTML.

You can copy the xsl files to something else (so you don't break streambaby ;-) and then edit it to be more in line with what you are looking for.

As far as the actual XSLT I probably can't help too much-- It's a miracle I got what I did working for streambaby (with a lot of help from the thread...)

If you do use this method and slowness does not end up being a problem (so you don't need the static HTML files) you can just replace pytivo-html.xsl with your new versions to get a customized info screen.

Sorry if I am answering a part of the process you already knew the answer to-- I think the key to the process above is the first transform simplifies the TiVo format XML into something a little easier to deal with (the pseudo pyTivo format XML)

...The program being watched just dropsout back to live TV. Streambaby remains connected, but it is necessary to go back via the folders to the movie and resume....

Click to expand...

If I had to guess I would say it has something to do with the TiVo timing out because of inactivity-- Streambaby has code to handle this (so it doesn't time out), but for whatever reason it doesn't seem to be doing the trick for you.

I don't want to jump to conclusions, but because I haven't heard of this issue before, it's conceivable it's some kind of issue specific to Australian TiVo's.

You can try a couple of things:
1) Try pressing "play" (or info, or anything else) every 5 minutes or so and see if that keeps the TiVo from timing out.
2) Try turning on extra debug information in Streambaby and see if there are any clues just before the TiVo "drops".http://code.google.com/p/streambaby/wiki/debugging_problems

I am trying to get Streambaby working with VUZE converted files on a WinXP PC, but the streambaby will not show up in either TIVOs.

They are both TIVO HDs. Then I stumbled onto this POST and thought I would try getting Streambaby working. Which I did after playing around with PATH statements until I got it to use Java 1.6 instead of 1.5 as it was erroring out.

So now Streambaby is running, but was not sure if I needed anything else with that running, or if the IP to configure was the IP of my PC?

Anyways Streambaby is not showing up in the TIVO either. I would love to be able to stream through the TIVO just like my XBOX or atleast download through VUZE. I tried restarting the TIVOs to see if they needed a reboot, but NO GO.

Does Streambaby or VUZE need Tivotogo installed on the same PC or any other requirement in order to show up on the TIVO?

I just installed Streambaby .25 on my Windows XP box. It runs from the command line with no errors, but I cannot see it at all from my TiVo in the Music, Photos, and Showcases menu. These are the only two lines in my ini file:

dir.1=d:\Movies
dir.1.name=Movies

I also have TiVo Desktop running, but no ports are overlapping. I tried turning off TiVo Desktopand restarting streambaby, but that didn't help. I can browse to my tivo's IP and I see the Congratulations! message. I can see TiVo Desktop just fine from my TiVo, so I know that PC-to-TiVo communication is OK. I do a netstat -a -n and I see port 7290 listening.

Any ideas?

Click to expand...

I know this is an old post, but for those who were trying to help me, I resolved my issue. I replaced my new TrendNET TEW-852BRP wireless router with a Linksys wireless router I found at a thrift store and Streambaby came right up. That TrendNET router was a POS and I highly recommend staying well away from it. DD-WRT doesn't support it, either. However, DD-WRT runs nicely on the Linksys.

Of course with the Snow Leopard update comes a 64-bit JVM. Is streambaby optimized to use this?

I boot my mac into 64-bit mode and would love it if streambaby were to perform better with the 64-bit optimizations.

I know it loads ffmpeg.bin so i don't know if that is optimized for 64-bit or not.. I have compiled ffmpeg and all its required libraries as 64-bit and it seems to give a large performance gain when transcoding (7-9 fps in 32-bit vs 21+ in 64-bit with the exact same settings). Most of this coming, (I have seen) from the correct compilation of libx264 for 64-bit. This enables the following on the processor (on the MBP unibody)

From my experience with engineering software in general 64 bit binaries run slower or same speed as their 32 bit counterparts, so unless we need access to >4GB RAM we try and use the 32 bit versions as much as possible. Of course a lot of it depends on the software itself and what libraries it uses etc.