• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

TS Parameters for JBL K-150

Count Bassie

Supporting Member
Jun 10, 2006
16,784
64,486
Smithfield, RI
I've found a .pdf of the TS specs for the JBL K-140, but they don't seem to load properly into WinISD... maybe I'm not doing something right, which I suspect. Anyone here have these specs, or has done such a WinISD project with that venerable old driver?

:help:

Thanks!
 
I've found a .pdf of the TS specs for the JBL K-140, but they don't seem to load properly into WinISD... maybe I'm not doing something right, which I suspect. Anyone here have these specs, or has done such a WinISD project with that venerable old driver?

:help:

Thanks!

You mean, it doesn't model the driver correctly? Make sure you didn't transpose any of the Q parameters.
 
WinISD can be real nitpicky if everything isn't dead on out to the n'th degree. Load just a few specs, get it to accept the driver, open new project using that driver...then hit the dropdown and edit/fill in the rest.
 
Huh?... :confused: :p

I picked up the JBL in a swap- I traded a Studio Projects B-3 mic I never use anymore and a couple disregarded-but-working-fine pedals for it. It's now residing in an EAW VB-125 cab, which is about 4 cu ft, and as far as I know a recommended volume for the driver.

I have the ports extended though from when I had a 3015 in there, and I figure I might have to re-size 'em for the K-140.

'S'it...
 
IMO, WinISD is one of the most user-unfriendly piece of software I've ever used.The least it could do is to tell the user what exactly had gone wrong so the user can correct it instead of making the user guess and try to get the parameters right by trial and error. If it was open source I'd go tear into it and fix it a new one.
 
IMO, WinISD is one of the most user-unfriendly piece of software I've ever used.The least it could do is to tell the user what exactly had gone wrong so the user can correct it instead of making the user guess and try to get the parameters right by trial and error. If it was open source I'd go tear into it and fix it a new one.


Ah, yes... 'tis a gift-horse with a rotten tooth... :D
 
IMO, WinISD is one of the most user-unfriendly piece of software I've ever used.The least it could do is to tell the user what exactly had gone wrong so the user can correct it instead of making the user guess and try to get the parameters right by trial and error.
I have no problems with it whatsoever. Enter only as many parameters as required for it to calculate the rest. The problem doesn't lie in WinISD, it lies with data sheets that are not as accurate as the program is.
 
Yes, that would be the case. WinISD works great for people who actually understands all the calculations involved and knows which parameters are required and which are the ones making WinISD barf. For the layman who just wants to plug the data files in and start playing with the program, it's hell. If the program provided a bit more feedback as to what it doesn't agree with and why, then it allows the layman user to fix the problem and continue. It's more user friendly and usable by more people that way.

I used to write software for a living and so I maybe bit opinionated on software design ;)
 
No offense taken whatsoever man.

I too have been working myself beyond the point of clear thinking.


Yeah, that'll cramp one up good. Have a weekend man! I'm off to make some noise on the local "Holy-Ghost Festival" circuit (i.e., fog machines, blinky-lights, and way too many subs out front...), good for loosening up the head-clog. :bassist:

We'll see if I can beat up that Hartke VX-215 cab that's been sitting in the basement!