Re: Topics suggestions for advanced system tech and tuning class
Jay,
Even among frequent users of measurement software I have noticed a diversity of mis-conceptions and/or misapplications, so some "how to" is needed to insure that everyone is on the page physics dictates.
My general structuring of topics generally follows this framework:
1. General physical principle
2. Useful analogy
3. Visual representation
4. Simulated measurement of the simplest use case
5. Check for understanding
6. Ramifications for measurement and processing
7. Real world application with messy measurements
---
On day two, after we have a morning presentation address general equipment, measurement tasks, and methodologies, we are going to set the class loose taking measurements, with their own measurement platforms, on the different use cases in locations throughout the facility. Everyone spends a set of time taking traces for their specific use case, and then we will round table and discuss their measurements.
You might choose to measure a SOS rig that we have set up, or measure a delay speaker in one room, or measure a center cluster in another room, etc. Pick the use case you have the most interest in. We will give you a list of measurements to take, and some guidelines on how to take those measurements, but you'll be responsible for them. Bennett and I will supervise and answer questions, but the measurement equipment, and ultimately saved traces, will be the attendees.
With multiple measurements happening in parallel, we can divide the work load and cover a lot of ground and allow desiring participants to have hands on practice. Spend 45min taking traces, and then an hour in post-mortem discussion of everyone's traces, then 45min applying solutions, and 30min listening to the end results. Attendees would see real data, and everyone can learn from the good, bad, and ugly of the classes collective measurements. A morning and afternoon session of this type covers many use cases. The evening hours will then fill in any questions, address any use cases people are confused on, and make sure everyone understands our more advanced suggestions.
---
Day 3 would be spent in the "big room" on site. It has a fairly complex multi-zone pa system with line arrays, downfills, delay lines, lots of subwoofers, etc. The morning would be split between talking about prediction software, and taking measurements, and the afternoon would step through each aspect of the system design, acoustic influences, etc. At the end of the day I would like to be able to compare the existing processing setup with what the class works through, and let the class discuss their take aways from that.
---
Hopefully this helps clarify what we would like to do, and why we are stressing that attendees need to be familiar with their measurement software, as they would be taking a number of measurements.
