|
SageTV Media Extender Discussion related to any SageTV Media Extender used directly by SageTV. Questions, issues, problems, suggestions, etc. relating to a SageTV supported media extender should be posted here. Use the SageTV HD Theater - Media Player forum for issues related to using an HD Theater while not connected to a SageTV server. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Spinning circle on Extenders (HD or MVP) halp!
When I stop a show on the HD extender, I get the spinning circle for at least 30 seconds. I replaced a PC client with this and I am not used to this type of waiting for the Sage Recordings to come up. I notice also that the link light on the front of the unit is blinking at a steady rate. All my systems are plugged into brand new Gigabit switches (Linksys Business-class or something)...
Server is running the latest version of SageTV (downloaded today) and Java 6 update 3, tested using the default STV, no STVis. Any recommendations? Anyone else seeing this? Last edited by KJake; 12-14-2007 at 10:44 AM. |
#2
|
|||
|
|||
Quote:
I am having major issues with spinning circle, loss of audio on HDhomerun channels, stuttering. Very disappointed. |
#3
|
|||
|
|||
Been doing more navigation, etc to try and figure out what's going on. So far, HD playback has been good and the PQ is better than my PC client was (was getting a lot of tearing in the 9.3 update).
If I'm watching something and hit stop, I get a spinning circle for upto 2 minutes. If I hit Back on the remote instead, I go straight to the previous menu. So, I don't think it is something wrong with the menu, but rather some operation that is performed when you press stop. I also noticed this same long delay after I deleted a recording. It was exessively long... Not related, but the naitive res switching isn't perfect yet. When I watch a DVD, something is wrong. It switches to 480i, but 4:3, no matter my settings. My TV doesn't even attempt to stretch it out. If this can get better, that'd be nice. I don't really want to watch my SD recordings and DVDs upscaled to 1080i. |
#4
|
|||
|
|||
Ahhhh The Spinning Circle of Death problem.
Luckily I only had this happen to me once last night. And I think it was from me pushing the remote button too many times not taking into account the delay in responding this remote can show.
__________________
We’re doomed. It will never work |
#5
|
|||
|
|||
the problem i had on my pc client was that if i hit stop to stop a recording and bring up the what do you want to do menu, then hit stop again to get off of that (or delete) then it spun and spun and spun. But on the other hand, I could hit home to get to main menu, and choose a new video to watch and it would immediately start up. So yes, I was seeing the exact same thing. I did not really test that to see if it was still there last night on my hd extender. The thing that always bugged me about it was that it was getting worse and worse and had initially showed up out of nowhere with no changes made to the server at the time. Reboots and such never made a difference.
__________________
SageTV user since 04/07! Server: Athlon 64 3000+ 2g, 2x500m mem, 80g OS, 4x500gb in hotswap enclosure, 3x1tb sata2, 2xHVR1600 dual tuners. Splitters on cable SD line (channels 1-99) and attic antenna for OTA HD Client1: HD300, 60" Samsung 60A3000 great room Client2: HD200, 40" Samsung LCD bedroom Client3: HD100, 42" Panasonic Plasma kid's playroom; Client4: MVP, 36" CRT basement workout area; Client5: MPV 13" CRT garage workbench |
#6
|
|||
|
|||
hmm, maybe Spinny is due to thread deadlocks (or thread starvation) on the server? I wonder if a single core cpu would eliminate Spinny. Or maybe setting affinity on the SageService process will address it.
__________________
[size=1]-MrD ============= Linux Server 7.1.9 (1)HD300 (1) HD200 (1) HD100 (2) PC Clients Intel Xeon L? 32Gb CetonTV cable card /FIOS |
#7
|
|||
|
|||
I have a Core 2 Duo 6700. This server is dedicated to Sage, so there shouldn't be any issue. I swear there is something either specific to my server, or the Sage core that causes this. It's like there is some code that only gets executed if you press Stop twice in a row. I just saw it happen after stopping an MP3 playback.
|
#8
|
|||
|
|||
I don't use our MVPs ever really, but my wife does and she just confirmed to me that the exact same things happen on the MVPs. She always gets a spinning circle after ending a show and/or deleting a show. I don't think this is a problem with just the HD extender any more. This is either a problem with my setup, or Sage at it's core.
|
#9
|
|||
|
|||
Ah ha! I may have something here...must test further:
Code:
Fri 12/14 11:08:40.668 MiniUI got connection from Socket[addr=/192.168.1.183,port=1070,localport=31099] Fri 12/14 11:08:40.669 MiniPlayer is adding to its map:00085c53a309 Fri 12/14 11:08:42.026 EventThread-00085c53a309 Hang Detected - hang time = 750 Fri 12/14 11:08:42.776 EventThread-00085c53a309 Hang Detected - hang time = 1500 Fri 12/14 11:08:43.526 EventThread-00085c53a309 Hang Detected - hang time = 2250 Fri 12/14 11:08:44.276 EventThread-00085c53a309 Hang Detected - hang time = 3000 Fri 12/14 11:08:45.026 EventThread-00085c53a309 Hang Detected - hang time = 3750 Fri 12/14 11:08:45.776 EventThread-00085c53a309 Hang Detected - hang time = 4500 Fri 12/14 11:08:46.526 EventThread-00085c53a309 Hang Detected - hang time = 5250 Fri 12/14 11:08:47.276 EventThread-00085c53a309 Hang Detected - hang time = 6000 Fri 12/14 11:08:48.026 EventThread-00085c53a309 Hang Detected - hang time = 6750 Fri 12/14 11:08:48.776 EventThread-00085c53a309 Hang Detected - hang time = 7500 Fri 12/14 11:08:49.526 EventThread-00085c53a309 Hang Detected - hang time = 8250 Fri 12/14 11:08:50.276 EventThread-00085c53a309 Hang Detected - hang time = 9000 Fri 12/14 11:08:51.026 EventThread-00085c53a309 Hang Detected - hang time = 9750 Fri 12/14 11:08:51.776 EventThread-00085c53a309 Hang Detected - hang time = 10500 Fri 12/14 11:08:52.526 EventThread-00085c53a309 Hang Detected - hang time = 11250 Fri 12/14 11:08:53.276 EventThread-00085c53a309 Hang Detected - hang time = 12000 Fri 12/14 11:08:54.026 EventThread-00085c53a309 Hang Detected - hang time = 12750 Fri 12/14 11:08:54.776 EventThread-00085c53a309 Hang Detected - hang time = 13500 Fri 12/14 11:08:55.526 EventThread-00085c53a309 Hang Detected - hang time = 14250 Fri 12/14 11:08:56.276 EventThread-00085c53a309 Hang Detected - hang time = 15000 Fri 12/14 11:08:57.026 EventThread-00085c53a309 Hang Detected - hang time = 15750 Fri 12/14 11:08:57.776 EventThread-00085c53a309 Hang Detected - hang time = 16500 Fri 12/14 11:08:58.526 EventThread-00085c53a309 Hang Detected - hang time = 17250 Fri 12/14 11:08:59.276 EventThread-00085c53a309 Hang Detected - hang time = 18000 Fri 12/14 11:09:00.026 EventThread-00085c53a309 Hang Detected - hang time = 18750 Fri 12/14 11:09:00.776 EventThread-00085c53a309 Hang Detected - hang time = 19500 Fri 12/14 11:09:01.526 EventThread-00085c53a309 Hang Detected - hang time = 20250 Fri 12/14 11:09:02.276 EventThread-00085c53a309 Hang Detected - hang time = 21000 Fri 12/14 11:09:03.026 EventThread-00085c53a309 Hang Detected - hang time = 21750 Fri 12/14 11:09:03.776 EventThread-00085c53a309 Hang Detected - hang time = 22500 Fri 12/14 11:09:04.526 EventThread-00085c53a309 Hang Detected - hang time = 23250 Fri 12/14 11:09:05.276 EventThread-00085c53a309 Hang Detected - hang time = 24000 Fri 12/14 11:09:06.026 EventThread-00085c53a309 Hang Detected - hang time = 24750 Fri 12/14 11:09:06.776 EventThread-00085c53a309 Hang Detected - hang time = 25500 Fri 12/14 11:09:07.526 EventThread-00085c53a309 Hang Detected - hang time = 26250 Fri 12/14 11:09:08.276 EventThread-00085c53a309 Hang Detected - hang time = 27000 Fri 12/14 11:09:09.026 EventThread-00085c53a309 Hang Detected - hang time = 27750 Fri 12/14 11:09:09.776 EventThread-00085c53a309 Hang Detected - hang time = 28500 Fri 12/14 11:09:10.526 EventThread-00085c53a309 Hang Detected - hang time = 29250 Fri 12/14 11:09:11.276 EventThread-00085c53a309 Hang Detected - hang time = 30000 Fri 12/14 11:09:12.026 EventThread-00085c53a309 Hang Detected - hang time = 30750 Fri 12/14 11:09:12.776 EventThread-00085c53a309 Hang Detected - hang time = 31500 Fri 12/14 11:09:13.198 Updating Disk Space Bar Fri 12/14 11:09:13.253 Got used/avail video diskspace Fri 12/14 11:09:13.254 Calculate space required for upcomming manual/favourite airings for next 2 days and display Fri 12/14 11:09:13.526 EventThread-00085c53a309 Hang Detected - hang time = 32250 Fri 12/14 11:09:14.276 EventThread-00085c53a309 Hang Detected - hang time = 33000 Fri 12/14 11:09:15.026 EventThread-00085c53a309 Hang Detected - hang time = 33750 Fri 12/14 11:09:15.776 EventThread-00085c53a309 Hang Detected - hang time = 34500 Fri 12/14 11:09:16.526 EventThread-00085c53a309 Hang Detected - hang time = 35250 Fri 12/14 11:09:17.276 EventThread-00085c53a309 Hang Detected - hang time = 36000 Fri 12/14 11:09:18.026 EventThread-00085c53a309 Hang Detected - hang time = 36750 Fri 12/14 11:09:18.776 EventThread-00085c53a309 Hang Detected - hang time = 37500 Fri 12/14 11:09:19.526 EventThread-00085c53a309 Hang Detected - hang time = 38250 Fri 12/14 11:09:20.276 EventThread-00085c53a309 Hang Detected - hang time = 39000 Fri 12/14 11:09:21.026 EventThread-00085c53a309 Hang Detected - hang time = 39750 Fri 12/14 11:09:21.776 EventThread-00085c53a309 Hang Detected - hang time = 40500 Fri 12/14 11:09:22.526 EventThread-00085c53a309 Hang Detected - hang time = 41250 Fri 12/14 11:09:23.276 EventThread-00085c53a309 Hang Detected - hang time = 42000 Fri 12/14 11:09:24.026 EventThread-00085c53a309 Hang Detected - hang time = 42750 Fri 12/14 11:09:24.776 EventThread-00085c53a309 Hang Detected - hang time = 43500 Fri 12/14 11:09:25.526 EventThread-00085c53a309 Hang Detected - hang time = 44250 Fri 12/14 11:09:26.276 EventThread-00085c53a309 Hang Detected - hang time = 45000 Fri 12/14 11:09:27.026 EventThread-00085c53a309 Hang Detected - hang time = 45750 |
#10
|
|||
|
|||
Cool, I can reproduce this and get these Hang Detected messages every time. Time to submit a support request!
edit: Tech Support request submitted. Last edited by KJake; 12-14-2007 at 11:33 AM. |
#11
|
|||
|
|||
Quote:
Your log definitely shows the issue I was alluding too. Try "right" clicking on the Sage process in TaskManager and set the "affinity" to the first CPU. Then tell us if the problem goes away (or subsides).
__________________
[size=1]-MrD ============= Linux Server 7.1.9 (1)HD300 (1) HD200 (1) HD100 (2) PC Clients Intel Xeon L? 32Gb CetonTV cable card /FIOS |
#12
|
||||
|
||||
I had some long spinning wheels and for my situation it was caused because I had changed the stream buffer to something much higher than the default 65535 in the client properties. This was on a client so I don't know if it would do anything for the extender. I noticed the extender doesn't even have that property. But there is a mini client network buffer setting in the server properties. Just a thought shrug
Last edited by ToxMox; 12-14-2007 at 01:02 PM. |
#13
|
|||
|
|||
Quote:
I took Sage out of service mode and stopped it and then started it as the old server application. Then I right-clicked and set the affinity of the SageTV process. Then I did a power cycle on the HDE and tried the same steps, they all resulted in the spinning wheel of death. Code:
Fri 12/14 14:05:22.358 EventThread-00085c53a309 Hang Detected - hang time = 750 Fri 12/14 14:05:23.107 EventThread-00085c53a309 Hang Detected - hang time = 1499 Fri 12/14 14:05:23.857 EventThread-00085c53a309 Hang Detected - hang time = 2249 Fri 12/14 14:05:24.607 EventThread-00085c53a309 Hang Detected - hang time = 2999 Fri 12/14 14:05:25.358 EventThread-00085c53a309 Hang Detected - hang time = 3749 Fri 12/14 14:05:26.107 EventThread-00085c53a309 Hang Detected - hang time = 4499 Fri 12/14 14:05:26.857 EventThread-00085c53a309 Hang Detected - hang time = 5249 Fri 12/14 14:05:27.607 EventThread-00085c53a309 Hang Detected - hang time = 5999 Fri 12/14 14:05:28.357 EventThread-00085c53a309 Hang Detected - hang time = 6749 Fri 12/14 14:05:29.107 EventThread-00085c53a309 Hang Detected - hang time = 7499 Fri 12/14 14:05:29.857 EventThread-00085c53a309 Hang Detected - hang time = 8249 Fri 12/14 14:05:30.607 EventThread-00085c53a309 Hang Detected - hang time = 8999 Fri 12/14 14:05:31.357 EventThread-00085c53a309 Hang Detected - hang time = 9749 Fri 12/14 14:05:32.107 EventThread-00085c53a309 Hang Detected - hang time = 10499 Fri 12/14 14:05:32.857 EventThread-00085c53a309 Hang Detected - hang time = 11249 Fri 12/14 14:05:33.607 EventThread-00085c53a309 Hang Detected - hang time = 11999 Fri 12/14 14:05:34.357 EventThread-00085c53a309 Hang Detected - hang time = 12749 Fri 12/14 14:05:35.107 EventThread-00085c53a309 Hang Detected - hang time = 13499 Fri 12/14 14:05:35.857 EventThread-00085c53a309 Hang Detected - hang time = 14249 Fri 12/14 14:05:36.607 EventThread-00085c53a309 Hang Detected - hang time = 14999 Fri 12/14 14:05:37.357 EventThread-00085c53a309 Hang Detected - hang time = 15749 Fri 12/14 14:05:38.107 EventThread-00085c53a309 Hang Detected - hang time = 16499 Fri 12/14 14:05:38.857 EventThread-00085c53a309 Hang Detected - hang time = 17249 Fri 12/14 14:05:39.607 EventThread-00085c53a309 Hang Detected - hang time = 17999 Fri 12/14 14:05:40.357 EventThread-00085c53a309 Hang Detected - hang time = 18749 Fri 12/14 14:05:41.107 EventThread-00085c53a309 Hang Detected - hang time = 19499 Fri 12/14 14:05:41.857 EventThread-00085c53a309 Hang Detected - hang time = 20249 Fri 12/14 14:05:42.607 EventThread-00085c53a309 Hang Detected - hang time = 20999 Fri 12/14 14:05:43.357 EventThread-00085c53a309 Hang Detected - hang time = 21749 Fri 12/14 14:05:44.107 EventThread-00085c53a309 Hang Detected - hang time = 22499 Fri 12/14 14:05:44.857 EventThread-00085c53a309 Hang Detected - hang time = 23249 Fri 12/14 14:05:45.607 EventThread-00085c53a309 Hang Detected - hang time = 23999 Fri 12/14 14:05:46.093 Updating Disk Space Bar Fri 12/14 14:05:46.154 Got used/avail video diskspace Fri 12/14 14:05:46.154 Calculate space required for upcomming manual/favourite airings for next 2 days and display Fri 12/14 14:05:46.357 EventThread-00085c53a309 Hang Detected - hang time = 24749 Fri 12/14 14:05:47.107 EventThread-00085c53a309 Hang Detected - hang time = 25499 Fri 12/14 14:05:47.857 EventThread-00085c53a309 Hang Detected - hang time = 26249 Fri 12/14 14:05:48.607 EventThread-00085c53a309 Hang Detected - hang time = 26999 Fri 12/14 14:05:49.357 EventThread-00085c53a309 Hang Detected - hang time = 27749 Fri 12/14 14:05:50.107 EventThread-00085c53a309 Hang Detected - hang time = 28499 Fri 12/14 14:05:50.857 EventThread-00085c53a309 Hang Detected - hang time = 29249 Fri 12/14 14:05:51.607 EventThread-00085c53a309 Hang Detected - hang time = 29999 Fri 12/14 14:05:52.357 EventThread-00085c53a309 Hang Detected - hang time = 30749 Fri 12/14 14:05:53.107 EventThread-00085c53a309 Hang Detected - hang time = 31499 Fri 12/14 14:05:53.857 EventThread-00085c53a309 Hang Detected - hang time = 32249 Fri 12/14 14:05:54.607 EventThread-00085c53a309 Hang Detected - hang time = 32999 Fri 12/14 14:05:55.357 EventThread-00085c53a309 Hang Detected - hang time = 33749 Fri 12/14 14:05:56.107 EventThread-00085c53a309 Hang Detected - hang time = 34499 Fri 12/14 14:05:56.857 EventThread-00085c53a309 Hang Detected - hang time = 35249 Fri 12/14 14:05:57.607 EventThread-00085c53a309 Hang Detected - hang time = 35999 Fri 12/14 14:05:58.357 EventThread-00085c53a309 Hang Detected - hang time = 36749 Fri 12/14 14:05:59.107 EventThread-00085c53a309 Hang Detected - hang time = 37499 |
#14
|
|||
|
|||
Quote:
file_transfer_buffer_size=65536 miniclient/buffersize=32768 miniclient/network_buffer_size=16384 |
#15
|
||||
|
||||
Yeah those are the defaults. Perhaps it is some kind of permissions problem accessing the files.
|
#16
|
|||
|
|||
Well, I'm not having an issue in playing back files. The spinning wheel shows up more when I'm trying to get out of the grouped view of a show to the main sage recordings screen, etc...and because extenders are considered extensions of the local sage server, I'm not sure that it could be a permissions problem with any Sage files.
|
#17
|
||||
|
||||
What OS is your server? Have you tried Sage support yet?
|
#18
|
|||
|
|||
yes, i find the hang detected all the time in that same situation in my logs. I looked further in to it but never found anything around it that was indicating a problem. I was running Sagemc on my client tho and did not thoroughly test it outside of sagemc in order to submit a ticket on it.
__________________
SageTV user since 04/07! Server: Athlon 64 3000+ 2g, 2x500m mem, 80g OS, 4x500gb in hotswap enclosure, 3x1tb sata2, 2xHVR1600 dual tuners. Splitters on cable SD line (channels 1-99) and attic antenna for OTA HD Client1: HD300, 60" Samsung 60A3000 great room Client2: HD200, 40" Samsung LCD bedroom Client3: HD100, 42" Panasonic Plasma kid's playroom; Client4: MVP, 36" CRT basement workout area; Client5: MPV 13" CRT garage workbench |
#19
|
|||
|
|||
#20
|
||||
|
||||
Quote:
Another thing to rule out. Use SageTV3.xml and turn off any unsupported extras via 5309 in the system info screen if you are using them. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
HD Extender wireless solutions thread | autoboy | Hardware Support | 46 | 01-04-2008 10:54 PM |
How does HD Media extender affect Sage+Meedio Users | techgeek | General Discussion | 2 | 12-11-2007 02:47 PM |
HDHR and New HD extender questions | VikingCrown | Hardware Support | 18 | 12-05-2007 11:48 AM |
dumb HD extender related questions | drewg | SageTV Media Extender | 5 | 11-30-2007 06:32 AM |
Multiple HD recording issue | ptaylor | Hardware Support | 0 | 02-23-2007 11:10 PM |