Phoenix Build 409

[photon]

Originally Posted by bialio

Thanks for trying. I don't know what might be going on. Maybe the logs photon sent stuckless will show something.....

I understand my logs did not point to a cause. I'll be happy to help if there is anything else I can do. Thanks for all the hard work you guys do.

[AWS]

Originally Posted by photon

I understand my logs did not point to a cause. I'll be happy to help if there is anything else I can do. Thanks for all the hard work you guys do.

Ditto on that. If any developer needs logs, I'll help out there and I really appreciate all the work ya'll do.

AWS

[stuckless]

I did review the logs from a couple people, and there was nothing in those logs that point to reason why things are not starting up.

I have 2 HD300s and 1 HD200 and I've never had it not startup correctly (which doesn't help you).

There is obviously something that you all have in common, but it's not apparently, yet.

[michaeldjcox]

This happens with me too on HD200.

I also cannot launch a client on the server PC and change the STV to phoenix - just get spinning cursor.

I took a look in phoenix and sagetv logs but cannot see anything obvious.

Michael

[photon]

Originally Posted by stuckless

I did review the logs from a couple people, and there was nothing in those logs that point to reason why things are not starting up.

I have 2 HD300s and 1 HD200 and I've never had it not startup correctly (which doesn't help you).

There is obviously something that you all have in common, but it's not apparently, yet.

Just guessing but maybe it's looking for something we don't have installed. Possibly software. Also I don't have any TV tuners installed on this box since I'm not ready to switcover to it until I've settled on a UI.

[AWS]

I don't have any tuners in this Sage server either. Its just for playback.

AWS

[bialio]

Hmm.. That is suspicious. Maybe the weather code that looks for the configured EPG source is #FAIL ing since there isn't an EPG configured...... ?

[stuckless]

Originally Posted by bialio

Hmm.. That is suspicious. Maybe the weather code that looks for the configured EPG source is #FAIL ing since there isn't an EPG configured...... ?

That's a good idea... It was added in 409, I think... I'll check the code so see if it's doing the connection in the background (which it probably should)

[AWS]

I don't know if this helps of not, but on occassion, when I play back a media file Sage throws an exception and says something like "there are no configured turners capable of playing the file". Once again, those aren't the exact words but it's something like that. That only happens when I tell BMT to import the media file as TV recordings.

This may not be related but I'm just throwing it out there.

Thx
AWS

[disco340]

I just tried to install Phoenix on my friends server for the first time and he also gets this "circle of death"

[rtengvad]

I have had the same start up issue with 409 and I have two tuners and an epg source configured on my server.

But maybe it is a weather problem anyway, since it is not working here in my country

Rasmus

[AWS]

On my PC client I have the .409 version (which isn't working - spinning circle). On my server/client PC I have the .408 version that was installed manually via the directions on page 3. Today I tried some very basic troubleshooting and copied the .408 *.xml file off my server/client PC on top of my .409 *.xml config file (still kept the .409 other files intact) and all worked fine. So mixing and matching the Phoenix.xml file from .408 on top of the "guts" of a .409 build works. No more spinning circle. I'm not sure what intended functionality I just lost, but at least the spinning circle is gone.

Maybe that helps narrow down where the underlying issue of .409 is. (?)

Thanks

AWS

[photon]

Originally Posted by AWS

On my PC client I have the .409 version (which isn't working - spinning circle). On my server/client PC I have the .408 version that was installed manually via the directions on page 3. Today I tried some very basic troubleshooting and copied the .408 *.xml file off my server/client PC on top of my .409 *.xml config file (still kept the .409 other files intact) and all worked fine. So mixing and matching the Phoenix.xml file from .408 on top of the "guts" of a .409 build works. No more spinning circle. I'm not sure what intended functionality I just lost, but at least the spinning circle is gone.

Maybe that helps narrow down where the underlying issue of .409 is. (?)

Thanks

AWS

I can confirm that works!
I downloaded this:
http://code.google.com/p/sagephoenix...8.zip&can=2&q=

Extracted Phoenix.xml and replaced the 409 version on my server. No spinning circle Phoenix loaded immediately.

This is my first time seeing Phoenix work without the Navigation/Screen display issues I strangely experienced the first time I tried it. I'm excited about exploring this UI for the first time.

Thanks AWS

It's probably not working properly. It looks nothing like the screenshots topic shows and DVD icons are all the same flame image. Music seems to work as described in the guide to it though.

[drpixel]

You may add me to the list that gets the spinning wheel as well. I have tried an uninstall of Sage TV, wiped out the entire SageTV folder and did a clean install to no avail. I did update BMT first before installing the Phoenix plugin.

Sage API version 7.1.9.1
Phoenix version 2.3.47
Sage version 7.1.9.256

Sage is running as a service, under my user id on the system.
System is WHS 2011 running inside of a virtual machine
I have two HD300 clients that connect to it
I have NO TV tuners
Library import folders are on a network share

Performing the xml file swap as described above (replacing version 109 with version 108 xml) worked like a charm. Hope this is of some use to you in tracking this down. Will be happy to provide any other info you need.

[Owen Brent]

I could have saved you the trouble of reinstalling Sagetv because I did the same thing a while ago and still have the same problem. I am running windows 7 that was upgraded from Vista. To keep my wife happy, I will have to keep using the SageTV UI. I also have working tuners.

[AWS]

You have tried .408, right? .408 is so much better than the stock UI and .408 works fine.

[Owen Brent]

I have not tried .408, I was hoping to help find the cause of the problem. I will try .408 as soon as I can find the time.

[bialio]

I do intend on tracking this down - just haven't had time to even watch TV lately, much less work on Phoenix!

Once we get back into the swing of things this will be first on my list.
btl.

[Owen Brent]

In the meantime, build 408 seems to be working perfectly (everything I use anyway). I had the time to install it (took only a few minutes) and I am happy to have it back.

[rhinoman]

Just tried this, I too had the 409 won't start issue and swapped just the 408.xml file and it started immediately, hope this helps you find the problem as it looks really nice.