and undercurrent on this forum.
Thought I would add my 3 cents and post this in DIY. As always, do as you wish with your own gear, but there seems to be this fairly constant disregard for the driver and application engineering that JBL did. The window of acceptable use is often narrower than people want to think it is for many JBL drivers and products. Indeed, it seems it is the rarer case for a driver to have a pleasantly and suprisingly wider range of applications.
Considering what JBL designed a specific driver for and attempting to use it in it's proper application, or one in which the variables do not put the dirver/crossover/system outside it's parameters, is what sets some peoples thinking apart from others. They just can't contemplate the value of using a driver/product in some way at odds with or outside it's performance parameters. The beauty is in recognizing and then properly implementing the driver/product in order to revel (no pun) in it's best abilities.
It is a narrower, more focused pursuit than some realize. The education process here involves understanding this and then asking questions that deal with using the product correctly, not outside it's intended application. There doesn't seem to be much wisdom in bucking JBL's efforts and results, particularly with drivers. There is more going into the design and refinement of JBL drivers than I think most people are aware of. I would say that it would not be unusual for a highly qualified engineer to spend a year of work just getting one driver dialed in, even with all the past knowledge base that exists.
p.s. this isn't concerning any specific post anywhere else; it has been a theme since about day one on this site
MBB