JBL Speaker List - draft!

[4313B]

Hey Giskard - 'any chance of getting those tables in spreadsheet form, or at least the last one in a little higher resolution? 'Anything I could do in return?

John

They are images of Excel spreadsheets (converted over from Quattro Pro spreadsheets from the very early 90's). I simply pasted them into Paint Shop Pro for ease of posting. They'll end up in the Technical Reference section at some point.

**I have attached it as an Excel S/S but renamed with ".doc" extension. So if you save it and rename it to ".xls" extension you can open it in Excel.

I looked at it briefly. Several errors but you've got the idea. For the Pro info you can look here:

http://www.jblproservice.com/navigat...%20Charts.html


BTW - I'm still looking for a DBA who can build us a relational database for the site.

[LE15-Thumper]

In the 004 system there is a 4 before the D123, what does this denote ?
I noticed a 2 or 4 in this column on other systems.

Thanks

[4313B]

In the 004 system there is a 4 before the D123, what does this denote ?
I noticed a 2 or 4 in this column on other systems.

Thanks

http://www.lansingheritage.org/image...1957/page8.jpg

[LE15-Thumper]

OK, Thanks

[Phil H]

Giskard,

Those are nice lists. I was curious about the notes on the first list. Are you working toward a complete list of enclosures for each system, or are they what you know from your personal experience? I ask because I noticed that a number of cabinets aren't listed that can be found in the literature on this site. Here is a link to one I know http://www.lansingheritage.org/image...1967/chart.jpg

I too started making a similar list. I just did it to help me learn what's what.

Roy,
I down-loaded your list but I need to install Excel on my computer (I've used Lotus 123 since DOS days). Probably next week, I'll install Office. I look forward to seeing your list.

[4313B]

Giskard,

Those are nice lists. I was curious about the notes on the first list. Are you working toward a complete list of enclosures for each system, or are they what you know from your personal experience? I ask because I noticed that a number of cabinets aren't listed that can be found in the literature on this site.

The various spreadsheets have different info depending on who at JBL did them. Some info is missing. Some info was incorrect and I corrected it. I have always meant to consolidate the various lists but haven't been too fired up to do so because it really requires a relational database as opposed to spreadsheets. Besides, I know all the information so it isn't really a chore to look it up. I know where it all is. I'll get to it eventually and ask Techbot to deal with it accordingly.

[remusr]

Giskard & Phil,

thx for the link and kind comments, I will work on my Excel list using your pdf's and the link info.
*I never did learn databases but may try yet! As an O&G engineer I always was able to get by with 123 or XL....
Later, Roy

[hapy._.face]

I started putting drivers (only) in an excel spreadsheet so that I could ref certain values. The categories were:
Type (15", compression, etc)
Model
PwrCap (watts)
Imp
Freq (range)
Sens
Fs




Then it occurred to me that this is a waste of time (redundant) if others are doing it, too. "Why not consolidate all of the information into one unified database," I thought.

The concern for what program to use came up. I have determined File Maker Pro (version 5 or better) would be suitable. It is Mac/pc stable. FMPro is manipulative in ways you cannot imagine. Plus- the info can be exported to Excel or just about any other program (with limited features, of course).


Say I had a subwoofer and wanted to build a 4way around it. I can sort the drivers by freq response, or impedance, or whatever value I wanted until I found suitable candidates for my project. FMPro will sort it in descending/ascending order or whatever you can dream up.



Another database can keep track of "systems" (for example). A link from my driver of choice (2235H, for example) will put me in the 'systems' sub database where I can read the specs of the systems that utilized a 2235H as a stock component (4350 for example). You get the idea...we could just link to pages already scanned in the library for decreased data entry.



Huge task, I know. But it could be chipped away at over time until complete.

[Titanium Dome]

FileMaker Pro is an excellent suggestion. We're using FM Pro 8.0 and FM 8.0 Server at work, and it is sweet. However, we had to get a FM software solutions guy to build what we needed. Thankfully, he was willing to do some work pro bono since we are a nonprofit organization.

Our FM 8.0 Server runs on an Apple XServe G5, but our clients are split about 50/50 between Mac and Windows. We've got four sites that have to log in to the system and utilize the server from remote locations. Works like a charm.

Once up and running, it's rock solid, and it's almost idiot proof from the end user point of view.

[hapy._.face]

Too bad about the FMpro going bye bye. It rocks.

Of course, all of that capability is overkill for a list of drivers and/or systems! Being able to sort various parameters from those drivers/systems, and it's overall stability/versatility mades it the obvious first choice. But if it's out- it's out.

I guess the biggest issue would be the data entry, huh? :shock: :shock: :shock:
Talk about burn out!

I can't imagine the task of sorting through years' worth of varying standardization and all the typos. wow. The old saying 'If you're gonna do it-do it right' definately applies here.

Another suggestion: It could be launched (intitially) by first entering the most basic elements (driver model#s/system model#s, for example) just to get a working architecture. Then (as time permits) adding/focusing one list of values at a time by decending importance: Dimensions, wattage, impedence, freq range, etc until you get down to the small details. All of this vs waiting until it's totally complete- as it might be more of an evolution of data.

Let me know if I can be of any help in this project, as I believe in it 100%.

EDIT: '59- You jumped in with your post as I was typing mine and it echoes what I was thinking. So, "Yeah" ditto what you said!! Getting the platform functioning first is paramount.
Giskard- Name your position. We are here if you need us- we'll shut up if you don't. No sense in taking all of the work on yourself- but I gather you are a tortured soul anyways . I fully understand.

[4313B]

Huge task, I know. But it could be chipped away at over time until complete.

It is an enormous task. I already have all the documented system lists. I don't have Filemaker Pro anymore so that negates it's use. Don has already suggested a certain software package and it will require me learning how to use it. I'm still waiting to see if the whole thing is even feasible. Should know by the end of March. I'll open that thread after we find out.

[JBLnsince1959]

It is an enormous task. I already have all the documented system lists. I don't have Filemaker Pro anymore so that negates it's use. Don has already suggested a certain software package and it will require me learning how to use it. I'm still waiting to see if the whole thing is even feasible. Should know by the end of March. I'll open that thread after we find out.

Early this year I PM'ed you offering help ( it is what I do for a living). Offer still stands ( altho my time is limited as I own my own company), however, I will not interfere or get in way....

What was the package Don mentioned?

I'll throw in my two cents here. Everyone seems to be focusing on the WORK ( data entry etc) and Software. That is really step 3 and 2 respectively. First thing is to clearly define EXACTLY ( PLAN,PLAN,PLAN ) what you want this puppy to do, what information it is to hold and how the user is to get to it.

Once this is done then only put in enough information for 3 or 4 systems and TEST,TEST, TEST, TEST, TEST. Once that's done then only the grunt work of data entry remains ..... This would be really fun and simple as projects go...nuff said....

[JBLnsince1959]

First thing is to clearly define EXACTLY ( PLAN,PLAN,PLAN ) what you want this puppy to do, ....

I'll be more clear and then have to get to work ( been putting 7 days a week for 3 months)....

What is the Mission Statement for this database........ ( leave out details about software, data entry...only what it is to do for the user..but be very exact on that. That is our first step.....

would[/b] be the data entry, huh? :shock: :shock: :shock:
Talk about burn out!

I can't imagine the task of sorting through years' worth of varying standardization and all the typos. wow. The old saying 'If you're gonna do it-do it right' definately applies here.

When climbing mountains never look all the way to the top but only at your next step ( keeps the mind focused and calm)

what is our mission statement...what is this to do for the user..that's the only thing we should be thinking about

[sajt]

that's godd

and ALTECs??

[Steelyfan]

Here are a few screensnaps from my humble music database (under construction)
-the first is a table view of the media items (currently old cassettes)
I could have even included pictures of the album cover.
-the second shows a small example of the value of a database , how you can retrieve media info per artist.

replace "media" by "enclosures" , and "artist" by "driver" (or vice-versa, or whatever) and you have a start for T.L.H.S.L.