|
Home | Forums | Rules | Articles | diyAudio Store | Blogs | Gallery | Wiki | Register | Donations | FAQ | Calendar | Mark Forums Read |
Software Tools SPICE, PCB CAD, speaker design and measurement software, calculators |
|
Please consider donating to help us continue to serve you.
Ads on/off / Custom Title / More PMs / More album space / Advanced printing & mass image saving |
![]() |
|
Thread Tools |
![]() |
#951 |
diyAudio Member
Join Date: May 2006
|
A question about xover resistors - how you would select the power rating for resistors in the xover attached - what are typical rules of thumb for the resistors in the signal path, those across the speaker and in the resonance branches ?
- S2 is mid short/long-term power handling 80W/250W, - S3 are two woofers 10" in parallel, rated noise power 190W each |
![]() |
![]() |
#952 |
diyAudio Member
Join Date: Nov 2009
|
To look at power dissipation in XSim select AddGraph, more, Component Power Dissipation (W). That will display a graph where you can select the components to look at. Then adjust your source (put mouse over source, then press t) to the power level you want. You can also adjust the impedance to match your drivers/crossovers.
IIRC (and someone correct me if I'm wrong) XSim applies the power level equally across all frequencies. In most real music the majority of power is in the lower octaves. So XSim may overstate the power used in the tweeter components. Anyone have more information on this? |
![]() |
![]() |
#953 |
diyAudio Member
Join Date: May 2006
|
That's nice
![]() |
![]() |
![]() |
#954 |
diyAudio Member
Join Date: Nov 2009
|
Pawel –
Sorry for my much delayed response about your MR18REX. Thanks for posting your XSim .dxo file – it had all the information I needed. You mentioned that this will be a 3-way speaker. I noticed Madisound has a 3-way kit that uses the M18REX. It’s called the CX871 (LINK and LINK) and was designed by Peter Noerbaek of PBN Audio. All the important information is listed: frequency response, crossover components and values, crossover points, individual driver responses and cabinet information. So that’s a great place to get ideas from a respected designer. You could use the same woofers as the CX871 and duplicate the full design. Done deal! Or you could use the MR18REX portion of the CX871 crossover and use different low end driver(s). The requirements of the low end driver(s) and crossover would be 90 dB sensitivity and a Linkwitz-Riley 24 dB/octave roll off at 300 Hz. I got intrigued and created a couple of simulations: The first is a sim of the published CX871 MR18REX xover. I did modify your .frd and .zma files (changes explained at the end) for the sim. Some notes: - The simulation FR matches the published FR quite well with a few small differences. It’s also very close to the CX871 driver roll offs and crossover point at 2100 Hz. - I used the 20 gauge inductor DCRs per the published design. The CX871 crossover does have a lot of parts and one very large (5.8 mH) air core inductor. So I created a second simulation based on the original crossover, but with the goal of using fewer, less costly and more standard value parts. Results of this simulation: - The frequency response, crossover point and driver roll offs are very close to the original CX871 sim. - The tweeter xover has four fewer parts. Contour shaping parts were replaced with a single resistor. - The midrange xover has three fewer parts, most notably the 5.8 mH inductor. My take away is this: While the MR18REX is a nice driver it does take a lot of components to make it shine. Lacking my own measurements I would use the CX871 MR18REX crossover as-is and keep the cabinet dimensions (especially baffle width) and MR18REX volume (~14 L) the same as the CX871. The woofer section could be changed (with a new woofer crossover) as long as it meets the CX871 requirements. I personally wouldn’t replace the woofers unless I had in-cabinet measurements of the new woofer(s). Hope this helps and good luck! Regarding the input file changes I made (and my opinion about what is important when using .frd and .zma files copied from manufacturer’s graphs): 1. Seas used a 12L closed box when measuring the MR18REX midrange and tweeter responses (stated in the data sheet). This is a very fortunate exception to the normally published Infinite Baffle (IB) responses. Had you started with IB responses (i.e. no cabinet) the cabinet effects shown below would need to be simulated and added/merged with the IB responses to approximate the in-cabinet responses. Lots of important things change when you put a driver in a cabinet! Using the Seas 12L closed box data is close enough for a first sim. Cabinet Effects = Baffle step and diffraction effects (midrange and tweeter), low end response changes (midrange) and impedance changes (midrange) 2. I created a new midrange .frd file. Your file had a marked response rise from 15 to 20 KHz that I didn’t see in the Seas response graph. It’s a small nit really, but I went ahead and retraced the midrange response. 3. Files copied from response graphs don’t contain important phase data. I used XSim to create phase data for all four files. If you’re not familiar with this capability, here’s how to create phase data: - Right click on a driver and select the Tune option. Then select the “derived” option in the “FRD phase source” box. In the next window you can define the frequency and slope of the lower and higher tails. Tails are fixed slope extensions to the data that increase the accuracy of the generated phase data. - To create phase data for the impedance file select the “derived” option in the “ZMA phase source” box. - To see the FR effects of the phase data: Open one of simulations and perform the above steps for both drivers, but select the “as measured” option instead. Notice the change in the system response without phase data. Then repeat the above steps again and re-select the “derived”options. You’ll then see how I tailed the .frd files. 4. Acoustic Centers: The Madisound information does have acoustic center timing, but it’s somewhat confusing. The tweeter crossover is marked as “-20.87 usec” while the midrange is marked as “Zero Delay”. I would interpret this to mean the tweeter’s acoustic center is actually behind the midrange driver. That’s possible, but I haven’t seen it happen very often. It all depends on how the negative sign is interpreted. This is a small value (0.28” delay) and has a small impact on the simulation. Since I had questions about the value’s sign and the impact is small I just left mod delay set to zero. Last edited by ernperkins; 5th February 2021 at 09:07 PM. Reason: typos |
![]() |
![]() |
#955 |
diyAudio Member
Join Date: May 2006
|
I really highly appreciate your detailed, insightful and value-adding analysis and comments.
Your improvements to the files are quite useful, they are not attached ? - can you please add them ? I do not want to sound as a know-it-all and evangelize here but I thought I present my POV as a sort of return for your effort and input as it is based on quite a bit of research using quite unique technical means. I have some distance to 'respected designers'. In particular using 4-th order xovers may look smart but for me is a recipe for a no-chance-for-good-sounding speakers. If I understand it correctly all xovers are 4-th order (I am not very experienced in reading analog xovers, I am a passer-by in this area, my focus is advanced DSP and digital xovers and audio processing). I do not understand the delays given in this brochure as a 4-th HP has a very different delay than LP. To me this kind of a xover from a respected designer ![]() It is much more about transients integrity and waveform preservation, especially the attack part. For me of course ![]() But the ultimate verdict is audition, also for my designs, no matter what high tech and calibre advanced arguments I would present here ![]() So I'll finish the xover according to my time alignment preference soon, the boxes are already built, there is also a classical non-time alignment version of xover so when the verdict is known I might let know here ![]() Last edited by pawelp; 6th February 2021 at 09:05 AM. |
![]() |
![]() |
#956 | ||||
diyAudio Member
Join Date: Nov 2009
|
Quote:
Adding the phase data is internal XSim - you'll have to follow the steps in my previous post and add the phase data yourself. Quote:
Quote:
Quote:
Last edited by AllenB; 6th February 2021 at 09:37 PM. Reason: Fix tags |
||||
![]() |
![]() |
#957 |
diyAudio Member
Join Date: May 2006
|
Disagreement is in most cases a better option
![]() Well, if the (speaker) frequency response was so overwhelmingly important then digital correction at the signal level and then active xovers would have cleaned the audio market since years. No matter what sophisticated analog xovers you may design it is just a humble fraction of the power you have with DSP. Why do you think it has not happened yet and the analog audio world holds up fine ? A question is a bit unfair as this is a specific area of human activity and we are now in the space where more objective criteria like noise level are already no longer on the table and the game has become very nuanced and subjective. But still it seems the audiophiles converge to some sort of common high fidelity reference ? One more argument - do you think there is any sginificant correlation between frequency response of most renowned and expensive speakers and their subjective rank ? ![]() But above all it is only audio, our nice hobby ![]() Last edited by pawelp; 7th February 2021 at 07:50 AM. |
![]() |
![]() |
#958 |
diyAudio Member
Join Date: Aug 2019
|
![]()
How do i get the right speakerdata. Where can i find de files?? For instance for the Seas Prestige FA22RCZ (H1597-08) 8" Fullrange
|
![]() |
![]() |
#959 |
diyAudio Member
Join Date: Oct 2017
Location: Lake Mary Florida
|
Is there anyone on here that lives near Orlando or Daytona Florida that’s using this cool software ?
I have a few speaker projects that I need help with on the crossovers |
![]() |
![]() |
Thread Tools | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Update to Windows Passive Crossover Designer available | dlr | Software Tools | 1 | 15th May 2014 11:46 PM |
Windows Passive Crossover Designer v1.2 available for download | dlr | Software Tools | 15 | 14th December 2013 12:48 AM |
Active Crossover Designer version 2 released | CharlieLaub | Software Tools | 1 | 12th November 2012 10:08 PM |
Orcad/AutoTRAX EDA - free schematic capture/PCB designer | Ilija | Everything Else | 3 | 16th July 2003 12:11 PM |
New To Site? | Need Help? |