I'm not sure, but 300w power supply looks too small to me. Maybe the graphic card is a little underpowered?

Bottleneck could be FMLE, have you tried FFMPEG already? It's a huge cpu saver compared to streaming over FMLE.

Also, the videocard could be easily upgraded, it shouldn't be anything fancy, but with a gtx950 or something you could be using hardware encoding and getting better performance.

300W looks a little bit light for a setup like this. We have 850 watt in our systems, so nothing is ever underpowered.

You should consider using FFMPEG. The system I used for a football game over the weekend was an i7 2600K 3.4 Ghz, 8GB RAM with a GeForce GT 610 (2GB). It was one camera at 1080x720p, using video delay, recording and streaming. The CPU usage was about 10 percent.

Also, as the others have commented, when you have the money, upgrade to a more powerful power supply.

@ Slaver

'Video Delay' is available in all versions of vMix,
'Instant Replay' is an upgrade feature and maybe not accessible to everyone.

@ Ph0en1x

I'm not a 'Power Supply' expert, but when I did my build, I was told that 450W would be the minimum recommendation, I went with 850W...
By 'room' I mean space on your hard drive. (I personally don't like working with a single drive) If your hard drive is constantly working at multiple tasks and having to "allocate" space, it may be 'overtaxing' your overall resources including memory and struggling to keep up which could be part of your issue with the 'Stinger'.
If your 'Master Frame Rate' is PAL 25p then your 'Stinger' should play back in 1.167 seconds (30 frames @ 25 frames per second), the fact that it appears to play flawless when not streaming or recording indicates to me that your CPU might be struggling with multitasking when asked to do everything you need it to do.
Recording and Streaming are both CPU intensive, what format are you recording in?
Again, your system, on paper, appears to be adequate enough to do a single camera vMix record and stream, but as indicated, is not as smooth as you would like.
Perhaps dropping to 720p and using FFMPEG will help, but the question remains, where is the bottleneck?
Are you able to document and monitor in 'Task Manager' what processes and/or resources are putting the biggest strain on your system?


Ice

Recording to a usb drive or an SD card, even over usb3 is asking for troubles. A 60 GB SSD drive is cheap as chips now, and will for sure perform a lot better and more stable.

Vmix is only displaying the amount of CPU the program itself is using. Just press ctrl + alt + del and select the task manager, there you will see the amount of cpu FMLE and VMIX plus all other background tasks are using together.

In every case I think having some headroom on all your components is not a luxury, but a must. You can easily say component X or Y is 'just enough', but you will see that when you push things to their limit, you get little weird issues that should be 'theoretically' impossible.

Something else: you replied you stream at 5 mbit, i hope the 5 mbit is not for recording full HD footage.

We previously had a lot of trouble because we recorded back in the days on a 60GB drive and used mp4 10 mbit or less. We had crashes and performance troubles all over the place. On this forum I found out you can't over compress your footage. Apparently it's just too much compression and especially in complicated scenes (fast moving lights for example) it's too heavy to handle, even for a beefy computer.

Now the minimum is 50 mbit mp4 or prores/avi, depending on the gig, and those work a lot better. Off course it required to buy a bigger drive, but since we stopped over compressing we had no more performance issues. Actually i'under impression that we used less cpu when compressing to a higher bitrate. Later we replaced an older nvidia card by a gtx 950 in one setup, and hardware encoding is running supersweet, we almost don't use any cpu at all anymore :)

@ Slaver

I've been using the 'Video Delay' feature from the beginning.
In many ways, it's not much different than "Instant Replay" for 'immediate' playback of an event, but therein lies the caveat, it's all about timing.
For hockey, I find a 12 or 13 second delay works well.


Ice