0 Members and 1 Guest are viewing this topic. Read 17853 times.
...Here is a link to what is going on: http://www.freepatentsonline.com/7085389.htmlScroll down about 20% of the page and you will find the schematic that the patent is based on. This 3 way crossover employs 5 caps, 3 inductors, 4 resistors and 2 iron core transformers. Something they don't mention and something I have not seen discussed is off axis performance. That's what the person next to you is hearing. Depending on the relation of wavelength (speed of sound/freqency) to cone diameter it may not be wise to quickly (120 dB/octave) change from one driver to the next. Measured on axis there will not be a problem. Measured off axis there will be sharp peeks or dips as the woofer transitions to the mid and as the mid transitions to the tweeter.
The same parameters that apply to a no compromise preamp design also apply to an electronic crossover.
Having looked at many passive crossovers, I think people may be giving way too much credit to the thought and effort that goes into these things. Even if a lot of thought goes into them, the various "solutions" to problems like BSC doesn't necessarily sound better subjectively. I once achieved better subjective sound quality by removing BSC circuit from my speaker, so YMMV as always..
Quote from: *Scotty* on 29 Jun 2008, 11:14 pmThe same parameters that apply to a no compromise preamp design also apply to an electronic crossover. Absolutely. I've tried at least 5 or 6 active crossovers, and barring the Krell crosssover (which I don't want to afford), the Bryston is a great example of a flexible, pure-sounding active crossover. It does not use IC's and uses discrete components with non-switch-mode PS. Even the Bryston starts to deviate from absolute purity once the gain controls are used, so I bypass those. Having looked at many passive crossovers, I think people may be giving way too much credit to the thought and effort that goes into these things. Even if a lot of thought goes into them, the various "solutions" to problems like BSC doesn't necessarily sound better subjectively. I once achieved better subjective sound quality by removing BSC circuit from my speaker, so YMMV as always..
Dear Turbo,Please post a list that shows that 99.5 % of speaker crossovers are more than simple slopes. If you can realize your transfer function at the speaker level then you should be able to also create the same transfer function at line level. Then we could enjoy the reduction of intermodulation and other problems amplifiers face when asked to handle full range signals and we can select amplifiers which have particularly good sound at different power levels.
In my experience, a good "crossover" often is doing some equalizing as well, even if the circuit topology looks simple. Cases where a textbook active crossover would meet the designer's goals probably exist, but not for me. Turbo's number may not be exact, but I agree with the point he's making.I have a copy of "Loudspeaker Recipes: Book 1" by Vance Dickason, which goes through the design process for four simple, straightforward two-way systems. He starts out with drivers that "on paper" go together well, but really getting it right is not a simple process. Despite being the author of the "Loudspeaker Design Cookbook", Dickason's final circuits do not look like cookbook circuits at all. One might then ask, why not just make the effort to choose drivers that would work well with a simple active crossover? The short answer is that there are tradeoffs at every turn, and fixating on this requirement would force many designers (myself included) to make major tradeoffs in areas that we believe are more important.Also, note that effective implementation of an active crossover, analog or digital, is not trivial. Active crossovers are a tool, and the results will be no better than the capabilities of the man using the tool. They are not a panacea - while active (especially DSP) crossovers can often address issues that are not readily addressed with a passive circuit, they do not magically solve the problems of designing a quality loudspeaker using real-world drivers. Duke
Quote from: Roger A. Modjeski on 30 Jun 2008, 04:41 amDear Turbo,Please post a list that shows that 99.5 % of speaker crossovers are more than simple slopes. If you can realize your transfer function at the speaker level then you should be able to also create the same transfer function at line level. Then we could enjoy the reduction of intermodulation and other problems amplifiers face when asked to handle full range signals and we can select amplifiers which have particularly good sound at different power levels.Certainly you realize that essentially every crossover has some level matching. So right off the bat you'll either have to add an attenuator, or the much worse but probably more often taken route of using amp gain (if it has one) as a volume control. I'd say that covers the 99.5% estimate.It's not about if you can do the same thing at line-level, any transfer function can be achieved at line-level. But adding BSC, notch filters, or other response shaping and equalization adds complexity and components as well. I'm speaking in the context of AudioCircle, and it's fair to say designers here don't use cut-n-dry slopes with level matching in their speakers. The designs here are more complex and more thoroughly exectuted in the crossover. Anything using a cone with any sort of break-up is going to require a complex transfer function, as will any irregularities in the FR of woofers or tweeters. But sure, it can all be done line-level.The point I keep trying to make is essentially everyone in the speaker industry does it one way for their own reasons, but you're advocating a different method. For that reason the burden of proof lies on you, not to spell out theoretical advantages, but to show us the proof. I think this site and myself included is very open minded, we're always looking for a better way. I have yet to see a product that can replace crossovers and realize the advantages you state, which are both audible benefits and cheaper to implement. If it did exist I'd be the first person in line to give it a run.