How to lower dpc latency windows 10 Videos

+Emre U lol i hardly hear him

I don't know if you are aware but the Delta 1010 is the interface I started using when I finally started "recording seriously". I can't say enough good things about it. You can see it in this video: //youtu.be/988gEhZoD9A?t=5m34s

+Rankangkah Attractive women are expensive?

+RealHomeRecording.com Those are expensive.

+RealHomeRecording.com holy shit dude you acknowledged him o___0

+RealHomeRecording.com haha omg I died xD

+a te Thanks.I'm working on getting an attractive woman to do future presentations. It's not in the budget at the moment though...LOL.

yea and the useless background services which should be optional like why would i need windows media player network shareing service running in the back ground when i don't even use windows media player. I even tried turning the service off manually and it always keeps running. now there is windows 10 coming up and people with windows 7 i herd gets a free upgrade and windows 10 is suppost to be better with gaming which i doubt. For whatever reason gaming and producing music in a daw are the two most demanding resources type of applications for windows and microsoft never thought of making an OS just for people who need alot of resources and aren't casual PC users doing simple things phones can now do. I blame Innovation in the business world which sacrifices quality for simplicity of doing things "on the fly" and flies are really annoying.

Awesome discussion guys. I have heard good things about Ubuntu. It's what Windows should be if Microsoft still gave a crap about optimizing hardware-software resources instead of making Windows look like an iPhone menu screen.

oh thought you start it in windows and closes windows while opening linux like a reboot OS Switch. I'll try the dvd first thanks.

interesting that you can use it inside windows, i'll try it out and get more info on it. Windows is a pain when it comes to video games or audio when producing since it runs too many useless services along with bugs in their updates that can actually give you a blue screen or stop programs from installing.

can you run ubuntu without windows in the back ground and without installing it as the OS. I herd about ubuntu,but don't know much about it's compatibilities with everything i use.

+RealHomeRecording.comyep lol. It's a pretty good audio interface and fixed alot of issues i was having with my audio being randomly bitcrushed, but there drivers for the interface is not great. I can finally perform on my new keyboard without cursing at my PC for hours because it decided to ruin my audio output randomly.

+blood lord The irony!

haven't. I actually like asio4all better then the m-track asio since asio4all lets me go at 2ms latency and it's the only way FL studios will let me use my usb mic. Theres also less options in M-track asio driver.

+blood lord That's definitely a driver issue and something you or I can't really resolve. Have you contacted tech support? Otherwise you may be better off returning it.

Your welcome

So what did you change?

+Molten Music Technology Awesome. I was going to say the same about windows 10.

Awesome!

+Forrest Simonds You're welcome and yes i'll do one on Windows 10 soon.

+3Rev Videos and Stuff website and blog changed location - sorry, i'll see if i can get that back up at some point.

ok i sorted it out about two minutes after sent the message its alright

+Steven Anthony As i say in the video, this is the "BIOS" the basic in/out system of your computer. Some computers don't let you mess about in there so if you can't find it or don't want to look then just ignore it - it'd for advanced users only.

+songfuzz Windows 10 will be along in time.....

+Justin Giacobbi Are you talking about the BIOS screen? Usually it's by tapping the Del or F2 key when first starting the computer up - but don't worry about it too much, the BIOS stuff is less vital.

+looneyburgmusic I blame the parents. There are a lot of tweaks that are no longer necessary. When preparing this particular video i went through as many as i could before wanting to shoot myself to see if there was any difference at all. These things can be terribly hard to measure, especially when you're starting from a decent computer with decent components that all behave properly - like I am here. Where it can make a difference is with bad computers with bad components and so just so something doesn't seem to help on my system I can't necessarily decide that it's no longer a valid tweak. Getting accurate information is of course very helpful but there's very little out there that refers to real-time audio performance - there's plenty on frame rates in games but that's not what we're after, and so I do the best I can. Thankfully the burningly critical are few and far between and instead the comments section is filled with people being helped by this tutorial. One of the main guys at Microsoft who develops the audio engine for Windows told me that my BIOS tweaks totally transformed his badly behaving DAW. That's why i ask about your experience, not to be snarky, but because actually that's all we really have to go on.High Performance in the power settings can have some effect but there are a dozen more settings hidden in the registry under the power profile that might also help - but if you have a mobile processor then the high performance mode is not going to help - it doesn't help on my Surface Pro 3 and in fact the designers of it tell me that High Performance mode will make it worse because it heats up quicker and so throttles in no time at all. So it's lovely to have facts, but we're not dealing with a single type of technology, board, processor, OS or user and so you have to go on what seems to work.If i were you I would start a letter writing campaign against the motherboard manufacturers for allowing idiots access to such a highly dangerous thermal switch. :)

+Molten Music Technology You are 100% correct. I have absoultly no knowledge of Intel CPU's, or how they work. I thought I had made that crystal clear already. Bottom line, if you are going to do a tutorial, at least make sure the information you are giving out is accurate. I would suggest starting with learning how the latest Intel processors deal with heat dissipation.edit:Ok, that was a bit harsh I know. Here is the deal. A lot of the things we have all been doing to "tweak" Windows based DAW's for the last 10 to 15 years are no longer necessary. If you want to stop any CPU throttling all you really need to do is change the settings in the Power Plan to High Performance. That will stop any processor throttling that is not needed to protect the CPU.

+looneyburgmusic Ok, i bow to your greater knowledge, i'm sure you're right. Many tweaks are following some overall logic rather than being individually effective and so removing anything to do with thermal throttling, anything that will step in and cause the CPU to clock down will prevent problems - because that's what this tutorial is for, it's for preventing or solving problems. For people having throttling problems digging around in the BIOS and finding things that disable that behaviour can end up solving the issue - all the tweaks here are based upon experience of trouble shooting systems for audio performance. You haven't related to me any of your experience in dealing with hot processors, but I have lots and that experience has shown me that Intel CPU's turn themselves off when they get to around 100 degrees - that's by design and that works and there's no damage to anything other than an unexpected shutdown. When dealing with the BIOS you are looking to to prevent noise increase and CPU decrease - that's why we do these things. You say it's not effective - that's fine, it seems to be helpful in what i've seen and it doesn't seem to be causing anyone any trouble. But, you know, i'm always reviewing these things and if something is pointless then.... it's pointless :)

+Molten Music Technology That is completely  incorrect. You seem to be mixing up outdated information from the Pentium IV days, with optional settings that some BIOS manufacturers may offer to throttle a CPU based on temp or core load. Thermal Monitoring is designed by Intel to work with "modern" processors only one way. Put simply, it works the other way around from what you just said - the BIOS does not poll the CPU, the CPU has sensors built in that will trigger based on the current internal temp. There are two different "levels" of protection - The first will flag PROCHOT#, which is the one that triggers the BIOS to throttle the CPU back by lowering the clock speed and stepping down core voltage. According to information released by Intel, that sensor will trip around 90-100C "average". If that flag fails to resolve the overheat, the CPU will begin to "self-throttle", by cycling the clock on and off.  If the core temp continues to increase, the second trigger will flag THERMTRIP#, which causes an instant clock stop of all cores, requiring a hard reset. THERMTRIP# is designed to latch, and prevent the CPU from operating so long as the internal die temp. is at or above the level that Intel has determined will cause permanent damage to the silicon, (somewhere around 130C). The actions of both those flags are not user adjustable at the BIOS level in any way, both are set per-processor at the factory by Intel. All you can do is disable the BIOS response to the PROCHOT# flag, which will simply cause the CPU to either self-throttle to prevent damage, or flag a thermal trip, which stops the CPU dead in it's tracks.In any case, there is no CPU currently produced by Intel that will trip either at a temperature below a level that could cause possible damage to the processor. In other words, so long as the CPU cooling is functioning properly, turning off Thermal Monitoring will have absoultly ZERO effect on processor efficiency, or core throttling, because those two flags will never be set. You are basically telling people to turn off something made to protect their CPU from damage in exchange for no gain in return. 

+looneyburgmusic No i don't think that's it. Disabling the Thermal Monitoring in the BIOS has no effect on the CPU's ability to shut itself down in the event of a high temperature. The thermal monitoring polls the CPU to ask it what it's temperature is and then, depending on the BIOS features, it may do something about that. We don't want that - we don't want the CPU interrupted for anything, we don't want to cause the CPU to slow down, we want to provide adequate and controlled cooling that might well be above the average temperature a normal user would use. So, you are not in any way removing safeguards against catastrophic damage, you are disabling a reporting tool that can sometimes be used to throttle the CPU and is making the CPU report on its temperature when it really doesnt need to. I've been there and done all this many many times and in 20 years in the business i've not burnt out a CPU or caused damage to a system through over heating - and i've over heated plenty of systems. So chill out man - it would be an extreme situation to cause the CPU to shut itself down but when it does, it's safe and easy and lacks drama - can't say the same for AMD processors though :)

+Molten Music Technology I think you are missing the point. The Thermal Monitor in the BIOS is triggered by sensors in the CPU. It's not a "The hotter the CPU is the more it's throttled". It is "This CPU has reached a temp. that bad things are about to happen." Those sensors are hardwired to trip before the max temp the processor can safely reach. It doesn't matter at all what type of cooling the CPU has, or how hot it may be safe to run - If Intel hardwired the CPU to signal an overheat to the BIOS at 85C then that is because 85C is the point that Intel says the processor is about to lock up, or burn out. So basiclly what you are saying is it is a good idea to defeat a part of the CPU/BIOS subsystem that was designed to protect the system from catastrophic damage. Windows itself would probably throttle the CPU long before the BIOS would from a CPU overheat trigger, or the system would just lock up or throw a Blue Screen. Bottom line is disabling thermal protection in the BIOS simply removes a layer of protection for the CPU that has no effect at all on how the system runs; if the CPU cooling system is operating correctly the processor will never reach a temp. that would cause a trip in the BIOS. edit:Another thing someone just reminded me of - if the Thermal Protection at the BIOS level is disabled, and the CPU does happen to reach the trigger temp where damage will occur, the processor itself will begin to "self-throttle", by cycling the clock on and off to lower power consumption, and temperature. So, in effect, disabling at the BIOS level will not stop the processor from throttling back if it gets too hot, it will just happen in a more extreme manner...

+looneyburgmusic The thing is that you don't really get any access to how the thermal profile works inside a computer. You may be able to run a system, water cooled, at a steady 85 degrees C but thermal monitoring would have flagged that up and started clocking down way before that temperature - but there's no need to. An Intel processor will shut itself down before it burns out so you are still protected - there's no need to be a drama queen. In finding a compromise between noise and cooling taking control of the way the processor behaves is what you need to do - but these are simply suggestions, you do whatever you want :)

that DPC latency is with HPET turned off. also with CPU power saving features turned off.

I disabled it at first, but now I have it turned on

+Anusha Dharmasenai'm gonna buy the asus p8z77-m pro i want to know if he have C states so i can disable to get dpc like you and USBPORT.sys to 4 less its possible ? thanks

I have to confess that I had to cheat a little but there to get such low DPC Latency figures. I had to disable all the C-States to get there. Otherwise it would be at around 30.