Closed TechMindsYT closed 4 years ago
I'll look into it, I must admit that I am seldom using a stick
Op vr 17 apr. 2020 om 19:13 schreef Matthew Miller <notifications@github.com
:
Hi, when I select DABstick I am able to see the software detects the RTL-SDR V3 dongle but as soon as I press scan or change one of the bands the application hangs and dissapears from the screen. I have tested Airspy, HackRF and SDRPlay which all work okay. I have tested a NooElec Smartee and RTLSDR V3 using Dabstick selection and they both make the app crash.
I am using Windows 10 and latest 3.4 build, same happened with previous version.
NooElec and RTL dongle both work fine in SDR# so drivers seem to be working okay.
Any thoughts? Is there a way to see the crash dump?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQEDJV2L2OXJHMJE6OTRNCE4XANCNFSM4MK467NQ .
-- Jan van Katwijk
Well, I fear some of the latest commits lets it crash. Same here with rawfiles and live reception.
My old dabsticks give normal results for what I can see
Op vr 17 apr. 2020 om 19:13 schreef Matthew Miller <notifications@github.com
:
Hi, when I select DABstick I am able to see the software detects the RTL-SDR V3 dongle but as soon as I press scan or change one of the bands the application hangs and dissapears from the screen. I have tested Airspy, HackRF and SDRPlay which all work okay. I have tested a NooElec Smartee and RTLSDR V3 using Dabstick selection and they both make the app crash.
I am using Windows 10 and latest 3.4 build, same happened with previous version.
NooElec and RTL dongle both work fine in SDR# so drivers seem to be working okay.
Any thoughts? Is there a way to see the crash dump?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQEDJV2L2OXJHMJE6OTRNCE4XANCNFSM4MK467NQ .
-- Jan van Katwijk
Very strange, which Dabsticks are you testing with? Is there a way to see a crash log?
Also, which driver do you have installed for your Dabstick?
I have two old sticks, a Noxon and a generic 820T based one. I use the Osmocom driver which I compile myself
I run some more tests with the sticks tomorrow (the sticks need too much of antenna to run from my chair) There is most likely something wrong, it would be helpful if I can generate the crash.
Op vr 17 apr. 2020 om 20:12 schreef Matthew Miller <notifications@github.com
:
Also, which driver do you have installed for your Dabstick?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-615390603, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQCSAEBU4CTDGSCQRH3RNCL2FANCNFSM4MK467NQ .
-- Jan van Katwijk
Can you send me a rawfile so that I can see what is happening
Op vr 17 apr. 2020 om 19:24 schreef andimik notifications@github.com:
Well, I fear some of the latest commits lets it crash. Same here with rawfiles and live reception.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-615369083, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQHWN2J44TAFCMXS57TRNCGGTANCNFSM4MK467NQ .
-- Jan van Katwijk
Well, There is one condition where I can get Qt-DAB to crash under Windows using a DABstick (but maybe with other devices as well): If I start scanning when a service list is being created. That is reproducible so I will fix it this weekend
Further no encountered problems with my 2 dabsticks
Op vr 17 apr. 2020 om 21:21 schreef jan van katwijk <j.vankatwijk@gmail.com
:
Can you send me a rawfile so that I can see what is happening
Op vr 17 apr. 2020 om 19:24 schreef andimik notifications@github.com:
Well, I fear some of the latest commits lets it crash. Same here with rawfiles and live reception.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-615369083, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQHWN2J44TAFCMXS57TRNCGGTANCNFSM4MK467NQ .
-- Jan van Katwijk
-- Jan van Katwijk
Yes with me 'dabstick' will crash as soon as I press scan. my SDR play rsp1a will scan ok but stations are not saved or show up anyway even though they do for a second or so during the scan. bizarre ! version 2 works 100% fine btw
Windows or Linux
On Sun, Apr 19, 2020, 9:50 PM m1ctk notifications@github.com wrote:
Yes with me 'dabstick' will crash as soon as I press scan. my SDR play rsp1a will scan ok but stations are not saved or show up anyway even though they do for a second or so during the scan. bizarre ! version 2 works btw
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-616214689, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQFRWH4OZ5JT2GQ6GHTRNNIZPANCNFSM4MK467NQ .
Windows 10 64bit
Ok, I have homework!
On Sun, Apr 19, 2020, 10:03 PM m1ctk notifications@github.com wrote:
Windows 10 64bit
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-616216374, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQDHUVFGOIITE6KTB73RNNKIVANCNFSM4MK467NQ .
Thanks for all your excellent work
I rewrote (part of) the code used in switching channels, there might have been a timing issue there. As said earlier, I do not have the problem so I cannot guarantee that it is solved. I uploaded a new windows installer. Let me know the result
Op zo 19 apr. 2020 om 22:27 schreef m1ctk notifications@github.com:
Thanks for all your excellent work
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-616219798, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQA4MSX52MWUYYXZD43RNNNDDANCNFSM4MK467NQ .
-- Jan van Katwijk
Great but where do I downlead it or did you just replace the installer here ? https://github.com/JvanKatwijk/qt-dab/releases/tag/3.4
I just replaced the installer
Op di 21 apr. 2020 om 22:17 schreef m1ctk notifications@github.com:
Great but where do I downlead it or did you just replace the installer here ? https://github.com/JvanKatwijk/qt-dab/releases/tag/3.4
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-617391458, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQGYRZJ7KGECNKWZWS3RNX5NRANCNFSM4MK467NQ .
-- Jan van Katwijk
OK it won't crash now with my rsp1a which is fantastic but after a scan there is no station list showing. I can only get 1 mux worth showing, I can receive 6 here so if I want another mux to show I have to again scan for that mux...no way to show the full list ?
If you use the presets for your favourite stations (which might be in different muxes) there is no need to scan again. It will tune to the right channel and play the right service.
ok but I thought the scan result of all muxes would display in the box and you just highlight / click on the one you want to play, that would be for more useful for me anyway with over 100 stations I would like to run through
Ah the XX button brings up a clickable full list ok thanks, great
The xx list is the history, I just saves all services ever selected (uintil the list is cleared of course). The presetlist is under your control, select a service, touch the name of the selected service with the right mouse button and it will appear in the presetlist.
The scan result will list the received ensembles and their components, however, it will not save them.
Op wo 22 apr. 2020 om 03:35 schreef m1ctk notifications@github.com:
Ah the XX button brings up a clickable full list ok thanks, great
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-617487155, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQGQYDYTKUFNLEMPLHDRNZCXXANCNFSM4MK467NQ .
-- Jan van Katwijk
OK can you make it so they can be saved though ? plus one day ad support for airspy HF+ ?
This is technically not possible. The bandwidth is limited. Please use another hardware.
Yes ok it's working very well, my rsp1a seems to be very sensitive on DAB, Rouen received this morning here in Brighton UK https://www.youtube.com/watch?v=BtL9BtdpdWA&t=6s
The latest version now asks whether or not you want to save the result of a scan in a file (textfile, readable by e.g. LibreOfficeCalc)
Op za 25 apr. 2020 om 01:54 schreef m1ctk notifications@github.com:
Yes ok it's working very well, my rsp1a seems to be very sensitive on DAB, Rouen received this morning here in Brighton UK https://www.youtube.com/watch?v=BtL9BtdpdWA&t=6s
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-619284454, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQEMONXPKBZJIIZE2M3ROIRDJANCNFSM4MK467NQ .
-- Jan van Katwijk
I just tried my RTL V3 and after a few secs after I hit scan your prog exists. All really good with my rsp1a though. it is excellent at sniffing out any hint of dx I find with 10A from Rouen. DAB player and Welle.io find nothing however
Apparently rtl V3 sticks behave differently from the "old" ones, I do not have a decent spec, so for noe I am helpless here
Op zo 26 apr. 2020 om 20:45 schreef m1ctk notifications@github.com:
I just tried my RTL V3 and after a few secs after I hit scan your prog exists. All really good with my rsp1a though. it is excellent an sniffing out any hint of dx I find with 10A from Rouen. DAB player and Welle.io find nothing however
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-619603918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQFNQKX7UL43CHWY3RDROR6L5ANCNFSM4MK467NQ .
-- Jan van Katwijk
Trying another R820T and got a full scan THEN it exited ! Oh well
Do I understand it correctly that the software crashes with rtl V3 in the scanner function? How about other use of the rtl V3 (i.e. is it specific to the scanner)
Op zo 26 apr. 2020 om 21:02 schreef jan van katwijk <j.vankatwijk@gmail.com
:
Apparently rtl V3 sticks behave differently from the "old" ones, I do not have a decent spec, so for noe I am helpless here
Op zo 26 apr. 2020 om 20:45 schreef m1ctk notifications@github.com:
I just tried my RTL V3 and after a few secs after I hit scan your prog exists. All really good with my rsp1a though. it is excellent an sniffing out any hint of dx I find with 10A from Rouen. DAB player and Welle.io find nothing however
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-619603918, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQFNQKX7UL43CHWY3RDROR6L5ANCNFSM4MK467NQ .
-- Jan van Katwijk
-- Jan van Katwijk
Coreect yes crashes after or at the start of a scan
I have a version of qt-dab now that generates some output on the console. Using an RT820 based stick I get an occasional crash (app one out of 10 to 15 scans), they seem to appear on the same place in the code. I also noticed that with other devices (my old Noxon stick, the SDRplay RSP 1a and Airspy) I do not get the same phenomenon, I did not manage to get them crashed, not normally and not while scanning.
My question is if you want to test with the attached version - preferably running from a command window such that the output remains visible - and send me the generated output in case of a crash with a stick
The attachment is a zipped folder, unzip the folder, everything you need to run is in that folder, and run the qt-dab-3.4.1 executable
If the output you get is - more or less - consistent with the output I get, then I dive into windows, compile and run from within windows with a debugger (I only cross compile from Linux, no cross debugging tools)
Anyway, that will be a great help in solving this issue
https://www.dropbox.com/s/pe1ndi0kfvsa9eq/windows-qt-dab.zip?dl=0 Thanks in advance best jan
Op zo 26 apr. 2020 om 21:18 schreef m1ctk notifications@github.com:
Coreect yes crashes after or at the start of a scan
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/qt-dab/issues/164#issuecomment-619609544, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQGCDV5LYEJYIEZK5YDROSCHNANCNFSM4MK467NQ .
-- Jan van Katwijk
As there is no progress, I suggest to close this issue.
Hi, when I select DABstick I am able to see the software detects the RTL-SDR V3 dongle but as soon as I press scan or change one of the bands the application hangs and dissapears from the screen. I have tested Airspy, HackRF and SDRPlay which all work okay. I have tested a NooElec Smartee and RTLSDR V3 using Dabstick selection and they both make the app crash.
I am using Windows 10 and latest 3.4 build, same happened with previous version.
NooElec and RTL dongle both work fine in SDR# so drivers seem to be working okay.
Any thoughts? Is there a way to see the crash dump?