ProSoundWeb Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: [1]   Go Down

Author Topic: Church Sound: Taking Care Of Business  (Read 282 times)

M. Erik Matlock

  • Global Moderator
  • Jr. Member
  • *****
  • Offline Offline
  • Posts: 60
  • Senior Editor Live Sound International/ProSoundWeb
    • ErikMatlock.com
Church Sound: Taking Care Of Business
« on: August 24, 2018, 08:13:25 am »

Talking with sound technicians and worship leaders, I often hear the complaint that from week to week, the quality of Sunday morning varies. I’ve determined that some of this is from training, such as when there’s a problem and the tech doesn’t know how to fix it. Some of it’s skill; certain folks simply have a better ear and command of the equipment than others.

On the same hand, the skill level of the musicians may also vary. I’ve found that with inexperienced musicians, the level at which they’re playing can fluctuate greatly. I attribute this primarily to a lack of confidence. When they know the song they “bang” it out, but when they’re unsure, they hold back.

Today I’d like to focus on another contributor to the problem of inconsistency: equipment status and organization...

Continue reading here: https://www.prosoundweb.com/channels/church/church_sound_taking_care_of_business/
Logged
This space for rent.

Simon_Barrett

  • Newbie
  • *
  • Offline Offline
  • Posts: 21
Re: Church Sound: Taking Care Of Business
« Reply #1 on: August 24, 2018, 02:37:10 pm »

Good article.

A lot of common sense here but it’s amazing how much is missed.

For example: Our worship team planner does not communicate the rota to our sound team. I am in both and so have been give. Both rotas. This is something an am trying to change.

Also, we have the disadvantage of not having our own building so the maintenance parties which would be great and mean I can train tech guys/girls don’t happen.


Sent from my iPhone using Tapatalk
Logged
Pages: [1]   Go Up
 


Page created in 0.087 seconds with 24 queries.