Replies: 13 comments 4 replies
|
Do you know any other software that has one? We are talking about live broadcasting and not internet radio. Seems it's hardware related on your side. Some hints
In some rare cases it could be broadcaster related. We have it sometimes here in Austria. Yes, it's very annoying. You can't do anything in such a case other than to complain at the operator or radio program. |
|
There is actually software buffer for input signal, currently it is set to 8*200ms = 1.6 sec. This is compile time parameter, you can change it before compilation if you want but I doubt it is going to help. I am using Nooelec RTL-SDR v5 almost everyday for continuous DAB reception for about 6-8 hours and I do not observe any issue on macOS. I did many tests on Windows in past and there was not problem either. I have few questions:
|
|
I've just recorded a situation where the software did a short interruption (less than 0.5 seconds). Here the output of the log file: 17:41:22.601 [I] default: IFFChunk::innerFromDevice: unkwnown chunk "\xFF\xD8\xFF\xE0" What can cause this muting of the Audio output? For further testing I've ordered NooElec NESDR SMArt XTR SDR, that comes with another tuner but I expect more the RTL2832U Demodulator to cause the problem. I use currently Qt for audio output instead of PortAudio. OpenSuse Tumbleweed uses PipeWire as audio Framework. |
|
Thanks for the log. |
|
Buffer is in my opinion not the problem, I tried to switch to X11, but the I had only one console without window decorations - useless. Is there a real option to wayland since X11 is outdated, or do you think to try Gnome instead of KDE Plasma. By the was I tried also Welle.io, but the sound there was buzzing at all time. |
|
Well, if it is due to Wayland, it could be problem in SuSE only. Other distros use Wayland too and does not seem to cause any problem. It could be also caused by AppImage if you do not compile yourself. AppImage is built in Ubuntu 22 that is pretty old and not compatible with SuSE in general. Building the app from source could resolve it too. You can also try other desktop environments, it could be also something lightweight, not necessarily Gnome. |
|
During the last two weeks, I tried several things, I tried 3 different dongles:
This weird looking combination of the programs dab2eti and dablin_gtx (dab2eti 188928000 90 | dablin_gtk) was working for hours without any interruptions. I always compiled Abracadabra from git-source, works fine so far, but I get tons of such cmake errors: |
|
I would say it it not a dongle problem. Specifically because the issue happens for RTL-SDR as well as for Airspy. The cmake warnings are strange, I do not see them on any platform I use for building the binaries. What Qt version do you have? I do not know how frequent the dropouts are but it would be interesting to start audio recording and listen to the output. After the dropout happens, stop the recording and check if it is in the recording too. My suspicion is that it could be caused by audio output device. Application does not implement SRC for audio output and it could explain the dropouts. The other test is to record IQ. When the dropout happens, stop the recording and then check if the dropout is present when you play the IQ recording as raw file input. I am sorry it is just try-and-error approach because I cannot reproduce any issue and you are the first reporting such problem. |
|
OpenSuSE Tumbleweed uses currently Qt 6.9.1-2.1. The sound system is using PipeWire. I've just forgot to put the outputs from Abracadabra (started from terminal) in my message: KDE PortAudio Output: 16:31:05.375 [I] AudioOutput: Hard mute [no samples available] KDE Qt Output: 10:30:27.043 [I] AudioDecoder: Muting audio (decoding errors) IceWM mit Qt output 09:08:32.843 [I] AudioOutput: Muting... [available 3968 samples] IceWM mit PortAudio output 20:08:37.037 [I] AudioOutput: Muting... [available 1920 samples] I'm just wondering from where or what application or library the statements "AudioOutput" and "AudioDecoder" are coming. You're writing that you don't have all these issues (cmake errors as well as interrupts) on your platform, so please let me know which platform(s) you are using. |
|
These are messages from the app. Audio decoder reports muting due to errors in audio stream and audio output reports muting when there is not enough samples available. What do you see in error stats in Ensemble info window? Is number of errors increasing or is it constant while drops happen? I build the app on macOS 15, Win11, Ubuntu 22.04 for x86_64, Debian (I do not remember the version) for AARCH64 and ArchLinux. I have not seen these warnings on any of these platforms. I will try to install SuSE in VBox when I have time for that to see if I can reproduce some of your issues. |
|
The main problem (sound interruption) is caused by PipeWire which SuSE is using, I switched back to PulseAudio and since at least two hours, everything seems to be fine. In this thread here is a not completely similar behavior of PipeWire discussed: |
|
The main problem (sound interruption) is caused by PipeWire which SuSE is using, I switched back to PulseAudio and since at least two hours, everything seems to be fine. In this thread here is a not completely similar behavior of PipeWire discussed: |
|
In the meantime I could organize a (real) computer with Kubuntu installed. The decoding errors from AudioDecoder occurs also here but not so often as on openSuSE. On the Essemble window each (Kubuntu and SuSE) decoding error gives three Audio CRC-Errors. When I start Abracadabra on SuSE, I get always 10 to 12 FIB-CRC-Errors at startup, but they don't increase even if I hear radio for hours. Startup at Kubuntu gives non of these errors. I use on both machines the precompiled appimage package. |
|
FIB CRC errors after tune are expected (you can alzays reset the stats by right click if you want to observe "steady state" values". Audio errors depend on input signal quality and protection level. I would expect that for EEP3-A and SNR > 10dB there should be no audio errors for static reception. |
|
The setup is as follows:
|
|
Depends what you want to compare. If the comparison is focused on application behavior under different OS, I would recommend to use exacly the same HW setup (same USB stick and the same antenna). The other interesting comparison could be to make IQ recording on one setup and replay it on other and vice versa. |
|
I've crossed the two RTL-SDR including the antenna. Now on SuSE with SMArt XTR SDR I have no FIB-CRC-Errors and 9 Audio CRC-Errors, on Kubuntu with RTL-SDR v5 12 FIB-CRC-Errors (they moved with the RTL-SDR Device) and 12 Audio-CRC-Errors |
Uh oh!
There was an error while loading. Please reload this page.
Thank you for the great software. There is just one thing I miss: It's a (software) buffer that can buffer up to to two seconds of signal. Even if I have strong signal there are for time to time small interruptions (< 0.5s) of playback. The hardware I'm using is a Nooelec RTL-SDR v5 SDR. Is there a possibility to implement a software buffer into AbracaDABra or an other way to fix the problem with the small interruptions?
All reactions