zaubertuba

That's A "Molex 3‐Pin, " do a search on those words and you'll see dozens of generic connectors just like it. :)

I unfortunately can't speak to iPhones but I've used different Samsung smartphones alongside expensive calibrated equipment, enough to make the subjective judgement that as far the Samsung microphones go, they are "in the ballpark, but not perfect." I'd expect most cellphone mics to be similar but there's probably some variation which is what you're concerned about (though I'd wager such variation is greater between different manufacturers than different models of the same make). I guess the question is, what are you hoping to accomplish? Are you trying to come up with phone frequency response data so you can try and normalize frequency response across a wide range of field data? How accurate are you trying to be? The most scientific approach, imho, would be to get one of the calibrated microphones, like this: https://www.amazon.com/Dayton-Audio-iMM-6-Calibrated-Measurement/dp/B00ADR2B84 Borrow the same models of phones that were used for capturing the recordings you've found, and then test them all with an RTA analyzer and a known flat source playing pink noise--at the same volume, positioning, etc. This way you can create a set of "overlay" data you can use in comparing all the disparate recordings you have. It still wouldn't be perfect but probably a lot more scientific than trying to account for phone differences by ear. Sorry this is an awful lot of "heresay" for what was a very specific scientific query, but I hope it's still helpful!

Most Bose systems are indeed designed as a system...with proprietary electronics matched with proprietary driver designs. Kludging a regular amp into a setup like that will at best sound like crud and at worst damage your speakers. Bose has it's place in pro audio-my last job was at a venue with a Bose line-array installed and it sounded really good. My trio has used their L1 portable system to good effect. But honestly if it were my money I'd take One and a Half's advice. There's better, more conventional and less costly options out there!

I don't play at this level, but intuitively, but wouldn't any mechanical advantage in your physical setup would be negligible to an electrical difference you have discerned before? What I mean is, for purposes of evaluation, as much as the cable difference is a concern; Rearrange your components. Put them back-to-back if necessary. Maybe you have them in an isolated rack or something that makes this more difficult, but if I had the same quandary I'd have no problem re-connecting everything laid out on the living room floor.

@Wonders:<br /> <br /> I did Google the heck out of the issue, but came up blank. Got some useful info. from one of my IT colleagues at work, though. <br /> <br /> After I solved the problem, somebody pointed out that perhaps it's a bandwidth or priority issue between USB and PS2 ports. Like you say...who knows? It's still somewhat of a mystery to me.

Thanks Peter, but as it turns out, I was indeed barking up the wrong tree. Turned out the problem was....<br /> <br /> <br /> ....my keyboard. Or possibly the PS2 port on my Motherboard.<br /> <br /> I ran DPC latency checker and it was showing major latency spikes whenever I typed. Another ASIO buffer test I did with a Cubasis configuration tool showed that Cubasis actually lost sync with the card when I typed (it was fine if I didn't touch anything).<br /> <br /> I'm using a borrowed USB keyboard to type this. No clicking, no distortion, no crazy latency spikes. The Cubasis test shows sync is maintained perfectly even if I type like the dickens while it's running.<br /> <br /> I'm obviously exceedingly happy it was such a simple solution. I get to hold onto my 1212m after all!

@XXHighEnd:<br /> <br /> "What!? I'm using legacy drivers on an old soundcard on a spanking-new OS and they're not working perfectly?!" --All that just to say, point well-taken. <br /> <br /> The E-Mu drivers may indeed be causing part of my headache, as they continue to try to use ASIO. I suppose it's a wonder the card works at all. *sigh* I may end up having to upgrade my soundcard. Pity, because it really does sound quite decent when I'm *not hammering away at the keyboard.<br /> <br /> I still see a problem, though if Chris and others are having problems getting more modern cards/updated drivers working, then what's left? How long do we have to wait for the card manufacturers to step up to the plate?<br /> <br /> Considering this, maybe external would be a better option. How's Windows 7 for USB or S/PDIF to an external DAC?<br /> <br /> EDIT: I may be barking up the wrong tree. Some research suggests my issue may be related to some other hardware. Stay tuned!

Hi Chris - I've been a periodic lurker on your site here, and a regular over on Head-Fi for a bit. I have to say you're doing a great job!<br /> <br /> I too, was hoping Windows 7 would "finally work." I had high hopes this past couple months as I've been testing the Release Candidate. It actually installed very cleanly and I even had my Older E-Mu 1212m up and running with relatively minimal headache. This computer is my "all-in-one" HTPC, so I needed a full-featured HTPC frontend, and the Windows 7 Media Center certainly delivers the goods. The OS in general is very clean, fast, and has actually been a joy to use...except that I've had a weird latency issue with my 1212m and my keyboard, of all things.<br /> <br /> I researched and found this on the Microsoft Developer Website:<br /> <br /> <cite>The Microsoft Windows audio team is working hard to reduce overall audio latency in future Windows operating systems. An important part of this effort is to provide low-latency implementations of audio APIs in order to eliminate any need to access the KS audio components directly.</cite><br /> <br /> <cite>The plan for future Windows products is to provide built-in multimedia APIs and core services with very low latency and complete bit-for-bit transparency. These features should eliminate the need for any application program to circumvent the audio subsystem....Be forewarned that the DirectKS approach is unlikely to work on operating systems after Windows XP and Windows Server 2003.</cite><br /> <br /> That, from this page:<br /> <br /> http://www.microsoft.com/whdc/archive/directks.mspx<br /> <br /> Now, it's admirable that Microsoft seemed to be working on bit-perfect output, but this was from 2002. We're at 2009, and bit-perfect output seems still a bit far afield. If Microsoft has stuck to their guns, and DirectSound is not yet yielding true bitperfect output, I fear we're in for a long wait.<br /> <br /> It's a real pity, because I've actually enjoyed working in the OS. Double-pity because Windows 7 Media Center is the best overall HTPC frontend implementation I've seen even compared to my previous favorite, MediaPortal (which is currently breaking on 7, depending on your situation). It even does quite a few things better than MythTV and XBMC, which I'd also tested pretty extensively.<br /> <br /> It does everything except *ahem* play back cleanly while I'm working at the computer.<br /> <br /> *Sigh*....I feel like I'm going to have to wander in the desert again for another 40 years.