|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#201
|
|||
|
|||
Thanks to all for your great input I was able to eliminate my stuttering. It turns out that there is a conflict with a180 tuners and SATA drives. But I saw on an earlier post someone mentioned that SATA drives in a raid are not affected by this conflict.
So I reformatted by drive and came up with the following configuration: 80 GB PATA drive for OS 2 - 250 GB SATA drives in a Striped array The SATA RAID is dedicated for recording and as an array it is not affected by the a180 SATA bug. I can't explain it but it works. |
#202
|
||||
|
||||
Quote:
I know Jeff wants to solve this. He's asked for my help in solving it before. I found my way to a solution under v6.0 and so I abandoned the effort to solve the stuttering, because (a) I had it working and (b) I knew there were changes coming in 6.1 to address issues found in 6.0. Now that 6.1 beta is out, and I have stuttering and some un-renderable files again, I plan to get back with him and try to work through it. I suggest that you do the same. Whatever pressures may be causing releases and betas to go out with these problems, I know he takes pride in the software and wants it to work for everyone. On the flip side, Jeff, it would be nice to work these issues through here (in a forum thread) rather than via email. Email doesn't allow those of us with problems to see the whole picture of the effort, and information gets scattered all over the place for us. It might help us to see the progression of the troubleshooting in a thread rather than email, because we'd probably feel more connected to the effort. Just a thought. |
#203
|
|||
|
|||
Quote:
I'll tuck away the raid data, useful to know. At any rate I was pretty darn sure it was not Sage doing it to you. |
#204
|
|||
|
|||
Quote:
Now, on the my post. I am not too shy about saying when I'm wrong and I'll admit it when it happens. I'm an honest above board guy who's not out to slam or smear anybody who doesn't deserve it. I was running some tests for Jeff and part of that was to revert back to V5 and try it out. I finished doing so. I had the stutter in Ver 5 the same as Ver 6, same shows same networks. PBS is one that stutters here all the time now. I honestly do not remember stutter, and you'd think I'd remember it as much as I hate it. Yet it was there. There are many changes that have been made to my system since Ver 5, it's entirely possible one of them is what makes Ver 6.1 stutter. I can't even begin to narrow it down. I've changed every single driver on my system, I don't know what I had back then because it more than likely was old and dated even then. I tend to leave it be when it works. Now they're all new, I've fiddled with bios settings relating to graphics and memory speed, I've changed memory, hard drives, fans on the cpu and graphics card, even have new cards for capture. I have done every thing I can think of to fix it, and I'm afraid all I've done is make it to where I can't do a thing to figure out what happened. I will swear to you all that I did not have stutter, I can't prove it. I will swear to you all now that Ver 5 stutters much the same as Ver 6.1 does. For what it's worth all that means is that on my system right now both stutter and that if I did indeed have no stutter then some update or driver has caused it. WMP for the record still does not stutter, and it's setup to use the Nvidia stuff in exactly the same manner as Sagetv. I've verified that much so I know it's not hardware. The point of this post is to say I apologize for being so vocal about the stutter, sure it bothers me but I could use more discretion about when I post and what I say. The only conclusion I can draw is that for me now, both stutter on hardware that's capable of playing it. I was apparently wrong. |
#205
|
||||
|
||||
I don't have all of the details and proof to back it up (yet), but I'm nearly certain that there is a demux issue.
Graphs built with stvmcspmpeg.ax stutter (this is the filter that loads under v6 and 6.1 if I do nothing weird to the system). Graphs built with mpegdemux.ax do not stutter. I don't know why this happens, I don't know that it is for certain a v5 vs. v6 issue. I do know that each time I install SageTV (since I moved away from v5), I have to go through a process of unregistering demux filters until Sage's mpegdemux.ax becomes the one that is used by SageTV in building graphs. Once that is accomplished, things are ok. I think it might be helpful to get away from the issue of v5 vs. v6, and focus on which filters actually work. I have asked before that Sage list the precise filter graph in its log file. I don't know (haven't looked yet) whether this has happened yet in 6.1, but I think it might yield further evidence. |
#206
|
|||
|
|||
Quote:
|
#207
|
||||
|
||||
I have been following this thread for while, as I too have stutterish issues using VMR9 in Sage. Could someone confirm that the VMR9 playback problem I have is the same or similar to the problem others are experiencing in this thread?. The symptoms are most apparent when watching fast sports like football. So for instance when a player is running with the ball the movement is not smooth at all and looks like frames are dropped creating a stutter like playback. Sometimes, even when a highlight is replayed in slow motion it seems as if there is some kind of stuttering at work and it doesn't take too long before it feels like you have a head ache coming on. The overall problem is subtle if you are not looking for it, but if your are it's very obvious. I use the purevideo decoder for VMR9 with the smart setting, and when watch exactly the same recorded content in WMP, the playback and PQ is perfect.
I have tried all variety of decoders and settings with VMR9 in Sage, but the best all round playback and PQ I can get is using Overlay with the Intervideo CSS decoder. One thing to add is that this problem occurs playing back SD broadcasts. I have not even looked for problems with HD playback yet, but I presume there would be problems there to. Hope someone can confirm this? Thanks, Mat.
__________________
Server/Client: 1.6GHz Intel Atom 330 | 2048MB DDR2 | Iomega 2TB eSata Hard Drive | Nvidia Ion | HDHomeRun DVB-T2 | Hauppauge NOVA-TD Stick x 2| Windows 10 | SageTV v9.0.12 | Java 1.7.0_79 Clients: HD100 | HD200 | HD300 | MI Box |
#208
|
||||
|
||||
Quote:
Next, I removed that filter from the graph and replaced it with mpegdemux.ax. Stuttering gone. Actually, there was a lot more trial and error in there when I was troubleshooting v6.0. Seeing the problems I had had under 6.0 repeat themselves in 6.1, I was able to pretty much go straight through the above to re-prove this solution to myself. In order to get this solution to take effect in Sage 6.0, I had to unregister stvmcspmpeg.ax, as well as Nvidia's demux and Microsoft's default demux. I believe that whatever demux graphedit chooses for a default rendering will be the one that Sage chooses. Restarts can come in handy when you're changing things, I think. If you want to get fancy, you could probably use RadLight or some other tool or even direct registry entries to alter the merits of the demux filters, but having already spent a ton of time on this little adventure, I was using brute force. I haven't yet followed through under 6.1 to get Sage's mpegdemux.ax to be the default demux -- but this weekend, I will. I'm fairly confident (knocking on wood now) that it'll be successful again. I don't really know why I didn't have this problem in v5, and honestly, I'm beyond caring at this point. Primarily, I just want the current version to work for me. Secondarily, I'd like it to work "out-of-the-box" and for others. Hopefully others with stuttering that seemed to crop up under 6.0 or 6.1 might be able to recreate this workaround. Hint: Obviously, it doesn't make much sense to go altering filter merits or unregistering them until you find a graph that works, unless you're experimenting. I think I've done some of the experimenting, so it should be easier for others to at least test whether Sage's mpegdemux.ax helps. (Note, it's called Sage MpegDemux, or something like that, in GraphEdit). Last I heard from Jeff, and if I understood him correctly, he didn't think stvmcspmpeg.ax should have been included in rendering graphs at all. Well, I for one can attest that it is included after running the Sage 6.0 and 6.1 installer on my client. If I remember correctly, I've seen the same behavior on another test machine, but I'm not positive of that. EDIT: note, after letting graphedit default-render the file, you have to manually remote the VMR7 renderer and attach the VMR9 renderer instead, at least I did (though I believe the same stuttering affected VMR7 as well). Last edited by salsbst; 02-23-2007 at 07:56 AM. |
#209
|
||||
|
||||
Quote:
|
#210
|
||||
|
||||
Quote:
The problem I'm describing is definitely "macro"stutter. You don't need to be looking for it to notice it, and it makes the playback totally unwatchable. How's your CPU utilization during your stuttering symptoms? In my case, CPU utilization cannot be blamed for the stuttering. |
#211
|
||||
|
||||
Thanks for the reply salsbst,
So my PC might have "microstutter" ......... doesn't sound good. I have not looked at the CPU performance for a while, but I seem to remember it was pretty low around 10%. I will check it out and look into "microstutter" when I get back home. Many Thanks, Mat.
__________________
Server/Client: 1.6GHz Intel Atom 330 | 2048MB DDR2 | Iomega 2TB eSata Hard Drive | Nvidia Ion | HDHomeRun DVB-T2 | Hauppauge NOVA-TD Stick x 2| Windows 10 | SageTV v9.0.12 | Java 1.7.0_79 Clients: HD100 | HD200 | HD300 | MI Box |
#212
|
|||
|
|||
Quote:
I removed my 84.21 nvidia driver and reinstalled the latest for MCE which is ForceWare Release 90 Version: 93.71, that then let me do some things I couldn't do with the 84.21, namely I forced my display to hdtv 720p and output a true 720p signal. A lot of the stuttering I had seems like it is now gone. I watched Boston Legal fine, and it seems PBS was better, but I've got to view what I recorded last night to verify. It's odd, but CBS which is 1080i at 29.97 fps never stutters, but all the 720p stuff at 60hz stutters and that led me to believe I had some sort of timing issues causing judder, even though that judder test program I had said it was fine. I'm playing more with that area right now, but I do have graphedit on the system and will see what filters are in the chain and possibly try what you've done and see if it's different, if need be. |
#213
|
|||
|
|||
Quote:
Use the Nvidia stuff of course to test. For SD I don't believe anything in the Sage program is at fault, from what I've seen it's mostly codec related stuff there. |
#214
|
|||
|
|||
If I did it right I've uploaded 2 graph's. One that plays back fine and one that stutters. The stuttering one does not use the nvidia stuff.
Check it out. |
#215
|
|||
|
|||
Quote:
Look at the frame rate and you will see it running somewhere around 10-18 Mbps, but ever second or two it drops just for a moment to 0. If I use the older nVidia 84.21 drivers with Overlay, frame rate is nice and constant. Use VMR9 and/or latest 93.71 drivers, and frame rate drops every few seconds which correlates to the micro stutter. The point about uninstallers not putting things completely back confirms my suspicions. The only way I got my setup to work was revert back to a clean install of Windows. I have only patched Windoze up to SP2. Have not installed the latest WMP and other stuff. That with older nVidia drivers (84.21) and Overlay works. Luckily I had made a disk image of the basic Windows image (using Acronis True Image) before installing Sage which allowed me to revert back to a virgin system and experiment with different versions of things. |
#216
|
|||
|
|||
Quote:
|
#217
|
||||
|
||||
Quote:
Neither of your examples are using VMR9, they're using VMR7, by the way. VMR9 is its own filter under DirectShow Filters. |
#218
|
|||
|
|||
Quote:
I don't get why it sometimes uses Nvidia and sometimes doesn't. Yes, if it uses Nvidia it works, and if it doesn't it stutters. Somethings not right on my Windows Installation I'm afraid, now to see why. I couldn't get it to use VMR9, it would give me an error and say that it can't make the connection. Maybe I'll try playing it in WMP and see what filters that uses, I can't connect to say playing back a video but I think it used to connect to WMP. Last edited by cummings66; 02-23-2007 at 03:22 PM. |
#219
|
||||
|
||||
Generally speaking, one reason that a certain graph will use one filter while another uses a different filter is in the process of negotiating pins. If one filter doesn't want to connect, another one from the same category (the next lower in the merit list) will be tried.
(Or something like that, I think.) |
#220
|
|||
|
|||
Yes, the issue I had was different. On the same file I would get a different filter every so often, you couldn't guarantee it would end up being the same one each time.
I unregistered the one I didn't want and Nvidia is always the filter now, and to be honest SD seems nicer. I never had complaints with it, but it is nicer now than it was. HD is better, enough so that I could probably live with it as is. It's not perfect, but it is improved. At this point maybe it needs more HP on the graphics card to be perfect. I'd like to know for 100% that this is what I need to do before I spend hundreds of dollars on a card, know what I mean. To be honest, I've considered blowing away windows and doing a total reinstall and seeing what happens. But that's not a quick process. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|