ProSoundWeb Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: [1]   Go Down

Author Topic: Church Sound: Worship Leaders On Important Traits Of Sound Operators  (Read 297 times)

M. Erik Matlock

  • Global Moderator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 412
  • Senior Editor Live Sound International/ProSoundWeb
    • M. Erik Matlock on PSW

Church Sound: Worship Leaders On Important Traits Of Sound Operators
Mix skills and system knowledge can be undermined...
By Gary Zandstra ē April 2, 2019


According to worship leaders, what are the most important aspects of being a church sound operator? Iíve been doing an informal survey on this topic, asking worship leaders for their views.

The answers have been surprising, at least to me. For example, to this point not one of them has mentioned that a sound operator should have musical talent. Nor have they brought up the value of having a critical ear when it comes to music. Maybe itís my own biases, but I thought these factors would at least rate a mention.

Hereís another one that hasnít come up: knowing how to properly operate the equipment and system.

Perhaps the worship leaders Iíve surveyed are assuming that a sound person should already have these skills, and therefore havenít mentioned them...

Continue reading here: https://www.prosoundweb.com/channels/church/church_sound_worship_leaders_on_the_most_important_traits_of_sound_operator/
Logged
Train the next generation. Success without a successor is ultimately failure.

Ken Webster

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 75
Re: Church Sound: Worship Leaders On Important Traits Of Sound Operators
« Reply #1 on: April 15, 2019, 02:27:09 am »

I think it works both ways.  The WL and church board need to be able to consider the sound teams advice on solving issues as well, otherwise it's next to impossible to resolve them and then nobody is happy and nothing can change.
Logged
Pages: [1]   Go Up
 


Page created in 0.04 seconds with 21 queries.