You can find the recording button at the right hand side of the application. Today, I will check out the internal recording function of Resolume Avenue. The second post tried to use the Syphon Recorder for that purpose. I havn't found a tool yet which supports proper memory profiling, so it's hard to actually verify if this is your bottleneck.In my little series I sketched, which applications I will use to create a video clip for one of my song, that I can upload to Youtube or Vimeo. Since you said you have no disk io, i expect the os to use file caching, adding to the burden of the ram usage. It's actually pretty hard to saturate a PCI3x16 bus, but it's a lot easier to saturate the ram io. Instead they travel from gpu all the way to ram, and then from ram all the way to the capture card. The video frames dont travel from gpu directly to the capture card. If i have one gues concerning your hardware, it would be memory bandwidth. In the end it's always hard to pinpoint directly where performance issues are coming from and it's always a combination between software and hardware. (you probably wont see this in your tool as the os switches threads between cores to distribute heat, so it'll show as averaged out between multiple cores) This comes down to resolume 5 preferring 4 fast cores over 8 slow cores, yours arent slow so you should be okay there. Resolume doesn't have 8 things it can do in parallel all the time, so a few of your cores/hyperthreads are just snoozing while the others are running as fast as they can. Your cpu is built for multitasking, it can do 8 things at the same time. The second cause is that they show an average for the entire system. This idle time shows up in your measurement too. So when we're using the cpu, the gpu will be idle. Resolume pretty much uses each hardware resource sequentially. First these programs tend to show you an average over a certain amount of time. The low cpu / gpu usage you're seeing has two causes. You'll see disk io go up if you make resolume use files that havn't been used for a while (trigger different clips), or just use very long videos that dont fit into free ram You probably have lots of free ram with that 32GB, if you aren't running memory intensive applications next to resolume. The OS detects which files are often used and puts them into free ram. Unexpected low harddisk rates are usually caused by the os' File Caching mechanism. For now I'll plan to only use 16 outs as that seems to be fine, but would be nice to use all 24! When only using 16-outputs the frame rate is about 35fps and turning on lots of effects only drops it to 33fps for example. Interesting thing is, effects or resolume settings (such as "disable global effects") don't seem to make much difference. is this all due to the bottle-neck of the GPU needing to move everything over the PCI-E lanes to the Decklink cards, or some sort of software bottleneck? I have gone through the usual Nvidia settings and set everything to max performance, vsync on or off doesn't seem to make much difference. However, when I check hardware managers I'm only seeing about 40-40% GPU usage, 25-40% CPU usage, and super low read-usage from the SSD RAID (though I find that sort of hard to believe as they are reading many separate DXV files). I'm not really suprised, as it's a lot for the GPU to render and move across the PCI-E lanes (keep in mind all cards have the full 16x/8x lanes available because of the CPU). So, with all 3 of the Decklink Quad2 cards installed and 24-outs going from Resolume we get about 18fps at 720p60. OS: Windows 10 Home 64bit w/all updates (game mode disabled) Storage: 2x WD Blue 1TB SATA3 SSD in Raid-0 (can't spare the pci-e lanes for m.2 in this case) I/O: 3x BlackMagic DeckLink Quad2 SDI cards (24 outputs total) GPU: EVGA GeForce GTX 1080ti Founders Edition 11GB Have a new "extreme" test system we put together in the shop to see how much we could push things a bit and having some interesting results.ĬPU: Intel Xeon E5-1620v4 (40 PCI-E lanes)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |