Did you consider to try Wirecast? I had those problems with Vidblaster and no problems with Wirecast.
Printable View
Did you consider to try Wirecast? I had those problems with Vidblaster and no problems with Wirecast.
@Brad - When you use VidBlaster's one-touch streaming to Ustream, you are actually using FMLE behind the scenes in its command line format. So CPU use is the same.
I tested VidBlaster to Ustream again tonight and it worked just fine. Not sure why I had a problem before. Suspect its something with Ustream. I've had problems streaming in the past when my Ustream Channel name had spaces in it. I think I had to replace the spaces with underscore characters.
Best news is that 2013 should be a stellar year for VidBlaster so far as improvements in CPU usage, HD streaming and recording. In a rare move, VidBlaster developer Mike Versteeg is working with a private beta group on optimizing for HD. First time I've seen a closed group working on the next beta. Intriguing stuff!
By the way, did some tests (the real test is coming up in a half hour) and it works quite well. I am surprised Mike V seems to think there is never anything wrong when clearly something is amiss since the FMLE is working separate from VB but VB's Streamer that, as he says, is exactly the same as FMLE is cutting off after a few seconds.
Thanks again Amnon and Tom, I will finally be back to live streaming again.
I think Brad is referring to the practice of using FMLE separately but in partnership with VB. VB sends Video Out to VVD. FMLE receives Video from VVD. Give you much more control (through FMLE settings) than to use the "one-touch" streaming settings inside VB.