Native Resolution Output Not Working

[cat6man]

wonder if EDID negotiation with the TV is missing 480i on the hd200?

+1 for fixing this on the hd200...........i'm new here.......do you vote on bug reports, or do the developers read the forum?

[razrsharpe]

Originally Posted by cat6man

do you vote on bug reports, or do the developers read the forum?

The only way to guarantee that it gets reported is to submit a bug report and get it in their internal bug tracking system. The developers do read the forums but it's not guaranteed.

[cat6man]

thanks.........my question was a little different.

if someone else submits a bug report, is it of value to sumbit a 2nd one or somehow indicate that this is important to you/others as well?

[razrsharpe]

ahhh... sorry... Yes I would say there is value in multiple people submitting the same bug. That way Sage knows that's important to more people and worth their time to fix.

[cat6man]

i just tested this here and native resolution works for 720p and 1080i but i get no picture at all on 480i so i had to delete that from the list of supported resolutions

tested using a sony hdtv via hdmi (no video processor)

can the person who said that 480i used to work with the hd100 confirm that this was over hdmi and not component? i know there have been issues associated with the sigma chip having timing problems with 480i over hdmi and i was actually surprised to hear that it worked at all this way

if it turns out that 480i cannot be supported over hdmi, i would propose that just for native resolution mode, the 480i (if enabled) be defaulted (or have an option to do so) to 480p so at least no scaling will be done..........my dvdo video processor has a mode called 'prep' which takes 480p in and converts it internally to 480i (to undo the interlacing), then scales and de-interlaced to the desired output resolution/frame rate for my system.

[cat6man]

damn, these guys are good!

480i bug report submitted
response: problem solved, fix to be in next release.

wooohooooo

[QueOnda]

Cool. Did they say beta or Public release?

[stanger89]

Betas are just precursors to public releases, or interim releases. I'd bet there will be a beta with it before the next release goes gold.

That's how Sage works. Put the next version out there with the "beta" tag and let the community play with it. It's better than most companies (Cyberlink, Arcsoft, etc, etc) who do the same thing but don't call them beta.

[cat6man]

Originally Posted by QueOnda

Cool. Did they say beta or Public release?

"next" is all...........

[cat6man]

Originally Posted by stanger89

Betas are just precursors to public releases, or interim releases. I'd bet there will be a beta with it before the next release goes gold.

That's how Sage works. Put the next version out there with the "beta" tag and let the community play with it. It's better than most companies (Cyberlink, Arcsoft, etc, etc) who do the same thing but don't call them beta.

beta testing media players is very very very important.

the sage folks seem very competent and fix a lot of things quickly.

where things typically break with network media players is when sigma releases a new SDK with new features and breaks half a dozen that used to work fine..........everyone is at the mercy of the lousy quality control for those SDK updates........not a thing sage or anyone else can do about it and this has been going on for many years (i was a beta tester for ziova/zensonic)

did i sufficiently mention that beta testing (particularly regression testing of stuff that used to be rock solid) is important when the SDK changes?