January 15th, 2011, 07:35 PM
They can leave the submitting of bugs open while leaving the rest of the trackers\logs closed to the public. Its the being viewable part that is hurting them in some respects. Also, I would take a look at the Bigs being submitted 1st, making sure that these are new, and not rehashed topics...
Originally Posted by SecretAsianMan
Just takeing a look at the recent submitions many look to be feature requests\suggestions and not actual bugs. Becasue people are using this as a feature request\suggestion tool as well the number of suggestions could far outweigh the ability to fix them\close them.
Bahh but this is kind of off topic since this thread should be about the firmware that was rleased the other day. Sorry all for continuing this discussion.
Last edited by Ph8; January 15th, 2011 at 07:41 PM.
January 15th, 2011, 07:38 PM
Yes I thought so too.. But as I was watching different videos it was subjective rather than something I could do a real comparison too. I even went and checked my settings to see if it was 0 - 255 and inducing the clipping.
Originally Posted by trooperlooper
Agree it seemed darker or clipping blacks.
January 15th, 2011, 08:03 PM
I installed RC2. So far it's working great, haven't run into any new problems, didn't have to do or reset or anything -- all my local content is there, web content is working better overall, etc.
However, I am still having trouble using Willow.tv to watch cricket:
The good news is that with the RC2 browser Willow.TV loads up much faster and I can actually log into my account now (which wasn't possible with the Boxee firmware prior to this), and all of the archived/replay videos and live streams on Willow.tv that are in Flash players load up pretty quickly, with decent video (even in full-screen mode) and good audio (a lot of their older videos were archived in Silverlight players, which of course don't work on Boxee; but I'm not going to be watching these old matches anyway, so no worries).
The problem is that after about 30 seconds of watching any video (full-screen or embedded), the entire screen is replaced by an error message from Willow.tv saying that either the Internet connection has been lost or there's a problem with the browser's security settings and/or cookies.
My Internet connection is fine, so I'm guessing that it's an issue with security settings or cookies.
If I then click "back" on the Boxee Browser I'm brought back to the Willow.Tv page I was on previously, and I see that I'm still logged in (which makes me think that the log-in cookies maybe aren't the problem) and I can start up another video. But after 30 seconds the error occurs again. Tested this tons of times, always with the same result.
The Willow.tv error message suggests some fixes, but they're specific to Internet Explorer. The message says to "turn off Protected Mode" if you're using Windows Vista. And for all versions of IE to "turn off 'Require server verification (https)' " and "add http://*.willow.tv to the list of Trusted Sites."
But for Boxee, what should I do?
I'm going to write the support guys at Willow.tv -- they've got Willow.tv working on all the major web browsers now, including the iPhone version of Safari, and they've even got a Roku app -- so hopefully they can get this working on Boxee's browser too (while we wait for a Willow TV app for Boxee). . .
But I'm reporting it here in case it's something that Boxee can help with; I'm thinking it might be a browser bug that's affecting other sites as well.
Last edited by Lukecro; January 15th, 2011 at 08:19 PM.
January 15th, 2011, 09:09 PM
Updated and once again Pandora plays but has no sound. I am confused as to why others are not seeing this.
Originally Posted by kdnoel
January 15th, 2011, 09:10 PM
I updated to RC2 and it was working great. We decided to take a trip to a local casino and after reading that they just added a feature to their rooms called guestlink we decided to bring the BB with to try it out. The guestlink is a new thing we might be sering in the future at hotels. It has every input port imaginable (hdmi,svideo,usb,sd cards, etc) allowing you to connect your portable devices and view them on the tv.
I plugged in the BB and booted it up to a red screen. When it boots I see the loading screen. I am unable to get into the restore menu either as it results in a blue screen as well. I had the BB set for 1080p st home and I am unsure what the tv in this room is capable of. It seems as though the BB may be fixed on the previously set resolution or something and I am not able to change it at this point. I'll need to plug it back in at home when we get back to see if I get the same results or not.
Might be a good feature to have the display reset somehow, maybe similar to how the PS3 resets when holding down the power button....
January 15th, 2011, 09:22 PM
For the record, I have audio with Pandora as well.
Originally Posted by kdnoel
January 15th, 2011, 09:28 PM
Installed RC2. getting better but still bugs
Local DVD playback:
Lost sound 20 minutes into the Muppet Movie
Some play with sound and no video
Some videos just stop 1/3 in exit
One video playback even caused the boxee box to restart.
(all of these work perfectly when being stream to my HTPC boxee install)
I get an error often about "attempted too many times, failure", then it stops
When a new songs starts, the volume is loud, then evens out
Then while playing, the volume of the song will go up and down
Been trying for three weeks to start the GymBox app, but it will not activate. Gymbox support can't figure it out and no solution from Boxee team on it yet. That was the only thing my wife was interested in and I can't get it running.
Starting to worry that Netflix won't make it by month end at this rate. Vudu still not available and at this rate, I expect when it does launch, it will have lots of bugs.
So close, still so far away.
January 15th, 2011, 09:29 PM
I just updated as well. All is good so far. I did notice one issue. Mediafly app has no sound. I will try to post other issues as I find them. Anyone able to resolve this?
January 15th, 2011, 09:43 PM
Quite a few of us seem to be getting 'loss of sound' problems... perhaps if relevant to the situation in which you lose sound, you could see whether there's any sign in the progress bar of much-too-rapid progress. If the progress bar is whipping along like that it would seem to indicate loss of clocking / freewheeling so it's trying to play back at a sampling frequency it can't reproduce.
January 15th, 2011, 09:50 PM