Reply to thread

Message

<blockquote data-quote="Meatwad" data-source="post: 753367" data-attributes="member: 90111">I had some issues at first with mine and 1.13, but I found out that the best thing to do is uninstall all codecs and then install the shark codec pack.&nbsp; You can also just do a base install of FFDSHOW but you're really going to want MPC h264 codec that comes with the shark codec package.&nbsp; There might be a bug in enabling DXVA in FFDSHOW.&nbsp; Whenever I enable it seemed to cause havoc with other DXVA codecs (might just be my system), anyway you may have to play with that setting if you want to use FFDSHOW DXVA.&nbsp; I advise you to use the MPC h264 codec as it doesn't seem to have any conflicts with DXVA being enabled.I've tested with Windows 7 64 bit and XP 32 bit and things run slightly smoother in XP.&nbsp; I haven't found a single antivirus/firewall solution yet that hasn't taxed the cpu too much while recording and watching at the same time (in either OS and that includes comodo and kaspersky so if you have to have av you might want to disable it when watching even if you've excluded scanning of the timeshift and recording folders) .&nbsp; Average cpu usage while watching 1080p live TV h264 is about 35%.&nbsp; Recording while watching will hit between 50-80%.Mpeg2 is actually a little trickier in XP, but not in Windows 7 (just use the windows 7 mce codec--you can probably use the mce h264 codec as well, I got good results with it).&nbsp; DXVA doesn't seem to kick in with some mpeg2 codecs no matter what I did to the registry.&nbsp; I did happen to find that Arcsoft's Total Media Theatre 2 didn't have any issues, yet cyberlink's 10 or 11 would almost always either max out the cpu or come in at high 80's when watching live from an ATSC tuner.&nbsp; The bigger the stream the higher the cpu usuage.Anyway, I hope this helps you or anyone else with a zacate.&nbsp; Also, I'm sure an SSD would probably help as others have advised.&nbsp; I just wish I could justify the expense.&nbsp; I currently run two samsung 5400 rpm drives I have my OS and timeshift folder on one and the recording folder on the other.&nbsp; I tried having them on a single drive with separate partitions but the cpu usage was much higher than I posted above so I'm certain an SSD would improve performance.</blockquote>

[QUOTE="Meatwad, post: 753367, member: 90111"] I had some issues at first with mine and 1.13, but I found out that the best thing to do is uninstall all codecs and then install the shark codec pack. You can also just do a base install of FFDSHOW but you're really going to want MPC h264 codec that comes with the shark codec package. There might be a bug in enabling DXVA in FFDSHOW. Whenever I enable it seemed to cause havoc with other DXVA codecs (might just be my system), anyway you may have to play with that setting if you want to use FFDSHOW DXVA. I advise you to use the MPC h264 codec as it doesn't seem to have any conflicts with DXVA being enabled. I've tested with Windows 7 64 bit and XP 32 bit and things run slightly smoother in XP. I haven't found a single antivirus/firewall solution yet that hasn't taxed the cpu too much while recording and watching at the same time (in either OS and that includes comodo and kaspersky so if you have to have av you might want to disable it when watching even if you've excluded scanning of the timeshift and recording folders) . Average cpu usage while watching 1080p live TV h264 is about 35%. Recording while watching will hit between 50-80%. Mpeg2 is actually a little trickier in XP, but not in Windows 7 (just use the windows 7 mce codec--you can probably use the mce h264 codec as well, I got good results with it). DXVA doesn't seem to kick in with some mpeg2 codecs no matter what I did to the registry. I did happen to find that Arcsoft's Total Media Theatre 2 didn't have any issues, yet cyberlink's 10 or 11 would almost always either max out the cpu or come in at high 80's when watching live from an ATSC tuner. The bigger the stream the higher the cpu usuage. Anyway, I hope this helps you or anyone else with a zacate. Also, I'm sure an SSD would probably help as others have advised. I just wish I could justify the expense. I currently run two samsung 5400 rpm drives I have my OS and timeshift folder on one and the recording folder on the other. I tried having them on a single drive with separate partitions but the cpu usage was much higher than I posted above so I'm certain an SSD would improve performance. [/QUOTE]

Verification