Reply to thread

Message: <blockquote data-quote="satesco" data-source="post: 1130287" data-attributes="member: 297935">Deeptho.I realize that bugs occur with every release. That's why I don't insist on them, even more so with 6903x. Those who work with it know that it is a card that poses problems for driver developers, both on Windows and now on Linux.Firstly, I'm interested in whether your application can be at the same level of functionality as under Windows and whether it can outperform dvb applications under Windows.But I'll talk about that later after I do some more tests with neumodvb.And for that, I will consider the observations you have made now.As for what version of drivers we use, or version of neumodvb (now v.0.8.8), it would be good to specify on your site expressis verbis this. On Github are mentioned only kernel versions and patches are. And in the case of Neumodvb, as you rightly said, it is a work in progress, which implies that such a user has a better familiarity with your application. I try to use it more often as I leave other activities aside.You once said that you don't have stv091x-based cards, but I wish you could provide better support for 6983/6903 cards as neumodvb has for 6903x/6909x cards! I can imagine that it's not easy to work remotely on hardware support that is not on your pc, but if you think you would be willing to do it anyway, I suggest you work on my computer.I have tested some low and high symbol rates with 6903x and 6983 at some positions with your application. With 6983, I have locked the lowest symbol rate of 185, on 11697 V(Radio Mars) at 30.0W. The 6903x card does not even detect the signal. What do you say?Instead, with this one can lock the highest symbol rate is used on satellites, of 107140 Ks on 11013 H and 11137 H (Data services) at 15.0W.Can we hope that neumodvb will lock the low symbol rate as IQmonitor?</blockquote>

Verification