I am having the same problem. This is not a problem with either the TV or any individual Compute Stick, this is a compatibility issue that is beyond my level of knowledge. I have tested both my TV and compute stick with other TV's and they both work fine.
We need intel to look at the drivers and potentially how the sound it translated through the HDMI port to the TV. Intel, please look into this and give us an estimate on when this will be resolved. If I can't receive at least an estimate and acknowledgement of the issue within the next week, I will have no choice but to return the device - and warn other consumers of this incompatibility. I really like this computer so far, but it is unusable to me where I want to place it! Thanks for your help.
Also please understand that this issue is far wider than these forums would indicate, and you are currently experiencing an impact to your sales because of this, in addition to future sales.
Argh. That was actually what I was suspecting. I chatted with an Intel rep today and got a case number. I haven't had a chance to try with other monitors and do your level of validation but I mentioned to the rep that my TV is pretty much built for this kind of usage with 5 HDMI ports. My chromecast works fine etc.
I would concur that its likely a driver issue in how the sound is being outputted through the HDMI port. Do you have the same TV as well?
The rep asked me to try installing the latest BIOS as well but I haven't had a chance to check and see which version I am on. Have you tried that as well?
I have installed the latest BIOS and video driver on my device.
Seeing how this is still an issue, and I didn't hold up my end of the deal by trying to install the latest bios and driver I will give you guys another week to acknowledge the problem and begin working to resolve it.
My tv: p5002ui-b1e
audio type: frc version: 9.248
Please acknowledge the issue and confirm your companies ability to reproduce it.
This is a known issue with some Vizio models, and other manufacturers as well. The Compute Stick team is currently working with the graphics/audio driver team to get an updated driver version to fix this problem. I don't currently have an ETA on when that will be available, however.
I tested in our lab the Intel® Compute Stick STCK1A32WFC with the Samsung model CY02 TV without any problem. I just used the compute stick and the TV, no adapters, no home theater or any other accessory.
Please perform the following test. Create a back up of your documents and make a recovery of your operating system tapping F8 while the stick reboots.
It might sound very basic but please make sure the TV is set as default Audio device.
Right click the Audio icon on the lower right corner of your display, select playback devices and select your TV.
How To Change The Default Playback & Recording Audio Device
NOTE: These links are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.
Thanks for the acknowledgement Lois. I look forward to the new driver that will solve this issue, any chance we can get a beta driver? I have had other companies give out beta drivers when incompatibilities are making the product unusable.
EDIT: Why are my posts/this thread being moderated now? I don't recall the earlier discussion being moderated, needing approval before a post shows up. Admins can you expand on what is going on? intel_adminCommunityAdmin
You haven't been added to a list of people needing moderation. It's something in our moderation engine that isn't working perfectly. I'm sorry that you are experiencing these moderation delays. We are working on improving the moderation engine, but I don't expect any changes to what you see in the next few weeks. We would turn moderation off completely. Unfortunately, there are spammers that will flood the forums if we turn off moderation.
Support Community Manager
Can we get an update on the drivers status? It has been a few weeks since we have heard anything and I am sure others are getting antsy along with myself.
I noticed an unsigned driver posted to the windows support downloads page that was released on 7/17/15, so I installed it in hopes that it would solve the issue. Unfortunately, this didn't help at all. So basically just looking for an update.