Ratzvan
Feed Hunter
- Messages
- 22,693
Hi
I realized many mistakes have have been done recently, above all posting biss 4:2:2 feeds that create unfair situation in biss area
In fact with last firmware upgrade several boxes tend to give at first approach an old wrong cw
Basically, server tends to give for biss feeds/channels a cw already stored in its database if feeds has the same parameters of an older biss one (freq../polarity/sr/pmt,vpid...), , without any real check
(Something similar happened still before, but more rarely and above all when server had no luck finding the cw)
I've too, after with my last tiger firmware update, got feed with biss ok cw message, near immediatly: but often that cw was a wrong one.
On standard 4:2:0 feeds it could be minor issue, because if you don't see any image on the screen, you can doubt cw is good, but with known 4:2:2 feeds it could be a greater one, because often feeds are posted with a old wrong cw that need to be corrected later.
When I came back to the older May firmware, problems ended and server started again to work fine.
I did a further check
No advantage seems to come with this new biss server approach to feeds in timeframe of opening the channel. But only problems.
I suggest every feed hunter to check if he has the same problem and eventuallly come back to an older firmware version and see if problem persists or not.
I can assure you, there is no worsening in biss au server working (except you could lose last forever server version)
R
I realized many mistakes have have been done recently, above all posting biss 4:2:2 feeds that create unfair situation in biss area
In fact with last firmware upgrade several boxes tend to give at first approach an old wrong cw
Basically, server tends to give for biss feeds/channels a cw already stored in its database if feeds has the same parameters of an older biss one (freq../polarity/sr/pmt,vpid...), , without any real check
(Something similar happened still before, but more rarely and above all when server had no luck finding the cw)
I've too, after with my last tiger firmware update, got feed with biss ok cw message, near immediatly: but often that cw was a wrong one.
On standard 4:2:0 feeds it could be minor issue, because if you don't see any image on the screen, you can doubt cw is good, but with known 4:2:2 feeds it could be a greater one, because often feeds are posted with a old wrong cw that need to be corrected later.
When I came back to the older May firmware, problems ended and server started again to work fine.
I did a further check
No advantage seems to come with this new biss server approach to feeds in timeframe of opening the channel. But only problems.
I suggest every feed hunter to check if he has the same problem and eventuallly come back to an older firmware version and see if problem persists or not.
I can assure you, there is no worsening in biss au server working (except you could lose last forever server version
)R
