2012-07-27

Car Audio Sucks

Seriously. Why do car audio systems look like they were made by and for teenage boys? A million useless, crappy features, but none of the ones that would actually be useful. And a design that clearly ignores a decade of Apple's work on making interfaces that are clean and efficient in favor of TOTALLY AWESOME DOOD designs. Features you say? A tuner so I can listen to radio would be ok. I want at least two aux inputs. One on the back (that I can plug my ham radio into) and one on the front (for my buddy's iPod / whatever). I want bluetooth with all the bells and whistles so that my phone can stream audio using A2DP as well as not sucking too much for phone calls. You want to really impress me? Implement the bluetooth protocols for sim offloading and then _be_ an android device. I step into my car and my handset greets the car-mount, and hands over it's responsibilities. I want mixer functionality so I can have more than one channel playing at once. Want to really impress me? Throw in the ability to auto-mute one or more channels when there's sound on another. (phone call => mute the entertainment) I do _NOT_ want a CD player. Stuck in the 90's much? I'm not going to burn a CD. I don't think I even own a functional CD burner anymore. Yeah, maybe a data-cd full of MP3s would be nice, but even that is crap when compared to any of the cloud services. Watch a DVD? This isn't my living room. Sirius radio? Are you kidding me? I can have more variety with better music from any of a dozen cloud based services. Like the rest of the auto industry, these guys feel like they're in a coma. Wake the fuck up, car audio makers.

2012-05-09

Yaesu FTM350-AR fail

So, I've been looking at getting an APRS setup for a while now. The radio I really want for the job is the Yaesu FTM350. It has almost everything I want, and best of all I'm sure it'll interoperate nicely with my other Yaesu gear (the automatic range check, would be particularly handy)... but it's lacking two stupidly obvious features. These aren't difficult features to add, either, both being software. The first feature is the ability to output waypoints to a NMEA compatible GPS unit for display purposes. The Kenwood has been doing this for years now: http://www.tornadovideos.net/forum?func=view&catid=11&id=205&limit=10&start=650

The Yaesu will actually write waypoint data in NMEA format to it's com port. You'd think that means it will do all of this... but apparently this is not the case. It will only write one waypoint: yours. It took some convincing on the behalf of Tim Factor (the Amateur Radio tech support guy for Yaesu) to make me believe that this was the case. I still can't figure out what the engineers who built this were thinking. Was it "well, clearly the user is going to want to send his current location from the GPS in the radio to... an after market GPS that already has the same data?" I presume it's intended to be read by a computer for transmission up to the internets... but this is a mobile rig. I don't have an internet connection in my truck. Of course if it was giving me waypoint information about all the stuff that's coming in over APRS, and I could display that on a GPS, well, that'd be useful. Incredibly useful. Worth buying the radio and GPS useful. If I was using it as a base station, I could feed it into a computer and upload it to APRS.fi or some such. It would make sense as a feature. But as implemented the feature is not just pointless, it's a demonstration of brain-dead stupid design.

The new Yaesu also lacks digipeater functionality. This is a mobile rig, so clearly there aren't any situations where I'm going to want to use it as a repeater. You know, since it's got a built in cross-band repeater (which is one of it's major selling points, in my opinion), you wouldn't want comparable functionality for the APRS side...

I'm super annoyed because this radio has so much promise. But such glaring omissions make me scratch my head. I keep hoping that some up-and-coming company will build a radio that plugs into an android phone and is fully controllable over USB. I'd pay real money for a radio that has an interface that was designed some time after the 90's, not to mention programmability that goes beyond stunningly limited.

Kettle Javascript fail

I was working on a javascript step in a Pentaho Kettle script and could not for the life of me figure out why it wasn't working as expected. An excerpt follows. It takes a bunch of boolean values and ORs them down to a single boolean.

var is_holiday = (is_variable_date_holiday || is_fixed_date_holiday || is_nth_day_of_month_holiday)


And... it doesn't work as expected. Apparently the handling of boolean type data is somehow going insane. My final solution:

var is_holiday = false;

var holiday_name = '';
if (is_fixed_date_holiday == true)
{
is_holiday = true;
holiday_name = fixed_date_holiday_name;
};
if (is_variable_date_holiday == true)
{
is_holiday = true;
holiday_name = variable_holiday_name;
};
if (is_nth_day_of_month_holiday == true)
{
is_holiday = true;
holiday_name = nth_day_holiday_name;
};

var is_working_day = (is_weekend == true || is_holiday == true) ? false : true;

Yes. It really is that ugly.