Gonzalo José Carracedo Carballal
Gonzalo José Carracedo Carballal
I don't think that message is related to this problem. Instead, it's like the device is reporting a 0-sized MTU, which is plainly wrong. What SoapySDR version are you using...
Confirmed on a friend's laptop
Wow, nice catch! This is actually a deployment issue that comes from SigDigger relying on the system's libpng instead of the built-in one. I'll fix this ASAP.
Alright, the laptop with Ubuntu 16.04 that I used for deployment just died. I think this is going to take a while :(
Hi! I've just made some tentative changes in the deployment script and came up with a new AppImage file. It turns out that I shouldn't be including libz in the...
Ouch. In any case, do you guys mind sharing the errors you get in the terminal with me? (both build failures or any library / versioning errors). They may help...
I will take all this into account. I'm expecting a new laptop next week, as soon as I have it I will install different VMs to do some intensive testing...
I've been trying to reproduce this behavior -both from sources and AppImage- but no luck so far. Could you attach the XML files saved in ```~/.suscan/config``` to this issue? Thanks!
Caused by weird behavior of the old SoapySDR's sample rate query API. Leaving for SigDigger 0.2
Hi Rob, Can you provide details on how you built SigDigger and all its dependencies? What branch have you cloned from? The master branch is rather old now and will...