-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
More Technical Data in the Expert Mode #210
Comments
Good evening Lars, very easy: You find that in qt-dab, just press the button |
Hi @andimik , Great to hear it! I'll try! 馃槃 However, I still prefer that Welle.io will "print" also this data. Why? Because this tool it's portable, so I can just use it with an Android device, a Windows PC or Tablet, a Mac notebook, etc. So, if I can get all the info from this great tool, then I don't need other when scanning in different regions. In any case, @AlbrechtL has all of this info in the code: welle.io/src/libs/faad2/libfaad/structs.h Line 146 in 948fd64
So it's only a few "prints" in the UI to show them in the current Expert View. Or I'm missing something? |
Why you need this information? |
Why not? In any case: Your DAB player is one of the most robust and portable. So I recommend to use it in any environment. So, I like to see all the technical data in the export zone (so for this reason is this zone, true?) |
Please visit http://www.fmlist.org/sendertabelle/dab-ww.php Here you will find all necessary information. If something is wrong or missing, please inform fmlist.org editors and share your observations. |
Hi @andimik ,
And all this info it's right (I feel). Thank you! However, I don't like to "get" the data; I like to "see" the decoded data. For example, if I try to decode some user DAB bitstream (at time, modulated to IQ samples; as the ETI-NI input is not supported). Please, think on this: The data exists in the App, and the info it's relevant. Futhermore, an Expert zone exists. So, what it's the reason for not showing this info? Is that sensitive information? I hope @AlbrechtL agree with printing this info. 馃槃 |
A nice way to show CUs is to draw 864 little squares in a grid and colour them according to which subchannel occupies them. The currently playing programme could be highlighted, and you could even use this to select the programme. |
Hi @mpbraendli , Great idea! 馃憤 However, before show complex data (like the occupued CUs), will be sufficient to print the numerical or string data, like the Protection Level, Subchannel ID, Start Address of CU, number of Used CUs, etc. @AlbrechtL , you agree? |
For such a reason please use Andi Gsinn's player, he shows every CU in one little square |
@andimik I cannot use Andi Gsinn's player, because I don't have a Windows machine. |
Lars uses Windows 7 ;-) |
Hi @andimik ,
Thank you! Great piece of software! It has a lot of Expert info in the DAB-Info section. Very useful! However, this software it's hard to setup. Why? Because the RTL_TCP input it's poorly documented. For example, even you use a remote server (or another local executable server) you need to first to setup the "custom" driver (aka "Treiber2" version); and only after that you can start it with "DAB_Player.exe -RTLTCP". Only in this way you can use it with an external RTL_TCP server (this it's because it uses a lot of DLL installed by this special driver in Windows\System32). In any case, a very good software for experts. But it lacks multiplatform support. That it's one of the must have of Welle.io. So, if @AlbrechtL agree with it, I suggest to improve the Expert Zone with useful info easy to write (mainly current info that only needs to be printed). Regards. 馃槃 |
I added it to the Open Tasks. |
Hi @AlbrechtL ,
First of all: Thank you for the last release 1.0-rc3. 馃槃
One suggestion to improve the IU: Can you please add some more technical data in the Expert Mode view?
I feel all of this information is known in the code. So, it's only a requirement to print this info in the Expert Mode view. Perhaps in a "two colums mode" where you at time print SNR, Frame/RS/AAC errors, etc.
You agree?
(I see this info in the "Technical Data" of the qt-dab tool... but your player is more robust and user friendly.)
Regards!
The text was updated successfully, but these errors were encountered: