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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.1 scanning crash #69
Comments
You do not have to delete INI to do the rescan - just go to menu - Clear service list. Nevertheless it should not crash, I will try to reproduce this problem on Windows, thanks for reporting. |
I know :-) Just trying to break it :-) 73 Herman Wijnants |
2.1 also crashing when doing a band scan, so not deleting the ini file! Solution: delete the libdabsdr.dll and replace it with the previous one! 73 Herman Wijnants |
Yes, confirmed. Just had a crash in manual scan. But tried to reproduce it with In my case I have a very weak signal in 8A of the same mux which I have locally on 6A. So, it's the same content. |
After more than 10 trials, this is a video (crash in minute 1:05) and Bildschirmaufzeichnung.vom.15.03.2023.00.04.38.webm
(updated: the video needs a blank line before it in github ...) |
This is auto scan, this time the Bildschirmaufzeichnung.vom.15.03.2023.07.20.16.webm
|
Update: the crash is at 7D and even 1.99.4+ (04ac900) had that problem, so this is not related to 2.1 only. This channel is used by two different muxes (Slovenia and Italy), but both are too weak, although I get a "Signal found" in previous version Bildschirmaufzeichnung.vom.15.03.2023.07.30.18.webm |
Thanks for all the reports. I think I have found the root cause that explains crashes for 2.1. However, I have no idea about the crashes for version < 2.1, I would need more information, ideally raw file that can be used to reproduce the crash. |
OK, it makes sense now :-) Then we are aligned, the bug is in DABSDR 2.1. I will release DABSDR binaries soon today and then I would like to ask you to test it with your setup to be sure that I have not overseen anything before release new version of AbracaDABra. |
Confirmed, no crash now with 2.1.1 :-) BTW: What does
mean? |
It means a problem. It happens when DABSDR is not able to process the data fast enough. Does it start to happen after update to 2.1.1? If this is the case then there is still some problem :-( |
I also get it under DABSDR 2.0.0
|
Well, synchronization is quite CPU demanding processing, now it needs even more MIPS due to selectivity filter. I am running the app on Ubuntu on >10 years old laptop now and do not see any samples dropping. I am trying all channels and it does not happen. |
On a very very weak signal Bildschirmaufzeichnung.vom.15.03.2023.14.44.55.webm |
Yes, CPU usage is the problem. I assume that you are running Release build. But I do not see such huge difference between channel with signal and without. Does it happen with prebuilt AppImage too? |
Qt-DAB: 60% in top on a very weak channel Then I've made a recording of the same channel and played it (continuously) in Abra. It's far below 100%. Bildschirmaufzeichnung.vom.15.03.2023.15.08.18.webm |
CPU issue does not seem to be related to this issue thus I have created new issue #71 to continue the debugging there. |
Version 2.1.1 with fix of this issue has been released, closing. |
Hi,
I unzipped 2.1 in the AbracaDABra folder and it worked perfectly well. Then I deleted the ini file to have AbracaDABra rebuild it and start by scanning for muxes. This didn't work and the scanning crashed AbracaDABra after having scanned a few muxes.
Solution: restore my back-upped original ini or start a scan and stop after a few muxes. Then continue building the ini by manually tuning to all muxes one by one.
73
Herman Wijnants
My logblog
BELGIUM editor fmlist.org
The text was updated successfully, but these errors were encountered: