Johan Lundberg
04 Oct 2010, 22:37
As a little extra special we did a behind the scenes production on this years finals of the STCC (Swedish Touring Car Championship). Of course our main focus was the big STCC production, so the behind the scenes stuff was more as a very appreciated bonus! Vidblaster was actually auto-cutting most parts of it by itself. :)
Vidblaster setup:
7 Axis IP-cameras
2 Microsoft Lifecam Cinemas
1 Decklink card (capturing the PGM from the main production via SDI)
Global resolution set to 640x360 at 25 fps
During setup and testing the IP-cams were running at 1280x720 with MJPEG compression. We wanted to test if the rather high network traffic would be a bottleneck. Peaking around 160-170 Mbps pure IP-cam traffic on the PC's network card with cameras still running fine was proof enough. CPU was around 25-30% on the i7 920.
The cameras were then lowered to 640x360, since that was the resolution used for recording.
All in all Vidblaster performed great and we now know that there's no problem throwing alot of IP-cameras on it.
The only problem was with Vidblaster deinterlacing the incoming PGM signal from the main production, which was produced in 1080i. A better deinterlacer (which I know Mike is working on) would really have helped!
Screen shots of Vidblaster attached.
Vidblaster setup:
7 Axis IP-cameras
2 Microsoft Lifecam Cinemas
1 Decklink card (capturing the PGM from the main production via SDI)
Global resolution set to 640x360 at 25 fps
During setup and testing the IP-cams were running at 1280x720 with MJPEG compression. We wanted to test if the rather high network traffic would be a bottleneck. Peaking around 160-170 Mbps pure IP-cam traffic on the PC's network card with cameras still running fine was proof enough. CPU was around 25-30% on the i7 920.
The cameras were then lowered to 640x360, since that was the resolution used for recording.
All in all Vidblaster performed great and we now know that there's no problem throwing alot of IP-cameras on it.
The only problem was with Vidblaster deinterlacing the incoming PGM signal from the main production, which was produced in 1080i. A better deinterlacer (which I know Mike is working on) would really have helped!
Screen shots of Vidblaster attached.