Pioneer 1021 / 1121, Airplay, You suck

After a year of owning both a Pioneer VSX-1021 and a VSX-1121, I would never ever buy Pioneer equipment again.

The Airplay software on the Pioneer crashes a lot. When it doesn't crash, it plays music out of sync with other Apple airplay devices. 

The HMG server? Who let that ship? Did they look up from their Atari 2600 for more then a few seconds before saying "Menus! What sort of crazy new concepts for an interface will you think of next? Ship it!"

Their support for their iPad and iPhone application has been non-existant.

On the other hand, the Pioneer sounds better then my 20 year old Onkyo amp (I think). 

Someday, someone, is going to build a modern amplifier right. 

I really doubt it will be Pioneer.

You can be right, or you decide to save everyone else a bunch of time...

This is one of my favorite valgrind finds at the moment (well, last few months):

|| ==881== Syscall param sendmsg(mmsg[0].msg_hdr) points to uninitialised byte(s)

|| ==881==    at 0x386BAF3D6B: sendmmsg (sendmmsg.c:36)

|| ==881==    by 0x386DE0B4D6: __libc_res_nsend (res_send.c:1132)

|| ==881==    by 0x386DE08BDF: __libc_res_nquery (res_query.c:226)

|| ==881==    by 0x386DE097B9: __libc_res_nsearch (res_query.c:582)

|| ==881==    by 0x5E8CAC7: _nss_dns_gethostbyname4_r (dns-host.c:309)

|| ==881==    by 0x386BAD9AF1: gaih_inet (getaddrinfo.c:845)

|| ==881==    by 0x386BADD750: getaddrinfo (getaddrinfo.c:2359)

If you really want to be right, and not cost a lot of other people time when you know you are right and valgrind is wrong. You could leave a snarky comment in the code where you create a fix to silence the valgrind error.

Or you could decide to not fix the warning, and cost a lot of other developers their time as they trip over you academically correct code which spews errors when run through valgrind.