Most shortwave is Chinese these days... What I've noticed is that the audio itself isn't necessarily the problem with TDF. It's phase noise within the transmission. Can't seem to get a good enough SNR to get the MSC layer to decode properly despite exceptionally strong signals. It's possible that it's intentional (as you say), but I'm not sure why they would do that for only some of the broadcasts. Either way, I'm pretty sure that since the extra MM overhead is 66% of the MSC layer, it's not helping...
Most shortwave is Chinese these days... What I've noticed is that the audio itself isn't necessarily the problem with TDF. It's phase noise within the transmission. Can't seem to get a good enough SNR to get the MSC layer to decode properly despite exceptionally strong signals. It's possible that it's intentional (as you say), but I'm not sure why they would do that for only some of the broadcasts. Either way, I'm pretty sure that since the extra MM overhead is 66% of the MSC layer, it's not helping...
I think TDF is doing something non-standard, not Journaline. I suspect there is more data in there with their crappy audio that requires proprietary software to decode and this is something they are trying to sell to clients. Just my guess though. Not much Journaline to decode in this part of the world either. Most DRM signals here are Chinese these days!
Hmm. Have noticed that the MM wasn't working properly in the TDF broadcasts, but never really looked at why or what was the status messages. Next time I get a good TDF signal (which is rare anymore in the US) I'll look a little deeper to see what's going on. It could very well be that either there's something new that's not being handled correctly, or there are broadcasters that are implementing something non-standard.
Hi Has any version of Dream here got a fix for the Journaline error that my versions throw on most recent Journaline broadcasts (eg the recent Hungary broadcast on 11m): "Error: expected NML Code 0x01, got 0x1a" To me this screams "broadcaster sending version code 0x1a but Dream doesn't have a clue as to how to deal with anything other 0x01". I've seen this on other recent broadcasters too. Any fix coming? Cheers, Chris
Removed QT references to webenginewidgets in .pro file
DREAM DRM Receiver can successfully decode a PCAP file containing only DCP-TPL packets. These packet capture PCAPs are given in the Dream sample files . But I have tried inputting a packet capture file which has DCP-PFT packets and DCP-TPL packets. I have tried inputting this file to dream DRM but its not decoding it. Someone please confirm if Dream decodes PFT packets because if not then the packets are probably corrupted.
https://github.com/wwek/dream/issues
Dream works normally in OpenWebrx
我是在树莓派PI5B上来编译运行dream的,内核版本是: linux Raspberrypi5 6.12.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26)aarch64
大佬,可以否帮分享下dream-2.1.1-svn808.tar.gz这个版本的xHE-AAC补丁源代码哈, 目前发现还是用2.1.1的稳定些,谢过大佬了! 我邮箱 45908351@qq.com 微信:Gerd-737 (用2.2的编译后很多错误,AAC 都解码不了,确实是有问题,看来只能用2.1.1版的liunx版本)
FAAD从来没有说过支持xHE-AAC解码, 你自己臆想出来的吧!你得使用FDK-AAC
What is the latest version date?
像这个错误一样的提示 https://sourceforge.net/p/drm/discussion/general/thread/90dc5df0a5/
按KIWI 改的14行代码后重新编译后,播放本地XHE-AAC 文件提示以下日志:
你好,win版本确实是可以正常工作了,但是我按kiwi提供的方法编译了树莓派PI5B用的Dream2.2时,执行程序 就提示错误,并且播放本地XHE-AAC 文件也不行,这是啥情况呀,而且在openwebrx里调用dream2.2也不能正常工作,是否有方法解决,感谢帮助! 45908351@qq.com 微信:Gerd-737
你好: 有关xHE-AAC 问题你到以下链接自行查看,尤其是第九楼的帖子,基本的步骤都有详述。原因是源代码有误(bug),现在只需一个C文件替换,重新编译即可。整个过程不超过2分钟。 https://www.drmrx.org/forum/forum/drm-reception-project/general-topics/1580-how-often-does-dream-start-to-crash-when-decoding-xhe-aac https://www.drmrx.org/forum/forum/drm-reception-project/general-topics/1580-how-often-does-dream-start-to-crash-when-decoding-xhe-aac 发件人:Allen xxj737@users.sourceforge.net 发送时间:2025年10月8日(周三) 23:47 收件人:"[drm:discussion]"general@discussion.drm.p.re.sourceforge.net 主 题:[drm:discussion]...
https://www.drmrx.org/forum/forum/drm-reception-project/general-topics/1580-how-often-does-dream-start-to-crash-when-decoding-xhe-aac https://www.drmrx.org/forum/forum/drm-reception-project/general-topics/1580-how-often-does-dream-start-to-crash-when-decoding-xhe-aac 发件人:Allen xxj737@users.sourceforge.net 发送时间:2025年10月8日(周三) 23:47 收件人:"[drm:discussion]"general@discussion.drm.p.re.sourceforge.net 主 题:[drm:discussion] Re: Installing Dream 2.2 on Windows (I want my DRM!) Hello Please help provide the...
Hello Please help provide the code, thank you very much 45908351@qq.com vx:gerd-737
root@Raspberrypi5:~# dream Got FAAD2 library Got FAAC library pa_c_sync failed, error -1 pa_init pa_context_connect failed CSoundPulse::Enumerate(): pa_init failed stoprec pa_c_sync failed, error -1 pa_init pa_context_connect failed CSoundPulse::Enumerate(): pa_init failed pa_c_sync failed, error -1 pa_init pa_context_connect failed CSoundPulse::Enumerate(): pa_init failed ~CSoundOutPulse stopplay ~CSoundPulse initplay 48000 38400 0 CSoundOutPulse::Init_HW() pa_c_sync failed, error -1 pa_init pa_context_connect...
Hello I come from China. I also encountered the same problem Looking for a solution
Removed prints.
New rama format working
Updating rama tag to latest RSCI version including MIME-type defined codec
Adding standard AAC for RAMA tag
Receiver now responds to RCI cdmo (change demod mode) commands.
Hi guys, I use Openwebrx plus(https://hub.docker.com/r/slechev/openwebrxplus) to run SDR service, and the built-in DRM only support AAC decoding, but not support xHE-AAC decoding. So I try to re-compile the dream from souce code to make it support xHE-AAC, and the make is ok, but if run the dream, it's still get error output. details information as below. 1. Basic informaion: Hardware: SDRPlay RSP1, a SDR(softwave define radio) dongle. System: Ubuntu 20.04 Docker image: https://hub.docker.com/r/slechev/openwebrxplus...
I should mention that ZFYoung's 2.2.x version of Dream has an issue where you can't change the input. You have to change the input in the dream.ini file. You can also do this by changing settings in a Dream 2.1 and taking a copy of the resulting dream.ini file in the program directory for version 2.1 and moving it over to your Dream 2.2.x program directory, replacing the dream.ini file for Dream 2.2.x.
So I have found a solution! https://www.drmrx.org/forum/forum/drm-reception-project/general-topics/1580-how-often-does-dream-start-to-crash-when-decoding-xhe-aac/ This fork of Dream "2.2.x" by ZFYoung is stable, but not compiled for Windows 7, but Windows 8.1. However, I have been using Vxkex extensions on windows 7 and it WORKS!!! Way back, I had installed Vxkex Extensions - https://github.com/i486/VxKex To run Dream 2.2.x, I installed npcap. https://nmap.org/npcap/ Next, I installed "vc_redist...
So I have found a solution! https://www.drmrx.org/forum/forum/drm-reception-project/general-topics/1580-how-often-does-dream-start-to-crash-when-decoding-xhe-aac/ This fork of Dream "2.2.x" by ZFYoung is stable, but not compiled for Windows 7, but Windows 8.1. However, I have been using Vxkex extensions on windows 7 and it WORKS!!! Way back, I had installed Vxkex Extensions - https://github.com/i486/VxKex To run Dream 2.2.x, I installed npcap. https://nmap.org/npcap/ Next, I installed "vc_redist...
Added fmjd in AM mode
Hi guys, I use Openwebrx plus(https://hub.docker.com/r/slechev/openwebrxplus) to run SDR service, and the built-in DRM only support AAC decoding, but not support xHE-AAC decoding. So I try to re-compile the dream from souce code to make it support xHE-AAC, and the make is ok, but if run the dream, it's still get error output. details information as below. 1. Basic informaion: Hardware: SDRPlay RSP1, a SDR(softwave define radio) dongle. System: Ubuntu 20.04 Docker image: https://hub.docker.com/r/slechev/openwebrxplus...
Hi guys, I use Openwebrx plus(https://hub.docker.com/r/slechev/openwebrxplus) to run SDR service, and the built-in DRM only support AAC decoding, but not support xHE-AAC decoding. So I try to re-compile the dream from souce code to make it support xHE-AAC, and the make is ok, but if run the dream, it's still get error output. details information as below. 1. Basic informaion: Hardware: SDRPlay RSP1, a SDR(softwave define radio) dongle. System: Ubuntu 20.04 Docker image: https://hub.docker.com/r/slechev/openwebrxplus...
Hi guys, I use Openwebrx plus(https://hub.docker.com/r/slechev/openwebrxplus) to run SDR service, and the built-in DRM only support AAC decoding, but not support xHE-AAC decoding. So I try to re-compile the dream from souce code to make it support xHE-AAC, and the make is ok, but if run the dream, it's still get error output. details information as below. 1. Basic informaion: Hardware: SDRPlay RSP1, a SDR(softwave define radio) dongle. System: Ubuntu 20.04 Docker image: https://hub.docker.com/r/slechev/openwebrxplus...
Hi guys, I use Openwebrx plus(https://hub.docker.com/r/slechev/openwebrxplus) to run SDR service, and the built-in DRM only support AAC decoding, but not support xHE-AAC decoding. So I try to re-compile the dream from souce code to make it support xHE-AAC, and the make is ok, but if run the dream, it's still get error output. details information as below. 1. Basic informaion: Hardware: SDRPlay RSP1, a SDR(softwave define radio) dongle. System: Ubuntu 20.04 Docker image: https://hub.docker.com/r/slechev/openwebrxplus...
Since I have Hamlib 4.5.5, I restored the 'const' where PrintHamlibModelList is defined. Let's be more specific. Code is precise. People would need to know exact changes to specific lines in specific files. I have worked out the following required changes: change src/util/Hamlib.cpp line 344 CHamlib::PrintHamlibModelList(struct rig_caps *caps, void *data) to CHamlib::PrintHamlibModelList(const struct rig_caps *caps, void *data) change src/util/Hamlib.h line 116 static int PrintHamlibModelList(struct...
Since I have Hamlib 4.5.5, I restored the 'const' where PrintHamlibModelList is defined. Can you please be more specific. Code is precise. People would need to know exact changes to specific lines in specific files. Thanks.
I hope it's possible for Hamlib to stop messing around with silly interface changes involving 'const' that break things here as well as in other apps... But my point was this was a compilation issue and should have been in the compilation section here, not general. You also would have found the answer quicker.
Since I have Hamlib 4.5.5, I restored the 'const' where PrintHamlibModelList is defined. It compiled and receives stations. I hope it is possible to do something to make this work with both Hamlib 4.5 and Hamlib 4.6.
I don't see 'const' in the line where where PrintHamlibModelList is defined. I may not understand what you were saying. In Hamlib.cpp I see int CHamlib::PrintHamlibModelList(struct rig_caps *caps, void *data) In Hamlib.h I see static int PrintHamlibModelList(struct rig_caps* caps, void* data);
Read my comments in the Compiling section.
I tried to compile dream-mjf r1412 on my Raspberry Pi and it failed. I have Hamlib 4.5.5 installed. Is Hamlib 4.6 required for this version? If so, can it be made to also work on the current stable release? These are probably the messages we need to see. src/util/Hamlib.cpp: In constructor ‘CHamlib::CHamlib()’: src/util/Hamlib.cpp:125:25: error: invalid conversion from ‘int (*)(rig_caps*, void*)’ to ‘int (*)(const rig_caps*, void*)’ [-fpermissive] 125 | rig_list_foreach(PrintHamlibModelList, this);...
Adjusted specs for Homebrew fdk-aac as well as git-built hamlib.
Removed const in PrintHamlibModelList to be compatible with Hamlib's rig_list_add method.
Removed enableAxis as no longer a method used by QwtPlot
Updated Include and Libs path specifications for using non-free fdk-aac library under Linux.
Just to be clear: Make a note to only use the fdk-aac libraries from RPM Fusion when building in Linux, and apply the changes to the dream.pro file using the blurb above, otherwise decoding won't work properly.
Ok... revised dream.pro by adding: unix: { INCLUDEPATH += /usr/include/fdk-aac LIBS += -L/usr/lib64/fdk-aac } before LIBS += -lfdk-aac in the fdk-aac{} section and it now properly builds using the non-free, v2.0.3 of fdk-aac. All indications are that it also decodes properly using the test tape files.
I should have tested this using the test files. Old problem is back, where decoding generates improper buffer errors and MSC light never lights despite having 20db snr. suggests something's amiss with the interface to the fdk-aac codec. So, one available codec (fdk-aac-free v2.0.0-13) links but fails. Other codec (fdk-aac v2.0.3-2) won't link... Weird situation, because the Homebrew version of fdk-aac (also v2.0.3) works fine on a Mac (pseudo-Unix) build, which also suggests something either may...
I should have tested this using the test files. Old problem is back, where decoding generates improper buffer errors and MSC light never lights despitee having 20db snr. suggests something's amiss with the interface to the fdk-aac codec. So, one available codec (fdk-aac-free v2.0.0-13) links but fails. Other codec (fdk-aac v2.0.3-2) won't link... Weird situation, because the Homebrew version of fdk-aac (also v2.0.3) works fine on a Mac (pseudo-Unix) build, which also suggests something either may...
Has anyone actually got the AAC codec working for transmitting. its been years since i last asked
Was recently rebuilding my Linux machine and stumbled upon a few requisite code changes. Hamlib changed their spec for rig_list_add, which affects PrintHamlibModelList found in both Hamlib.cpp and Hamlib.h. Small change: just remove the 'const' where PrintHamlibModelList is defined in both files. Qwt eliminated the enableAxis method. This affects several lines in DRMPlot.cpp. Just search for plot->enableAxis and replace with a double slash in front of it to comment those lines out. Worthwhile to...
As a rule, you'll also want your receiver filter at least 10kHz wide and Sharp instead of Normal. You may also want to look at the local noise source that's creating in-band interference... Almost looks like mains or display noise, so you'll want to look at the antenna you're using.
Hi! I have tried as you suggested, but MSC CRC is always red, even when SNR is >14. As a result no audio, I will try to get some shortwave DRM and update here.
What may help is if you set the following in the System Evaluation window: Misc Settings - MLC: Number of iterations: 4 Audio - Reverberation: Off (not really sure that will help, but won't hurt processing) Interferer Rejection - Bandpass Filter: On Interferer Rejection - Modified Metrics: On
Thank you for the insight. Looks like SNR is the root cause. I am attaching a screenshot of best SNR I could get for reference.
You're not showing the System Evaluation display, so it's hard to tell what's going on. From what you are showing it looks as if there's not a good, clean signal there. You need to have about a 12dB signal-to-noise ratio for it to demodulate the audio properly. Given that you're only showing two bars at the top and two at the bottom (it won't play without all three on the bottom), I'd say that's what's happening. Plus, it looks like you have some serious in-band power interference on the GQRX display,...
I have build Dream from https://github.com/godarklight/dream for Ubuntu 20.04 I am able to decode local DRM channels but playback is not working due to the following errors- *** playback UNDERFLOW fill failed 5 Can you please help me resolved this issue?
Should be wherever dream.exe is run from.
I'd love to know where this "Dream.ini" file is supposed to be, since I don't see it in my installation directory.
Hello, I wasn't aware of this development - this is very interesting indeed! It's probably better to focus on this encoder rather than FDK-AAC. R On Thu, 7 Mar 2024, 16:25 Rafael Diniz, rafael2k@users.sourceforge.net wrote: I would also consider libxaac, which explicitly mentions DRM: https://github.com/ittiam-systems/libxaac It supports many object types, including HE-AAC and USAC (xHE-AAC). USAC is also supported in DRM (thou the super-framing is a bit different in order to allow "abr" framing)....
I would also consider libxaac, which explicitly mentions DRM: https://github.com/ittiam-systems/libxaac It supports many object types, including HE-AAC and USAC (xHE-AAC). USAC is also supported in DRM (thou the super-framing is a bit different in order to allow "abr" framing). I can see 960 frames support is there, and also some ER tools! Cheers, Rafael On 3/7/24 13:41, Rash wrote: Hi Sam, Apologies - I don't really know enough to be much help. You should probably look at this repo instead of the...
Hi Sam, Apologies - I don't really know enough to be much help. You should probably look at this repo instead of the one I previously pointed you at, because I think the fdk included is much more up to date: https://github.com/Opendigitalradio/ODR-AudioEnc/tree/master You can also look at the ODR-AudioEnc source to see how FDK-AAC is interfaced for DAB+. All of the DRM related bits have been stripped out of FDK-AAC, which is probably the source of your error? So I suspect you'd need to call it as...
Thank you very much! Rash, I called the DAB fdk-aac library you mentioned for coding, and his code has several more parameters than the ordinary 1024 coding, I attached the screenshot of the code. But I still can't generate the aac file. In addition, after I changed the parameter TT_DABPLUS to TT_DRM, the message "Unable to set the RAW transmux" was displayed. I suspect that the parameter used by drm is different from that used by DAB. Do you know any other parameters, or do you know where to look...
Hi Rafael, That's a good point! I don't know enough to be certain that it would, but If someone does plug FDK in, I would be happy to carry out tests against a DRM codec that does have ER. I don't have a suitable channel simulator, so only 'conducted' measurements to several different receivers (e.g. a Coding Technologies portable) via a variable step attenuator, but it should be adequate for quantifying how valuable ER is. R
Hi, I just wandered by to answer a question about FDK and spotted this topic - I have a couple of (Edit: well, three) suggestions: Add a raw IQ UDP output like Spark and the AlgoKorea Windows transmitter (which I've not used, but it doesn't half look like DReaM!) This would be nice for a few obvious reasons. One very cool one is it enables an FL2000 VGA adapter to be used as a 0-150 MHz DRM signal source by using the Osmocom FL2K library with an IQ modulator tool that's on Github. Apply a raised...
Hi, I just wandered by to answer a question about FDK and spotted this topic - I have a couple of suggestions: Add a raw IQ UDP output like Spark and the AlgoKorea Windows transmitter (which I've not used, but it doesn't half look like DReaM!) This would be nice for a few obvious reasons. One very cool one is it enables an FL2000 VGA adapter to be used as a 0-150 MHz DRM signal source by using the Osmocom FL2K library with an IQ modulator tool that's on Github. Apply a raised cos filter for the IQ...
You are right, nevertheless, I suppose a receiver would work even without using the ER tools. Rafael On 3/5/24 19:42, Rash Mustapha wrote: Hi Sam, You won't believe how painful it was to sign up here, just to answer this question. The captcha was being ridiculous! The answer is 'yes'...however, it's not a slam dunk! An OpenDigitalRadio colleague patched FDK for 960 transform so it can be used as a DAB+ encoder, however DRM30 uses the Error Robust (ER) AAC Scalable object type (ID = 20) High Quality...
Hi Sam, You won't believe how painful it was to sign up here, just to answer this question. The captcha was being ridiculous! The answer is 'yes'...however, it's not a slam dunk! An OpenDigitalRadio colleague patched FDK for 960 transform so it can be used as a DAB+ encoder, however DRM30 uses the Error Robust (ER) AAC Scalable object type (ID = 20) High Quality Audio Profile and FDK doesn't have this profile. It's here anyway: https://github.com/Opendigitalradio/fdk-aac And good luck! R
Hello, the mode I use is B mode, 10kHZ bandwidth, and the corresponding multiplexing frame length in the protocol is 5826 bits. When I was encoding the MOTSlideshow service, the size of a generated data packet was 472 bits. I sequentially filled every 12 data packets into the multiplexing frame and added 160 0s. Is this method correct? If there is any problem, Hope you can give me some advice.
Hello everyone, I want to use the fdk-aac library to compile an AAC+SBR audio service for drm. Does anyone have an fdk-aac library that supports 960 frame length? It would be better if there is a reference code. Thank you for your help.
I'm using v2.3, but it's a version compiled on a Mac from the CVS codebase, not a pre-compiled distro. Shouldn't really matter though since I don't think the distro had any problems with MOT. In your file, it looks like there's nothing in it, but it's very hard to tell because there's no audio to let me know if it's looping or not. In a future one, you might want to include an audio channel. Attached is what I see. Maybe if @olliehaffenden has any time, he can investigate what the problem might ...
I've waited for about 10 minutes after running it in the command line, but there is still no image displayed. Which version of Dream are you using? I suspect it might be an issue with my version. Additionally, could you help me test a file? I generated it myself, and it only contains one MOTSlideshow service. I've attached the file and screenshots below. Thank you for your assistance!!
That sample file has two slides in it: One that shows "BCE" and another with a picture of a transmitter rack. The MOT display is not immediate and may take a while to display anything. Are you waiting for the entire sample file to play through? From the terminal, the proper command for Windows is: <path to dream>/dream.exe -f <path to sample file>/<name of sample file> or, for the sample you chose: <path to dream>/dream.exe -f <path to sample file>/RTLwithSlideshow_ModeB_10kHz.flac
That sample file has two slides in it: One that shows "BCE" and another with a picture of a transmitter rack. The MOT display is not immediate and may take a while to display anything. Are you waiting for the entire sample file to play through? From the terminal, the proper command for Windows is: <path to dream>/dream.exe -f <path to sample file>/<name of sample file> or, for the sample you chose: <path to dream>/dream.exe -f <path to sample file>/RTLwithSlideshow_ModeB_10kHz.flac
I also used Dream V2.1.1 to test the example of the file area. The MOT display box cannot display pictures. Is it a problem with my version? I've attached a screenshot below. Could you please provide some command line scripts for the dream software? I will use it for testing, it would be even better if there are websites that learn command lines. What version of Dream software are you referring to?
Can you provide some command line scripts for the dream software? I will use it for testing, it would be even better if there are websites that learn command lines. What version of Dream software are you referring to?
It's possible that you may have the appropriate encoding codecs, but not the decoders for that particular content stream. Or, Dream just doesn't recognise it. Does your copy work with the MOT samples from the Files area? If it does not, it may be a clue that MOT is not working at all. You may want to try to run Dream from the command line to see what errors are being produced when it attempts to display it.
The MSC CRC on the evaluation box is gray because this light is used to detect the CRC on the audio frame. If it is a transmitted data service, it is gray. I'm encountering the same problem as you now. Pictures cannot be displayed. The interface displayed by your MOT is the same. How did you solve it?
Hello everyone, I am studying the encoding of MOT slideshow. The encoding has been completed. However, when decoding with Dream v2.1.1, the picture cannot be displayed and only the following screenshots can be displayed. Can any experienced teacher give me some advice?!!
But there are other issues. Partly due to a recent Hamlib commit. Attached are my diffs. Missing using namespace std;, std::high_resolution::to_time_t() etc. etc.
Ok, I've fixed that. It now compiles, but running DreamConsole --test 1, it aborts on a sample-rate of 96000. In SoapyRTLSdr/settings.cpp: throw std::runtime_error("setSampleRate failed: RTL-SDR does not support this sample rate"); And Dream.exe crashes at start-up: class CUpstreamDI : public CReceiverModul<_BINARY, _BINARY> , public CPacketSink { public: CUpstreamDI(); virtual ~CUpstreamDI(); /* CRSIMDIInInterface */ bool SetOrigin(const std::string& strAddr); bool GetInEnabled() {return source...
The source is designed to be able to build with a wide range of different configurations: e.g. it can use different audio decoding libraries, different sound devices etc. Trying to make these all work at the same time is like whacking moles, but feedback from people like yourself who have a different configuration is a great help to us, so thanks for taking the time to post. If it won't build without Soapy, that's my bad, because it should be possible to build it to use a soundcard input carrying...
Have you been able to install Soapy itself? Sure. And there areIMHO too many #ifdef tests in this ollie branch; * A test for HAVE_LIBZis superflous. zlib is required. * Seems to me SoapySDR is required too.
I've just looked and I see what you mean about the #include being omitted if WIN32 is defined. If you do want to use Soapy, I think the first step would be to move that outside that #if altogether. Have you been able to install Soapy itself? It looks like there are Windows installers for it.
Hello Gisle and thanks for your enquiry. I haven't tried building my branch (dream-ollie or dream-ollie-deployed) on Windows so I'm not surprised there are issues. I'll try to help you later this afternoon, but to point me in the right direction: are you wanting to use Dream with an SDR front-end of some kind, using the SoapySDR library? That's the main thing that my branches offer in addition to e.g. dream-rafa.
I'm struggling to compile this project with the qmake generated Nmake-files. E.g. this error seems related to a missing USE_SOAPY: src\sound\soundinterfacefactory.cpp(89): error C2259: 'CSoundInMMSystem': cannot instantiate abstract class windows/Sound.h(54): note: see declaration of 'CSoundInMMSystem' src\sound\soundinterfacefactory.cpp(89): note: due to following members: src\sound\soundinterfacefactory.cpp(89): note: 'bool CSoundInInterface::Read(CVector<short> &,CParameter &)': is abstract sound\soundinterface.h(44):...
Don't have multiple HTTP requests in-flight at the same time, to allow for long polling.
Fixes to make AM with RSCI out work:
Hello trying to run Dream 2.2.1 on Debian 12. The only way to pipe audio from Gqrx is starting Dream with the -I option: $ ./dream -I alsa_output.pci-0000_00_10.1.analog-stereo.monitor But as soon as Dream locks to a station it crashes with: pulseaudio output device 'alsa_output.pci-0000_00_10.1.analog-stereo', init done *** stack smashing detected ***: terminated
I tried commenting out the definition for rig_model_t but compilation failed in Hamlib.cpp. My C++ knowledge isn't enough to fix it at that point. If it can be modified, it would be a much better fix then my hack.
So, Sourceforge's editor thought that angle bracket was an html directive... ignore the closing (angle-bracket) /file (close-angle-bracket) thing.
So, Sourceforge's editor thought that angle bracket was an html directive... ignore the closing thing.
Im just wondering if the AAC option that is greyed out will ever change with AAC dlls in dream and if soo what is the acceptible DLL file name. cheers guys @jcable
wow thats an idea. if you could transmit low bit rate video like the images DAB uses from the station but its like a GIF animation of the weather but using H.256 or something. like having a animated cloud or something @fineware
For some reason the file interface is a bit messy, so you need to use the command line to play each sample file properly. Command line should be something like: dream.exe -f <file name=""></file> The file is a test of some web cam shots. I've included a screen shot of what it should look like, but clicking on the "1" button brings up the MOT viewer.
For some reason the file interface is a bit messy, so you need to use the command line to play each sample file properly. Command line should be something like: dream.exe -f <file name=""></file> The file is a test of some web cam shots. I've included a screen shot of what it should look like, but clicking on the "1" button brings up the webcam viewer.
DreamWebcamApp_ModeA_10kHz.flac is loacted in files
does anyone know what this is? it seams to do nothing in Dream