Hi guys... I'm so stressed out from this problem. I keep thinking I've fixed this problem and then it comes back. I don't know what else to do and this is 3 weeks in the making now. If someone can help me with this, I will send you some money via paypal... If it can't be figured out over the forum board, then if someone in LA is a real specialist with this sort of thing, I can pay you to come out. I just don't know what else to do anymore...
I have a brand new computer. Fresh Win 7 64 install from cyber computers. I mention that so you know there isn't any pre-installed software on there. It's pretty powerful... i7 3820 with 8gb of RAM and a solid state drive for the OS and software. Asus Sabertooth X79 motherboard. Hooked up via USB is a Behringer Xenyx X1222USB mixer.
Everything seems great until I turn on a webcam. The C920 is hooked up to a USB3 port. The second I turn it on and put it in 720p or higher, I usually start hearing pops. I've gone hours with it being fine. That's one of the frustrating things. Today it is not fine and every single time I get things going these pops happen. I made an Audacity recording while the popping was happening. You can hear it at (Dead Link Removed) (It doesn't sound exactly the same because it seems like each click actually pauses the recording.) Hard to explain but it is pretty similar in the recording.
What I've done so far...
• At first I was told it was because I had 3 of these C920 cams on one USB bus. Not really the case, but I bought 3 USB3 PCIe cards and installed them. They work great and this still happens. I have discovered that it happens even when one of these cams is producing an image. Usually at 720p or higher.
• Today I grabbed my cheaper webcam (Logitech 600) and put it on there. It caused the popping sound too. Not as often, but it did in 720p mode. Even when it was the only cam hooked up. The second the picture shows in HD it does this.
• I BELIEVE this only happening when the mixer is hooked up by the way. Maybe there's a conflict between logitech cams and this mixer? The Behringer driver is installed.
• I've disabled the on board sound since I want to use the Behringer for recording and hearing everything. I've disabled the webcam mics...
• I've noticed that in the device manager there is an AMD sound driver, and realtek sound driver and the Behringer . I've disabled the other 2 at times and this still happens. Not really sure why there's AMD and Realtek.
• This popping happens in the logitech "quick capture" software in photo mode, not video... Or in XSplit Broadcaster. Which I'm going to use for streaming the video to our podcast online while we record. But it starts happening as soon as any software shows a picture from the cam at 720p or higher. It's capable of doing 1080p.
• In the task manager, nothing is making the CPU overload. Never even gets to 20% while things are going on.
The weird part is, I have had all 3 cams streaming on the net while simultaneously recording the video and audio from the mixer to my hard drive with NO PROBLEMS... Sometimes I turn the computer on and just pulling up the video starts this popping on the other hand. I'm not playing with settings. I don't know what is causing this. If anyone has any ideas I'd be most grateful. If you have any questions regarding anything in my setup, I'll get the answers for you very quickly. I'm on my computer all the time. I'm starting this podcast in 2 weeks, as you can see on the site where that mp3 file is hosted. I have to figure this out. It's all new equipment... Mixer, computer, cams... So frustrating. Was thinking about going out and buying a microsoft webcam tomorrow to see if it's a logitech thing, but not hopeful since 2 different logitechs made this happen.
Thanks a lot
B
Comments
I am still running windows XP SP 2. If you have a new rig, you a
I am still running windows XP SP 2. If you have a new rig, you are probably running Windows 7. Though this may be similar?
From control panels, you go to system. From system you go from the general tab and select the Advanced tab choose performance tab and then settings. From settings Select best performance. And then go to the Advanced tab. From there, you will see Performance scheduling, and you will choose Background services. Then you'll see and select system cache. Below that you'll see virtual memory. Then you'll select change. From there, you'll see that Windows has selected a dynamic memory with large and small numbers. You don't want that. You'll select custom size, then select zero for both. Then you'll select set.
You'll also see recommendations for how much memory should be set for virtual memory. You can go back and punch the same number into both and then select set again. This will change your dynamic memory to a single fixed value which can also be helpful.
The only caveat here is when you select for best performance, the look of Windows will change. You won't have all that cool crap happening with things zooming in and fading out. They're only trying to emulate a Macintosh operating system and they've turned everything into a cartoon. I liked cartoons when I was a kid but today it's only the Simpsons or maybe King of the Hill?
My propane doesn't work anymore on my RV. I'm all electric now.
Mx. Remy Ann David
Hey kilerb....back over here I see...howdy One thing maybe you d
Hey kilerb....back over here I see...howdy
One thing maybe you don't fully understand is the fact that with a computer and digital camera chips (webcams). You don't have to be "broadcasting", or "streaming" or do anything other than have the camera on for the computer to stream the data from the CCD image chip into RAM where the CPU buffers and then processes that data either onto a HDD or caching it as it fills up with image data. That's how they work. That how you "see" an image on your screen!...It has nothing to do with "broadcasting" or saving it (recording) or streaming it onto the internet. When it's turned on the CPU starts to buffer and cache the data in RAM. As soon as that buffer space fills up the CPU starts dumping the data out the back end. FIFO (First In First Out). The OS assigns the page space of the RAM. It's not unlimited. You only have 8Gb, 2 of that is reserved for your OS (Win7).
A typical data packet that is sampled from the imaging chip is 6Mb/sec. So HD could be twice that. All of that 6Mbps has to go into RAM which is the only "real-time" memory the CPU can use. Then once it's in there if it needs to it will route that data to a HDD for saving if that's what you want to do. But it all goes into RAM first....everything in your entire system does.
Now the CPU also has to go and get data for all of the OS routines (processes), your application, and anything else that stored on your HDD and put that in RAM so it can run that stuff. The CPU uses controller chips to switch that data back and forth from one to the other...HDD to RAM, RAM to CPU, CPU to RAM, RAM to HDD all while it's executing and putting stuff onto your screen, watching your mouse is located, streaming audio and running your applications.
So video puts a huge strain on your system....3 video cams yeah defintely. The CPU is plenty fast, the RAM is plenty fast, SATA drives are pretty fast (still a litlle slow) But when you start to try and run too many processes from the OS or an application and capture data from 3 cams in HD your going to have to strip down the OS (processes) and remove anything you can think of that isn't related to that task.
Your CPU has to switch and do all of those things with enough RAM page space to not create a bottleneck. What your seeing is something interrupting for that spit nanosecond and that is when you see those glitches.
There are so many processes and services running in the background (some are manual, some are automatic) that you'll never know when one of those processes or service request the attention of the CPU and BAMM right in the middle of monitoring your camera you get a glitch. That "Viper" site that Huesph suggested needs to be implemented to the bare bones settings. Multiple hardware drivers are killers on throughput...they slow everything done because they are hardware related and have to be executed before the CPU can move on......glitch...it goes on and on form there.
You have start from the beginning and dedicate this machine to do nothing but video and audio and strip it down to the bare essentials if you ever expect this to work. Adding RAM can only help. The OS uses 2Gb of RAM so you really only have 6Gb to work with and that may just be the marginal level. I could easily see 2Gb of buffer space per camera.
I would be really surprised if you added another 8Gb if that doesn't solve your problem.
But before you do that you need to streamline that computer.
P.S. I'm not looking for a reward....:cool:
Thanks Remy... I actually just did a test on a 3rd computer. J
Thanks Remy... I actually just did a test on a 3rd computer. Just had to replace my home computer because my old one crapped out. I got a Gateway i5 processor with 8gb of ram. Just brought in one of the cams and turned it on. Went right into the red on this computer too. So I guess a webcam in high res is using a lot of resources... I pulled up the task manager and the physical memory is at 33% after shutting down a couple adobe programs and the latency is still spiking high and even when it's not spiking it's in the red on this one at all times. I don't hear any popping. That seems to only occur when I'm listening through the usb mixer. But it goes as high as 24k on the DPC Latency test, so I'm assuming that's not good... How do I turn off disc caching? And if I do that, will it hurt things if I'm recording audio and video on my computer while broadcasting?
Thanks!