Hi

give us more details and useful info

hardware specs?
asio?
number and type of cameras?
number of usb devices?
etc...

we are not magicians!

I ran a program called latencyMon. runs fine if the vmix window isn't selected. After selected it sputters... this is the output from it. I'm not sure if this is helpful at all?

Thanks again,

Chris

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:01:19 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: SOLIDBAMBOO
OS version: Windows 10 , 10.0, build: 15063 (x64)
Hardware: H67MA-USB3-B3, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16367 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3392 MHz
Measured CPU speed: 1 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 2136.869527
Average measured interrupt to process latency (µs): 4.906434

Highest measured interrupt to DPC latency (µs): 2132.643482
Average measured interrupt to DPC latency (µs): 2.764337


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 228.667748
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.755488
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 1.351381

ISR count (execution time <250 µs): 2448548
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 644.211675
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 1.174375
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 2.140579

DPC count (execution time <250 µs): 1809682
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 584
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.


Process with highest pagefault count: none

Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 16.050934
CPU 0 ISR highest execution time (µs): 228.667748
CPU 0 ISR total execution time (s): 8.401512
CPU 0 ISR count: 2414874
CPU 0 DPC highest execution time (µs): 424.007370
CPU 0 DPC total execution time (s): 9.613334
CPU 0 DPC count: 1657151
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1.931311
CPU 1 ISR highest execution time (µs): 17.505307
CPU 1 ISR total execution time (s): 0.036020
CPU 1 ISR count: 11033
CPU 1 DPC highest execution time (µs): 414.798054
CPU 1 DPC total execution time (s): 1.548624
CPU 1 DPC count: 31208
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1.961458
CPU 2 ISR highest execution time (µs): 24.048644
CPU 2 ISR total execution time (s): 0.047001
CPU 2 ISR count: 10804
CPU 2 DPC highest execution time (µs): 644.211675
CPU 2 DPC total execution time (s): 1.552537
CPU 2 DPC count: 43548
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.645178
CPU 3 ISR highest execution time (µs): 38.483491
CPU 3 ISR total execution time (s): 0.025320
CPU 3 ISR count: 5368
CPU 3 DPC highest execution time (µs): 377.823113
CPU 3 DPC total execution time (s): 0.210709
CPU 3 DPC count: 16670
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1.458941
CPU 4 ISR highest execution time (µs): 37.638856
CPU 4 ISR total execution time (s): 0.031613
CPU 4 ISR count: 5325
CPU 4 DPC highest execution time (µs): 442.800118
CPU 4 DPC total execution time (s): 0.353044
CPU 4 DPC count: 28447
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.388017
CPU 5 ISR highest execution time (µs): 17.885613
CPU 5 ISR total execution time (s): 0.007162
CPU 5 ISR count: 1073
CPU 5 DPC highest execution time (µs): 120.939858
CPU 5 DPC total execution time (s): 0.039643
CPU 5 DPC count: 8619
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.415912
CPU 6 ISR highest execution time (µs): 32.868514
CPU 6 ISR total execution time (s): 0.000485
CPU 6 ISR count: 63
CPU 6 DPC highest execution time (µs): 100.924528
CPU 6 DPC total execution time (s): 0.070442
CPU 6 DPC count: 9614
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.492416
CPU 7 ISR highest execution time (µs): 7.645342
CPU 7 ISR total execution time (s): 0.000048
CPU 7 ISR count: 8
CPU 7 DPC highest execution time (µs): 78.782724
CPU 7 DPC total execution time (s): 0.153483
CPU 7 DPC count: 15009
_________________________________________________________________________________________________________

high latency makes it difficult for me to play live keyboards.

the latency is fine, even when I'm changing all kinds of scenes and cameras via midi hotkeys, not a glitch

once I choose vmix as the active window... no amount of buffers helps. I've done great with it set as low as 64 with no glitches with vmix not chosen, and as high as 1024 with glitches when vmix is chosen.

I'll try another graphics card if you think that's the issue... just seems strange that it's only when it's an active chosen window. no other programs or windows open have this effect.

Chris

so the fact that I can run 1024 buffer, and still have pops when I chose vmix as the active window,

and the fact that I can go as good as 64 buffer, and have no pops when running vmix as long as it's not the active window.

and the part where I can run all kinds of other programs, make them the active window, and not encounter this problem...

you don't think vmix is related to this issue?

it only has problems dealing with real time audio when vmix is the active window, the workaround I'll likely use, if need be, is to use vmix but never touch the program directly... and program a zillion hotkeys.

how about we see if perhaps vmix is indeed the issue, instead of buying another computer? is that so crazy?

Chris

Also running at 4k can be an issue with such a minimum card.
What about running the display at 1920x1080? same issue?

Steve

I scaled them both back to 1920x1080. Same issue.

In use: NVIDIA GeForce GT 740 (the choices are default and two identical looking NVIDIA GeForce GT 740 choices)

low latency is not set

neither is enable optimus graphics compat

output format UYVY
renderer EVR
skip 0
priority normal

Everything under that is checked except memory and read lock.


I will add this wrinkle... if I make a change like fps, or something that requires vmix to restart...if I stay on vmix as the active window... I don't get the drop outs. if I chose another window, then go back to vmix.. the drop outs happen again.

hardware encoding where? in vmix? in ableton? the nvidia ap?

thanks in advance!

@ Ittaidv

I believe hardware encoding is supported with GTX 750 and above.
As far as I am concerned, NVidia x10 to x40 series cards are entry level cards anyways.

But it may be a mute point in ckurtis' case as I am inclined to think it is a software/driver incompatibility issue somewhere along the line.
Just my thoughts.


Ice

I'm going to likely ditch my firewire card and my usb3.0 card for a combo card so I can fit a double space graphics card in my tower. So I'm open to two space cards.

Any thoughts on these 1060's or 960's? http://a.co/bVvKSaa

or this one? http://a.co/hxf4tnX

will they be supported by vmix if I encounter the same problem?

Thanks