Hi All.

Just finished a two day 13 game football marathon, and vmix performed like a champ, but did some things that concerned me.

First, my hardware is a 1 GB Nvidia GPU, i7 processor, 8 GB ram, and decklink PCIE capture cards.

I captured in 1080 59.97, recorded in 720p 59.97 and streamed in the same. I ran an external 480p output with a usb3 Intensity Shuttle. I also did a fullscreen of output on the secondary output on my graphics card.

Render times were never above 6MS Vmix cpu never above 20%, and overall cpu never above 60%.

We ran two cameras and a video delay, as well as an NDI scoreboard. I used the video delay extensively for replay.

Here is the issue- quite often after saving a delay, and then selecting next item in the list via shortcut, vmix would seem to freeze for a second. Then, when the video delay window had moved to the next item, the fps on the recording would spike to 140-200 fps and then return to normal. (I would go to next item as quick as possible after the red save button went off.) Audio meters would freeze as well. Then happened 60-75% of the time.

Occasionally, on the previews for inputs, frames would seem like they were being skipped. But recording and streaming in all instances was smooth and uninterrupted without dropped frames.

Its almost as if the display could not accurately show what was being streamed/recorded. All ended up being fine, but it was concerning.

Any thoughts/suggestions?

I had this happen in the past but found that it was because the hard drive that contained the list items had went to sleep. I fixed this issue by going to Power Options in Windows and selecting Advance and telling my computer to never let the hard drive go to sleep. The response time was instant where the disk was moving. I have since upgraded all drives to SSD now but one of my many fail my way to success stories.

@ kjones9999

Can you elaborate a little more on your system specs and workflow?
(specifically hard drive(s) and cpu specs)
Like PrepSpin, I suspect it is Hard Drive related, not necessarilly affecting mission critical events, but a refresh hiccup of sorts of the UI.
It would be good to get to the root of this "glitch" to eliminate and/or avoid it or at least be aware of what it is and whether or not it is something to be worried about during a prodution...


Ice