Need PC audio help, GAF. MUCHO gracias.
Okay, so I have some Turtle Beach headphones (3.5mm jack + USB), and I just bought my first HDMI monitor with speakers. How do I easily switch back and forth between the two for the audio output?
The long way as I've discovered is to pick whichever one I want to use in Windows Audio Devices and right-click it > Set as default device. But that's annoying when I'm in a game.
I do have Reaktek HD Audio Manager, but that doesn't seem to do anything for me that Windows Audio Devices can't.
Is there an easier way I can switch between the output devices, or even have both devices outputting at the same time (a little less ideal but I would take it)?
what if we include this in the OT, I'll see if it does indeed work. 
At what point during the process is everything failing?Quoting myself here.
I think I found a way around the usual Microsoft program. Much easier.
http://www.guidingtech.com/10026/create-bootable-windows-8-usb-drive-iso-image/
Nvm, nothing works. ;_; I cry
·feist·;46331010 said:
In addition to what Ty4on says above, possible variables:
Interesting, watching now. A minute in and let's see what comes from this.
His tested had a 7870 as a GPU. Not that I'm looking for reasons to discount him but I wonder what it would be with an nvidia GPU as well. Kudos as it seems the AMD CPU holds up well.
mkenyon's link has this graph
So if you look back to the Firefall data I posted, I'm not kidding when I say I had to run that same benchmark (and it's a replay, I only hit play and then start the capture, auto shut off after 180 seconds) a total of 5 times (30 runs), and even then I'm getting wildly different stats that make zero sense. The stuff I posted I even had to omit the 4400 and 4600 runs because they were totally wonky compared to the rest. All I have to do is hit a '+' or '-' on my board twice to get ready for the next test. This is using a completely different system.
They have actually! They're now in line with Lynnfield processors. Below even i3s though.
here: http://techreport.com/review/23750/amd-fx-8350-processor-reviewed
They have actually! They're now in line with Lynnfield processors. Below even i3s though.
here: http://techreport.com/review/23750/amd-fx-8350-processor-reviewed
So if you look back to the Firefall data I posted, I'm not kidding when I say I had to run that same benchmark (and it's a replay, I only hit play and then start the capture, auto shut off after 180 seconds) a total of 5 times (30 runs), and even then I'm getting wildly different stats that make zero sense. The stuff I posted I even had to omit the 4400 and 4600 runs because they were totally wonky compared to the rest. All I have to do is hit a '+' or '-' on my board twice to get ready for the next test. This is using a completely different system.
This guy probably just runs a test and calls it good. I wanted to do that too, but couldn't live with inaccurate data.
That's because Min/Max/Average is a really bad way to measure performance. For example, here's 3 minutes of gameplay in Firefall. First chart is min/max/average, second chart is a plotline of the FPS.
Minimum 83 FPS, pretty good right? Wrong. Here's a plotline of the exact same data that shows, in milliseconds, how long it took to render each frame.
There are a huge number of frames that are taking over 16.7ms (60fps) to render, with some reaching 70ms (14fps). These are the kind of stutters that one would encounter when running out of VRAM.
A much more accurate measurement of 'average' experience is 99th Percentile Frame Latency, which shows us how long it took to render 99% of all frames.
In instances where there aren't major stutters, this should generally line up with average FPS. But that's the thing, average FPS completely misses situations where things are going wrong. It only polls data once a second, yet it could be averaging out 70ms frames with 8ms frames over a second to show you 80fps.
The more I'm researching this stuff, the more I can't believe that FPS has been a standard for so long. It's sooooooo bad.
I have med-small hands, and I definitely cannot claw grip my sensei. Spawn/Xornet is the way to go with claw, but as you are left handed, that's definitely not a good fit. I'll do some research for you and let you know if I find some good stuff.
My best guess is that he isn't controlling the benchmark variables well enough then. Most of the stuff I have done, I have stuck to replays as that limits input variables during the benchmark.
