View Poll Results: Do you think Boxee will fix HD Audio Dropouts?

Voters
68. You may not vote on this poll
  • Yes

    10 14.71%
  • No

    58 85.29%
Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: Do you think Boxee will fix HD Audio dropouts?

  1. #1
    Join Date
    Jul 2011
    Location
    Raleigh, NC
    Posts
    327

    Default Do you think Boxee will fix HD Audio dropouts?

    Well time for another poll Do you think Boxee will ever release a fix for HD Audio dropouts? It's a 15 month old Jira bug and I'm curious as to whether people have finally lost faith or if there are still some believers out there. Boxee's lack of response to this bug for the last 5 months or so leads me to believe it will never happen. Feel free to leave comments but don't forget to cast your vote!
    Last edited by nfodiz; April 23rd, 2012 at 07:31 PM.
    Boxee Box rev A1 fw 1.5.1.23734 wired NFS - Boxee Box rev A2 fw 1.5.1.23734 wireless NFS
    WD Mybook Live 3TB fw 02.11.09-053 NFS - Seagate BlackArmor NAS 110 1TB fw 1000.1211
    Asus RT-N66U fw 3.0.0.3.151 -> Trendnet TEG-S80G 8 port Gigabit switch
    WDTV gen1 - WDTV Live - WDTV Live Streaming

  2. #2
    Join Date
    Sep 2011
    Posts
    477

    Default

    Unfortunately, I think we may just have to deal with the audio situation as it is. Avner's latest fireside chat seemed to indicate Boxee has not even received the new Intel SDK, and without it we won't be seeing a fix. Sux to be us...
    Router: ASUS rt-n56u (Black Diamond)
    Server: Intel Quad Core 8200, Radeon 3450, 4GB RAM, Windows 7 Ultimate, Wired Gigabit
    Boxee Box: latest firmware, Wired Ethernet
    Connectivity: Netgear AV500 Powerline Adapters

  3. #3

    Default

    Quote Originally Posted by drunkwithpower View Post
    Unfortunately, I think we may just have to deal with the audio situation as it is. Avner's latest fireside chat seemed to indicate Boxee has not even received the new Intel SDK, and without it we won't be seeing a fix. Sux to be us...
    I agree. Avner's comments sounded grim concerning this fix.

  4. #4
    Join Date
    Jul 2011
    Location
    Raleigh, NC
    Posts
    327

    Default

    Quote Originally Posted by drunkwithpower View Post
    Unfortunately, I think we may just have to deal with the audio situation as it is. Avner's latest fireside chat seemed to indicate Boxee has not even received the new Intel SDK, and without it we won't be seeing a fix. Sux to be us...
    Something about that still smells fishy to me. At one point they claimed it was fixed and they could not reproduce the dropouts anymore on their development boxes. How could they have fixed it without the new SDK? Can you add fixed drivers to development boxes without having the need for the updated SDK that fixes the issue?
    Last edited by nfodiz; April 23rd, 2012 at 07:45 PM.
    Boxee Box rev A1 fw 1.5.1.23734 wired NFS - Boxee Box rev A2 fw 1.5.1.23734 wireless NFS
    WD Mybook Live 3TB fw 02.11.09-053 NFS - Seagate BlackArmor NAS 110 1TB fw 1000.1211
    Asus RT-N66U fw 3.0.0.3.151 -> Trendnet TEG-S80G 8 port Gigabit switch
    WDTV gen1 - WDTV Live - WDTV Live Streaming

  5. #5

    Default

    Quote Originally Posted by nfodiz View Post
    Something about that still smells fishy to me. At one point they claimed it was fixed and they could not reproduce the dropouts anymore on their development boxes. How could they have fixed it without the new SDK? Can you add fixed drivers to development boxes without having the need for the updated SDK that fixes the issue?
    That question occurred to me as well. Maybe they had a beta version of the SDK for testing that won't be finished or given the green light by Intel. Whatever the real story is this is a very frustrating issue for those of us with HD capable receivers.

  6. #6
    Join Date
    Apr 2012
    Posts
    3

    Default

    I voted NO, but I really HOPE they do... I love my Boxee, but this bug is driving me insane!

  7. #7

    Default

    not for the existing hardware. maybe BB v2.0 (if there is one).

  8. #8
    Join Date
    Nov 2010
    Posts
    102

    Default

    It's a shame and a complete joke what Boxee is doing here!! Promising to fix this crucial bug and getting customers to believe and buy this ... and at the end betraying customers in such a blatant way :-(

  9. #9
    Join Date
    Dec 2010
    Location
    The Netherlands
    Posts
    183

    Default

    Quote Originally Posted by nfodiz View Post
    Something about that still smells fishy to me. At one point they claimed it was fixed and they could not reproduce the dropouts anymore on their development boxes. How could they have fixed it without the new SDK? Can you add fixed drivers to development boxes without having the need for the updated SDK that fixes the issue?
    Actually they claimed that they got an update from Intel that seemed to have fixed the bug. Intel probably had built a version of the Boxee Box firmware with their new SDK from the source code provided by Boxee and shipped the resulting firmware back to Boxee so they could test if this really fixed the problem.

    Look, I've dealt with Intel development tools before and believe me when I say that those guys are not the fastest when it comes down to releasing updates and updated versions of their development tools. Even then they sometimes manage to mess things up. The first release versions of version 11.0 of their C++ compiler came with an optimizer bug that would eliminate functional code from inner loops! It made our software incredibly fast, but non-functional.

    Maybe they learned from that incident and now do more rigorous testing before releasing their tools to end customers.

  10. #10

    Default

    I personally feel that we may be barking up the wrong tree here. Has anyone tried to directly talk to Intel on this issue? We should all be spamming their email addresses with questions and concerns about the SDK getting to D-Link.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •