Vidblaster Streaming Issue

[TomSinclair]

Ustream changed something in the last several weeks or so, not sure just what. It affects the ability to stream directly through the VidBlaster streamer. You can use the same Ustream codes and use FMLE separately as Amnon suggests. Frankly, I like have more control over FMLE settings, so I've not used the built-in Ustream streaming in VidBlaster in quite some time.

Using VidBlaster and then using FMLE to stream separately is covered in a tutorial I did a while back on Streaming to DaCast. Same principles, different codes.

[BradShoemaker]

Ustream changed something in the last several weeks or so, not sure just what. It affects the ability to stream directly through the VidBlaster streamer. You can use the same Ustream codes and use FMLE separately as Amnon suggests. Frankly, I like have more control over FMLE settings, so I've not used the built-in Ustream streaming in VidBlaster in quite some time.

Using VidBlaster and then using FMLE to stream separately is covered in a tutorial I did a while back on Streaming to DaCast. Same principles, different codes.

How is using FMLE on processor? I should be fine, but I didn't know whether or not it added more or less weight on the processor compared to the internal streaming from Vidblaster.

[Spino]

Did you consider to try Wirecast? I had those problems with Vidblaster and no problems with Wirecast.

[BradShoemaker]

Did you consider to try Wirecast? I had those problems with Vidblaster and no problems with Wirecast.

I've considered everything, but when spending as much as I did for Vidblaster, not to mention it has always worked well for me in the past, I think I'll stay with VB provided that using FMLE continues to work.

[Spino]

, I think I'll stay with VB provided that using FMLE continues to work.

Yes but Vidblaster + Streamer module active to VVD (or Video out module) + FMLE need a lot of CPU resources ....anyway good luck.

[TomSinclair]

@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!

[Spino]

First time I've seen a closed group working on the next beta. Intriguing stuff!

I think it came after Wirecast Insiders.

[Amnon]

Yes but Vidblaster + Streamer module active to VVD (or Video out module) + FMLE need a lot of CPU resources ....anyway good luck.

VERY negligible !!! One time out of three (when I tested it) it was actually using less resources. I don't think I will ever go back to the streaming module.