I don't get 1080p with HD300, only 1080p24???

[stanger89]

FWIW, I haven't seen any 1080p60 issues from my HD300 on my Samsung B6000.

[appelm]

Originally Posted by appelm

I'm seeing the flickering artifacts too at 1080p on my pana vt25. Going to try a different HDMI cable and see what happens.

Well, I tried a different cable and the problem did go away. But, I had the new cable plugged into a second HDMI port on my tv just to test it. Since my remotes are all programmed for the first port, I switched the new HDMI cable to the other port, and the flickering artifacts came back! I tried the old HDMI cable in the second port, and no more artifacts.. So it seems its a problem with one of the ports on my TV. For now, I'm fine since I have three ports and not using them all.

[dibs]

Originally Posted by appelm

Well, I tried a different cable and the problem did go away. But, I had the new cable plugged into a second HDMI port on my tv just to test it. Since my remotes are all programmed for the first port, I switched the new HDMI cable to the other port, and the flickering artifacts came back! I tried the old HDMI cable in the second port, and no more artifacts.. So it seems its a problem with one of the ports on my TV. For now, I'm fine since I have three ports and not using them all.

Mine went away for a little bit after I rebotted the HD300, but the flickering came back eventually. I'm interested in hearing if your artifacts come back as well. I have the same cable plugged into the same port as my old HD200 and never had this problem.

[Fuzzy]

flickering/sparkles is almost always a sign of a low signal strength on the HDMI cable. this is the result of either a bad connection, low powered drivers in the source, poor quality cables, or low sensitivity on the receiving end - or more likely, a combination of the above factors. If the HD200 doesn't have this problem, and the HD300 does, with all else the same, then it does imply that the drivers on the HD300 are weaker than those of the HD200. Does this mean the drivers on the HD300 are TOO weak? not necessarily. It may be that you have other weak components, and this last change was enough to push it sub-par. Since changing out the HD300 isn't necessarily an easy task, you might try either replacing the cable, or as others have tried (and reported working) a different port on the TV (may have a low sensitivity on one). there are also HDMI amps/extenders out there that in the worst case might be ebough to stabalize the signal at those high data rates (1080p60 is really not common in the CE world... so cables aren't commonly tested to those rates the only common sources of it would be a PC display)

[impro]

I do not think it is the cable.
If the hd200 worked with same link then it is the HD300
I had problems with flickering and a pink picture when I plugged the HD300 for the first time but I just disabled it.
I have no use for 1080P60

Originally Posted by Fuzzy

flickering/sparkles is almost always a sign of a low signal strength on the HDMI cable. this is the result of either a bad connection, low powered drivers in the source, poor quality cables, or low sensitivity on the receiving end - or more likely, a combination of the above factors. If the HD200 doesn't have this problem, and the HD300 does, with all else the same, then it does imply that the drivers on the HD300 are weaker than those of the HD200. Does this mean the drivers on the HD300 are TOO weak? not necessarily. It may be that you have other weak components, and this last change was enough to push it sub-par. Since changing out the HD300 isn't necessarily an easy task, you might try either replacing the cable, or as others have tried (and reported working) a different port on the TV (may have a low sensitivity on one). there are also HDMI amps/extenders out there that in the worst case might be ebough to stabalize the signal at those high data rates (1080p60 is really not common in the CE world... so cables aren't commonly tested to those rates the only common sources of it would be a PC display)

[Fuzzy]

My point was that it may very well NOT be JUST the HD300 that is the problem. You may be able to change cables or receiving end and the HD300 will probably work just fine at 1080p60. If you have a combination of marginal factors, and one gets slightly weaker, then you will have problems. However, if you can improve one of the other factors to make up for the change, then you may have satisfactory results.

[appelm]

Originally Posted by Fuzzy

My point was that it may very well NOT be JUST the HD300 that is the problem. You may be able to change cables or receiving end and the HD300 will probably work just fine at 1080p60. If you have a combination of marginal factors, and one gets slightly weaker, then you will have problems. However, if you can improve one of the other factors to make up for the change, then you may have satisfactory results.

That's exactly what I found as I mentioned above. So far flickering has not returned using the same old cable that was causing flickering before but is now plugged into a different port on my TV. My VT25 has 3 HDMI ports. I had been using HDMI3. Now I'm using HDMI1 and its fine.. Seems the third one is more sensative. Clearly the HD300 output is weaker than the HD200, at least for me, but as Fuzzy explained is possible, it is strong enough for at least one of my HDMI ports..

[peternm22]

Just wanted to add that I can't get 1080p60 to work on my TV either via the HD300. I tried the included HDMI cable and a cable I have from Blue Jeans Cables and neither works at 1080p60. Every other resolution works (including 1080p24). I'm using a Samsung LN40A650.

This is progress over my HD100, which I could never get to go above 480p over HDMI (I just used component video).

I can't get 1080p60 over component from the HD300 either (TV says mode not supported), even though that was the mode I was using with the HD100.

[Hunter69]

I wanted to chime in on this subject. I am hooked up via component and the picture is unstable @1080p 60hz. I never had this problem with the HD200. This is a bug in the hd300 not cable. I have trouble shot this extensively. 1080p/24 is stable. I like the resolution to output native resolution to the source and I cannot, due to this bug. I have to set it to a static resolution of 1080i/60hz.

I had posted this thread and did not realize it was the same issue as described in this thread.

http://forums.sagetv.com/forums/showthread.php?t=51077

I do describe how I got it to stabilize but later when messing with the resolutions I found that 1080P/60 was still not stable.

[NEOSG]

1080p/60 is not stable for me either with latest beta frimware. Causes crash of HD300 regularly. 1080p/24 will work, but looks goofy with 24fps. So, run 1080i

[jchisholm]

Had lots of video weirdness with my new HD300 and my Samsung LN52B550
I set the HD300 to 1080i and haven't had a problem since.

[jchisholm]

Also..
I *can* verify that the digital audio cable that comes with the HD300 is of poor quality (at least in my case).
The optical output is visibly very attenuated at the end of the cable (not enough to drive my Kenwood amp) whereas a generic 15' Newegg cable is fine with lots of intensity.
Not complaining specifically as very few other products would even bundle an audio and a HDMI cable but just a heads-up that they (at least mine) aren't of high quality.

[rockinray]

I am having the same problems with a Pioneer PRO-111 FD.

See "electronic" flickering on the screen. It gets fairly bad to the point where unwatchable.

If I set to 1080i, then the fonts looks horrible on the menu / guide... 1080p looks perfect.

Ray

[peternm22]

Just updated to the latest firmware for the HD300 (and also Sage 7.0.20). When I select 1080p now, I can actually get an image on the screen and it looks fine. However, every few seconds the screen blacks out and comes back on, so it's still unusable.

[NEOSG]

Originally Posted by peternm22

Just updated to the latest firmware for the HD300 (and also Sage 7.0.20). When I select 1080p now, I can actually get an image on the screen and it looks fine. However, every few seconds the screen blacks out and comes back on, so it's still unusable.

This is exactly what happens to me

[peternm22]

Originally Posted by NEOSG

This is exactly what happens to me

What TV are you running? I'm running a Samsung LN40A650.

[ojosch]

I remember when I got my Samsung LED TV I first plugged in my Dish Network receiver to it, and I was getting this weird flickering with a lot of purple color, and I noticed I had my 15ft HDMI cable on it that had the big round cylinder-shape noise filters on each end of it. So I got another 15ft cable from PCables.com that did NOT have the filter on each end and that fixed my problem. Flickering went away, and the purple color was gone after that. Both cables had identical pin-count and all, so I can only assume it had something to do with those filters. That cable with the filters on it works fine on that same TV if I plug it to my Lenovo Thinkpad's docking station's DVI port (using a DVI-to-HDMI adapter plug), but it just cannot be plugged into the Dish Network receiver for some reason

I just thought I'd throw in this little tidbit in case it proves to have some diagnostic value for you.

[NEOSG]

Originally Posted by peternm22

What TV are you running? I'm running a Samsung LN40A650.

Out of town so can't check. Basic specs 32" LG lCD 1080p

[pizzachef]

Have two HD-300's on two different TV's, each of which replaced an HD-200 so I have been able to do some debugging. In none of these installations do I use the sagetv supplied cable.

Both work in 1080p/60 on my Samsung LCD with a 6 foot cable

On my projector, with a longer (but very good) cable run, the old HD-200 worked fine in 1080p/60. However, neither of the new HD-300's work in 1080p/60 with the projector, even with the most recent beta firmware. All other modes, including 1080p/24 and 1080i/60 work fine.

This leads me to agree with the previous poster -- the signal strength was probably just above marginal in the HD-200 and something has been done in the HD-300 to drop the signal output strength below the threshold. That is why it works on a shorter cable run.

[rtrski]

I'm still using an old DLP 720p set (Toshiba 52HM84). I couldn't get the HD200 to ever work with it using it's single HDMI connection - tried 3 different cables. Nothing. Had to go Component, which worked fine as I had well shielded component cables.

But now I bought an HD300 and didn't realize (yes, specs were all visible if I looked) that component is now only available through a multipin breakout, which means I have to use their cables. And for some reason the TV won't show an input if I set the HD300 component to 720p, which is native for the TV. It does work with 1080i, which is odd.

Did try the HDMI cable that came with the HD300, and a couple older ones laying around. Again, no dice. Not surprised...for all I know my HDMI connection on my TV *never* worked since I got it in 2003.

The only disappointment is that the pigtailed cables don't seem to be as good a quality - the HD300 pic is noticably darker and a tiny bit ghosted thanI was getting with the HD200. I'd trade back...except since I've upgraded to V7 I expect the 300 will work better in terms of animation and thumbnail speed.

Just waiting for the bulb in this thing to blow out so I can upgrade. What was supposed to last 2-3 years has lasted 6 because our living room is dark enough I leave the TV brightness at the low-power bulb setting. <wry grin>