Log in
Register
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Low Earth Orbit
DIY Audio
Steering advice for those serious about DIY speakers.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Phil Graham" data-source="post: 24481" data-attributes="member: 430"><p>Re: Steering advice for those serious about DIY speakers.</p><p></p><p></p><p></p><p>Starting out with a product that everyone needs makes sense, but it also makes the underlying assumption that result you produce is up to the standards of performance you have envisioned in your mind. If the product doesn't perform, you all have collectively created expensive paperweights.</p><p></p><p>Think about comparing this to the open source software (OSS) community. In the OSS community, people develop software tools that many have mutual needs for and aid their business. Examples like Apache and nginx help everyone who has serving web pages as part of their business, but didn't want to have to pay for such software. When the software is done it can be widely distributed for very little cost, recreated as many times as needed.</p><p></p><p>In contrast, you have a product that every person involved must build individually, completion of the design involves a substantial cost to each builder, and there is no easy way to divvy up the design responsibilities amongst the community.</p><p></p><p>To return to the OSS comparison, the people involved with this project don't know how to "code" (i.e. they don't deeply understand loudspeaker design). Nor do these people have the "code development/debug/etc" tools (i.e. the loudspeaker measurement and design equipment and software). Hopefully this analogy will help expand some of the potential absurdity of the project.</p><p></p><p></p><p></p><p>If you need a pile of wedges, I would strongly encourage purchasing them from a manufacturer. Indeed I would posit that the very act of needing a pile of wedges would preclude one from having the time to build them! You'll be much happier if you treat your attempt at the coax design as lottery money, rather than something your business is going to need to rely on.</p><p></p><p></p><p></p><p></p><p>I suspect this project will increase the participants' appreciation for the actual engineering in the boxes mentioned above. There is extensive engineering in horns, driver design, and crossovers. Especially if you try to build to a similar price point, you are going to find that the passives in the XOs get pricey quickly.</p><p></p><p></p><p></p><p>I don't anticipate you meeting your performance goals without hiring a third party to do your XO design, and that point, how much are you really DIYing, and which members of the build pay for those design services?</p><p></p><p>Just some counterpoints to consider...</p></blockquote><p></p>
[QUOTE="Phil Graham, post: 24481, member: 430"] Re: Steering advice for those serious about DIY speakers. Starting out with a product that everyone needs makes sense, but it also makes the underlying assumption that result you produce is up to the standards of performance you have envisioned in your mind. If the product doesn't perform, you all have collectively created expensive paperweights. Think about comparing this to the open source software (OSS) community. In the OSS community, people develop software tools that many have mutual needs for and aid their business. Examples like Apache and nginx help everyone who has serving web pages as part of their business, but didn't want to have to pay for such software. When the software is done it can be widely distributed for very little cost, recreated as many times as needed. In contrast, you have a product that every person involved must build individually, completion of the design involves a substantial cost to each builder, and there is no easy way to divvy up the design responsibilities amongst the community. To return to the OSS comparison, the people involved with this project don't know how to "code" (i.e. they don't deeply understand loudspeaker design). Nor do these people have the "code development/debug/etc" tools (i.e. the loudspeaker measurement and design equipment and software). Hopefully this analogy will help expand some of the potential absurdity of the project. If you need a pile of wedges, I would strongly encourage purchasing them from a manufacturer. Indeed I would posit that the very act of needing a pile of wedges would preclude one from having the time to build them! You'll be much happier if you treat your attempt at the coax design as lottery money, rather than something your business is going to need to rely on. I suspect this project will increase the participants' appreciation for the actual engineering in the boxes mentioned above. There is extensive engineering in horns, driver design, and crossovers. Especially if you try to build to a similar price point, you are going to find that the passives in the XOs get pricey quickly. I don't anticipate you meeting your performance goals without hiring a third party to do your XO design, and that point, how much are you really DIYing, and which members of the build pay for those design services? Just some counterpoints to consider... [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Low Earth Orbit
DIY Audio
Steering advice for those serious about DIY speakers.
Top
Bottom
Sign-up
or
log in
to join the discussion today!