|
| Author |
Message |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sun Sep 07, 2008 11:50 am Post subject: |
|
|
Also, simply following your instructions at
http://pytivo.krkeegan.com/pytivo-stopped-working-t412-15.html#3256
didn't work to allow me to enable the service. I could run the console, but not the service.
After I copied pyTivoService.exe...and...crap, sorry, another pyTivoService.* file I was able to start the service. |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Sun Sep 07, 2008 12:28 pm Post subject: |
|
|
My bad, I'll update the instructions. Seems krkeegan's installer does some extra magic to install those because they don't show up in his git fork. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sun Sep 07, 2008 1:05 pm Post subject: |
|
|
| Not that it matters at this point whether I'm running it via console or service... |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Sun Sep 07, 2008 4:47 pm Post subject: |
|
|
In your pyTivo.conf, change your beacon line under the Server section to the specific IP of your Tivo box which I believe you said was 192.168.0.2, so:
| Code: | beacon = 192.168.0.2 |
There are reports from others saying that the default beacon isn't working and setting the beacon to the specific IP(s) should fix it for now. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Sun Sep 07, 2008 6:26 pm Post subject: |
|
|
Thanks for not giving up on me.
Unfortunately, the specific beacon trick (the first thing I tried, actually) doesn't do it. I've tried it variously through this process, and I did it again in response to your suggestion.
.2 is my server.
.8 is my Tivo. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Mon Sep 08, 2008 4:31 pm Post subject: |
|
|
Hey, uh, I got home from work today to find that my pyTivo is working!
Thanks so much for all your help.
rj |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Mon Sep 08, 2008 5:13 pm Post subject: |
|
|
Here's a long shot.
Shutdown pyTivo, then edit your pyTivo.conf and add this to your Server section:
Make sure you have your beacon line still set to just your Tivo's IP address, then start pyTivo.
See if that works. |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Mon Sep 08, 2008 5:14 pm Post subject: |
|
|
| urge wrote: | Hey, uh, I got home from work today to find that my pyTivo is working!
Thanks so much for all your help.
rj |
Ah, cool. Maybe the beacon line worked, but you just needed to wait for the Tivo to refresh. |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Mon Sep 08, 2008 5:15 pm Post subject: |
|
|
| Wait, did you misread what I said? It's working now! |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Mon Sep 08, 2008 5:16 pm Post subject: |
|
|
Nah, I had started my post and then got distracted. Meanwhile you posted your success and then I finally hit the submit button  |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Mon Sep 08, 2008 5:19 pm Post subject: |
|
|
| Now to see if I can make my mp3s show up. Do I need to install a plugin or something? |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Mon Sep 08, 2008 5:29 pm Post subject: |
|
|
No extra plugin needed. The music plugin is builtin.
However, the music share shows up under the Find Download something or other.
Also, if you're using the latest wmcbrine fork, the music player may have a slight problem. There's a line of code that needs fixing for it to detect the right song duration. I've been meaning to tell wmcbrine about it, but I keep forgetting.
Shutdown pyTivo.
Open pyTivo\plugins\music\music.py in your favorite text editor and change the following line:
| Code: | durre = re.compile(r'.*Duration: (.{2}):(.{2}):(.{2})\.(.),').search |
to
| Code: | durre = re.compile(r'.*Duration: ([0-9]+):([0-9]+):([0-9]+)\.([0-9]+),').search |
Be careful not to change the spacing before the line at all, save and restart pyTivo.
That's the important fix otherwise fastforward/rewind and the time estimation won't work.
There is another small fix where the milliseconds are slightly off, but it really doesn't affect things.
Last edited by rdian06 on Mon Sep 08, 2008 5:50 pm; edited 1 time in total |
|
| Back to top |
|
 |
urge
Joined: 05 Sep 2008 Posts: 22
|
Posted: Mon Sep 08, 2008 5:47 pm Post subject: |
|
|
| Boy, I'm happy with pyTivo. This is great. Too bad about my AvelLink, though. I'll have to put it to use somewhere, I guess... |
|
| Back to top |
|
 |
wmcbrine

Joined: 04 Jan 2008 Posts: 444
|
Posted: Mon Sep 08, 2008 7:50 pm Post subject: |
|
|
| rdian06 wrote: | However, the music share shows up under the Find Download something or other. |
No, it would be under the "Music, Photos & More" menu.
| Quote: | There is another small fix where the milliseconds are slightly off, but it really doesn't affect things. |
Do tell. _________________ My pyTivo fork |
|
| Back to top |
|
 |
rdian06
Joined: 12 Apr 2008 Posts: 364
|
Posted: Mon Sep 08, 2008 8:39 pm Post subject: |
|
|
| wmcbrine wrote: |
No, it would be under the "Music, Photos & More" menu. |
My bad.
As for the timing fix, when calculating the total milliseconds duration, the multiplier for the decimal part varies based on the digits of precision. I think this fixes the math, but just using the constant 100 factor wasn't really that far off
In pyTivo\plugins\video\transcode.py, change:
| Code: |
if d:
vInfo['millisecs'] = ((int(d.group(1))*3600) + (int(d.group(2))*60) + int(d.group(3)))*1000 + (int(d.group(4))*100)
else:
vInfo['millisecs'] = 0
|
to:
| Code: |
if d:
vInfo['millisecs'] = ((int(d.group(1))*3600) + (int(d.group(2))*60) + (int(d.group(3))))*1000 + (int(int(d.group(4))*(10**(3 - len(d.group(4))))))
else:
vInfo['millisecs'] = 0
|
I might have stuck in more parentheses that really required, but it helps me keep the terms straight by righting it all out.
And there is a similar line for calculating the millisecond duration in pyTivo\plugins\music\music.py that needs the same change. |
|
| Back to top |
|
 |
|