I have the same equipment and did not have this problem until I updated the catcher software two days ago.

cshotton said:

tomkofam said: I have the same equipment and did not have this problem until I updated the catcher software two days ago.

There definitely seems to be a problem with the new SlingCatcher firmware. I have horrible video/audio stuttering issues now that were not present before. Rebooting the 'catcher helps for a while. But the problem seems to be limited to the SlingCatcher because Sling desktop apps running on computers using exactly the same wired network connection all work flawlessly.

Are you using a PRO or PRO-HD.  I'm using a PRO and am not seeing this stuttering.  So I'm thinking it's a catcher issue with the PRO-HD hardware.

What happens if you lower the rsolution used by the catcher?

I also got the same problem with the new firmware updated on my slingcatcher. It also connects to a slingbox HD-PRO.

Here's a good one too. I got sent RMA for all 3 of my sling catchers in reguards to the Remote Control fast forward problem.
Now lets see. We use them every day almost 24/7. We really didn't notice the fast forward problem until it was posted here. So it's not really a serious problem for us. Maybe for others it is. They couldn't just send us some sort of script file that we could load into the catcher via a USB key or NAS and download the old Firmware. they are telling us we have to send them back for repair (re-furb)
So we are going to live with it. Yes I know this is bad. But like I posted other places. It does what we want it to.
But it's almost like Sling is doing a denial-of-service attack (DoS attack) on their own products with the these firmware upgrades.
In other words. Do the Firmware upgrade. It then breaks something. Then they tell you to ship the product back at your own cost. The service for that product is then lost for one or 2 weeks and chances are you get a re-furb product back.
All I can say is in my 55 years. I have never seen a company work this way.
Sling must be working fine and selling product since they are still in Business. But it's really amazing to us that they still are.

Those of you with the remote fast forward problem. Sling will tell you to send the catcher back to them if you call in.

Can anyone tell me if the Sling Catcher really does give a better picture on the TV rather than on a computer screen? If so, what number was the old software that worked properly (ie not freezing all the time? How do I update the software? Do I put it on a memory stick and plug the stick on or is it not possible to do this? I am considering getting one for my television.

Hope it works properly. If anyone can help I would be most grateful.

Thanks in advance.

James

I'm experiencing the same issue with the SlingCatch / Slingbox PRO-HD setup. Has anyone had any luck correcting either via rolling back the SlingCatcher firmware or some other way?

Ihave the latest firmware on both, and I could never keep the Slingbox Pro / SlingCatcher combination from locking up. I did notice that with the "OPT" key pressed, the speed would normally stay quite high, but then the bar would drop to almost nothing, and then it locks up.

I am going to change the slingbox pro to a S-Video setup (which is how I have the classic), and see if maybe it is the component output that is causing it to lock up.

I will find out next week. I upgraded firmware on the Slingbox HD Pro and also added an additional S-Video out to it. I am in the US and the slingcatcher is in London, so will be able to see if those changes fixed anything.

I appear to finally have this fixed. When I updated the firmware on the Slingbox PRO HD (which just became available about mid July), and was able to test it out this week back in London. I have been pretty much streaming continuously without a problem - even HD - getting about 2-2.3 MB/s. A couple of times the connection was broken, but that was over a several day period which you might expect on a transatlantic stream, but it did not lock up the PRO HD and require a power reset. On both occasions, I was able just to reinitialize the connection remotely without a problem.