You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd really like your new implementation of the driver.
However, when connected to a Samsung TV set (UE19C4000), I most of the time fails to get any channel from all the test streams I've used: the TV set seems to find a signal on the specified frequency, but after several seconds, it bails out and claims it find no channel.
When using the ITE driver and test suite, the TV set has no trouble locating the channels (using the same freq/FEC/QAM/etc. as with your sendts.c file) and playing the ITE test streams.
I'm not sure what can go wrong here (missing information in the TS stream?), and I would like to know whether you would have a reference to a stream that you have been using to test your driver implementation, in order to compare the behaviour and understand why the TV set seems so picky about the TS content.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
I'd really like your new implementation of the driver.
However, when connected to a Samsung TV set (UE19C4000), I most of the time fails to get any channel from all the test streams I've used: the TV set seems to find a signal on the specified frequency, but after several seconds, it bails out and claims it find no channel.
When using the ITE driver and test suite, the TV set has no trouble locating the channels (using the same freq/FEC/QAM/etc. as with your sendts.c file) and playing the ITE test streams.
I'm not sure what can go wrong here (missing information in the TS stream?), and I would like to know whether you would have a reference to a stream that you have been using to test your driver implementation, in order to compare the behaviour and understand why the TV set seems so picky about the TS content.
Thanks.
The text was updated successfully, but these errors were encountered: