MattWorley wrote:It would be great if every building that handled multi-camera webcasts just had a Tri-Caster. I use one at work and it's brilliant!
It does much of the stuff that is being asked for.
MattWorley wrote:It would be great if every building that handled multi-camera webcasts just had a Tri-Caster. I use one at work and it's brilliant!
It does much of the stuff that is being asked for.
That gives me an idea. How about some graphics and prelude music that can be streamed before/after? Make it easy. Preferably last in stream so that the operators can work out kinks in the video and audio without broadcasting it, but still stream something for the other sites to check out their systems.sammythesm wrote:a) allow switching between multiple sources that can be video, photos, music, powerpoint, etc.
What version of the webcast software did you use? I have been using a Win7 (x64) laptop with the V2 software and it has performed perfectly.sammythesm wrote:1) Win 7 didn't work. We had to go back to Win XP. It would be really nice if the webcasting client was Win 7 and MacOS X compatible. Really, truly compatible. This caused a lot of frustration in the initial setup. It wasn't even a driver issue with the cards. We purchased 3 different analog video capture cards and tried them all on Windows 7 with no luck.
We are currently planning on using a Sony EVI-D70 with the Vaddio control kit to remotely control/power the camera that over a pair of (dedicated) CAT5 cables. That will allow us to get decent results (videowise) from non-expert camera operators.3) Support for IP/network cameras or RTP/RTSP streams. This would greatly lower the disruption to the meeting. (no big bank of computers and monitors and cameras in the overflow or chapel area) You could very easily install nice IP cameras inside the chapel and then produce the webcast from a room outside the chapel. The camera 'operators' don't even need to be in the room to get a good shot. Especially since most of these meetings can be accomplished with a single stationary camera.
Personally, we are running SD cameras, we dont have bandwidth to stream HD video and so anything better than an S-Video connection is overkill.4) Better enable cameras with HDMI or other digital signals. I know I'm going a little over the edge with this one since the hardware support for HD/HDMI/Component is still expensive and nascent, but it would be very nice to have an end-to-end digital webcasting system, allowing the producer to easily connect one or two cameras with component or hdmi outputs, then switch between them. I'm using a fairly new HD camera from Canon, and it really looks bad when converted to analog and run through an analog capture card.
I would recommend that you do two things:5) Audio. We're really struggling with the audio in our setup. We're finding that the 'record out' jack near the clerk's desk rarely (if ever) works, the assisted listening devices are difficult to control the volume (too many knobs), and we couldn't even get a wireless lapel mic attached to the church system to work correctly (too many adaptors and volume controls). I dont' have a great suggestion for this one, but it's a problem.
I have always adjusted the sound levels outside of the webcast program (via a mixer and the Windows volume levels). That has worked great for the 3 meetings which I have broadcast for our stake.One thing that would help is being able to adjust the volume during a webcast from the webcast software. We think we can adjust the volume using the windows volume controls, but we're not sure if it's taking in the webcast (since you can't access volume controls after you start a webcast)
It was Win 7 32-bit with latest version 2 webcasting software. Still not sure why we had problems. Perhaps we should try x64 with the instructions/learnings other have posted. End of the day, WinXP worked out OK.Aczlan wrote:What version of the webcast software did you use? I have been using a Win7 (x64) laptop with the V2 software and it has performed perfectly.
The Axis solution you mention would be cool to try. I have access to some Axis equipment, so I'll give it a look.We are currently planning on using a Sony EVI-D70 with the Vaddio control kit to remotely control/power the camera that over a pair of (dedicated) CAT5 cables. That will allow us to get decent results (videowise) from non-expert camera operators.
We will be running it from the stake clerks office and thus the most visible part of the operation will be the camera mounted to the wall or the choir mics (if there is a choir singing).
If you want to go to a network camera, it appears that the AXIS 214 camera (which is based on the Sony EVI-D70) has a driver available that would let their network cameras be seen as a video capture device on Windows, but it probably wont work with the webcast communicator box.
Personally, we are running SD cameras, we dont have bandwidth to stream HD video and so anything better than an S-Video connection is overkill.
Sadly, I AM the audio guy...I would recommend that you do two things:
1. Find an audio person in your stake and recruit them to handle the audio
2. If the audio person agrees that the problem is in the chapel sound system, ask your FM group to get it fixed
I have always adjusted the sound levels outside of the webcast program (via a mixer and the Windows volume levels). That has worked great for the 3 meetings which I have broadcast for our stake.
It's not that I'm unable to find a solution - it's just that all the solutions I have feel like bailing wire and duct tape. Maybe I should be OK with that - it is, after all a temporary setup and not a permanent installation. You are welcome. I am glad to hear that it went well.sammythesm wrote:Thanks for your thoughtful replies, Aaron.
We actually had our first webcast last night, and it went all right.
Out of curiosity, did Windows Media Encoder work outside of the communicator software? If not, do you have the x32 version of Windows Media Encoder 9 installed?It was Win 7 32-bit with latest version 2 webcasting software. Still not sure why we had problems. Perhaps we should try x64 with the instructions/learnings other have posted. End of the day, WinXP worked out OK.
It looked nice, but I dont know that it will work with the communicator (which we are probably going to use).The Axis solution you mention would be cool to try. I have access to some Axis equipment, so I'll give it a look.
I know what you mean. I have run the webcasts that we have done up to this point mostly with my own gear (or gear that has been lent to me). It makes it easier sometimes, but interfacing it with the church equipment can be problematic.What prompted the use of the webcasting software (vs communicator appliance) was the Stake's desire to save money. If they didn't want to spend $800 on a webcasting appliance, they certainly don't want to purchase an audio mixer, video mixer, multiple cameras, choir microphones, etc. So we were trying to do the most with the least investment. My personal gear is not too shabby, so I was hoping to utilize the more advanced digital capabilities of the gear I had.
I think that the biggest issue with IP cameras is that they all have their own propitiatory way to view the video. There is no good standard to work with. That is why I suggested Axis because their driver should allow their network cameras to be seen as a camera by Windows. If I could get a demo and they worked, we might go that route, but I dont think that we will.Enabling the digital endpoints (IP cameras, or HDMI capture) would just make setting up the equipment easier (fewer cables, fewer adapters, more integrated operation) and produce a better end product (i.e. the software could detecting the aspect ratio, more gracefully down sample for webcast, etc) A better origination image just makes for a better webcast overall, no matter what the bandwidth limitations.
I recognize the industry is still in transition and all the tools aren't quite there yet, especially at a reasonable price point.
Our FM had a record out and a line in installed in the stake clerks office (not sure why). That is where we are planning to run the webcasts from. It is on the other side of the wall from the chapel and should work well to feed audio in from the stage if we need the choir microphones.Sadly, I AM the audio guy...
The suggestion was more to promote thinking outside of the box as a community and thinking of a way to capture the audio without necessitating a bunch of extra mics, an audio mixer, and a dedicated audio guy to mix it all live. I still don't have a great idea, though, so I'm stuck in the boat with everyone else.
Thankfully, our FM group did get the record out fixed in time for the webcast, but it was still a bear to run and conceal a cable from the front of the chapel to the overflow where we were webcasting from.
We have had 3 successful webcasts so far. At the last one, one of the members of the Stake Presidency wasn't feeling too well, so he spent most of the Sunday session in the clerks office. That really impressed him and helped to jumpstart the current project (to setup so that we can webcast from the Stake Center, or another building via the webcast communicator).At any rate - our first webcast was a success. Hopefully we can keep getting better from here, and as the leadership uses it more they will see the benefit from investing a bit in it.