my running post 5.0 wish list

[Dean Roddey]

That was supposed to be the whole point of it being generic, that it wouldn't have to be updated. But they screwed that pooch pretty much.

[Dean Roddey]

BTW, don't expect too much in 5.1 because the HTML based client is going to be the far and away top priority. Getting that done is most definitely a survival issue, and it will be taken seriously. Other, smallish stuff can be done of course. But we have to keep our eyes on the prize for 5.1. If we can get a good HTML client out there for portable and non-Windows devices, and with all of this stuff being done for 5.0, we will finally really be able to go out there and compete.

[jkmonroe]

yeah, but some of the stuff listed is small-ish and would provide a lot of good value, and other stuff would really enhance first-timer usability. think of this list when you need to get away from the grind and have some time to add a small bit or two.

[kblagron]

Okay, here is one you can take off the list :-)

The IV /binding wasn't working, and I needed it to use my CQC Server as my .wav output to my audio system. The PlayWav() didn't work in Win7 and PlayIVWav() did - but only when I didn't have multiple RDP logins to that computer. Since I have upgraded to Win10, the PlayWav is back working, so the PlayWavIV() isn't needed at least in my setup.

Probably a low priority, but all is good on my end now.

[batwater]

That was supposed to be the whole point of it being generic, that it wouldn't have to be updated. But they screwed that pooch pretty much.

Perhaps it is a mater of Yamaha adding new function types and the driver not knowing what to do with the new types, can't handle, and so won't connect. There was a fairly big streaming technology jump between the version of the protocol doc used to build the driver (6 years old) and the most current documentation. Yamaha V2 Driver Error was the thread we discussed back in January.

-Ben

[jkmonroe]

updated to add increased hue support for groups/scenes and tunable white bulb.