Do not put the wpcap and packet dlls directly in the folder with my build. simply install npcap as normal, the application will find it in the system folder.
All you have to do in Dream 2.1 is choose your INPUT sound device, for some reason changing the input will crash 2.2, but you can change the output. Or if your Dream 2.1 works on normal AAC, just copy that Dream.ini into the folder with the new dream.
Also, for the record, when installing applications without an installer (such as my RAR) it is best to NOT put it in program files, because of Windows permissions. My setup goes something like:
C:\bin\SDR\ (SDR Apps)
C:\bin\SDR\analytics\ (decoder apps)
My DReaM is at C:\bin\SDR\analytics\DReaM
you dont need to use the same folder names I do, I just have a lot of SDR stuff I try to keep organized.
by extracting the rar to a custom made folder outside of Program Files you reduce the chance of extra errors stemming from when the application cannot write its own files (such as Dream.ini).
Last edit: zefie 2020-05-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unzipped Zefies' version of Dream 2.2 in it's own folder, uninstalled Ncap and re installed it, and now Dream seems to want to work, (now to wait for Radio Marti later to test). Note, something when installing Ncap made it try to install it twice, happened both times I installed it, let it install twice the first try and aborted the attempt on the second try, Don't know if that made a difference, but I thought I'd note it.
and THANK YOU!!!!
Last edit: Michael E McCarty 2020-05-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, another update. Band conditions are good and I found a signal to play with. With SDRuno set to line out (virtual cable) and with the digital button clicked and the bandwidth set at 12k, Dream seemed to be reading the signal (it identified it for location and signal type), even though input is still default. I thought it had to come in on the virtual cable to do this, am I routing stuff wrong?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If DReaM is identifying the signal and you are sure its coming in over the virtual cable (mute SDR and make loud noise into your mic to verify its not using mic), then I would not worry about what it is displaying as the input device, its likely a cosmetic issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When testing with a couple test recordings Dream 2.2.1 worked well. When listening to on the air signals if the S/N ratio isnt high enough for a good audio decode Dream never crashes. It will stay up for hours. As soon as its good enough to decode audio Dream will crash and close if the signal varies or drops momentarily which of course happens all the time on HF. Darn! I had high hopes. Seems to me the problem is now related to the FDK codec. Sure wish the old DRM Radio software from years ago was still supported and upgradeable or could be reverse engineered. It worked a treat.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe this has to do with the error handling (or lack thereof) of the new AAC decoder. When it recieves a corrupt frame, it crashes instead of trying to recover. This is one thing I hope I'm able to address when I can actually debug it and make it crash when the debugger is running. Haven't had much time to mess with it, nor luck when I did have time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When it recieves a corrupt frame, it crashes instead of trying to recover.
There's clause in DRM standard in section"5.3.1.2 xHE-AAC audio frame: Audio frame content CRC" which can be used to decide if the audio frame in question is corrupt and be dealt with accordingly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regardless the internal implementation on FDK side, the audio frame CRC is mandatory in DRM bitstream and serves as "insanity check" on what is contained in its payload that will be further processed by FDK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, a further update. Tried a cheat to overthrow the "crash on changing input" by opening up the INI file and manually inputting the choice I wanted, hit "save" and it seemed to take. Choice is now correct, Ive got a good waterfall, and it ID'd the station and parameters once, but still no audio. Signal is not great, I've got a 6.6 DB SNR and the MSC CRC is not lit. How much signal do I need to get decoding started?
Last edit: Michael E McCarty 2020-05-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
GOT IT!!! Found a stronger signal elsewhere and it's working! Signal not outstanding but good enough, some occasional digital stuttering but the station is staying locked, no crashing. Decode is aac, will see later how it handles other modes. If I minimize Dream and then click on the taskbar, it seems to start another instance of Dream as opposed to bringing it up.
Thanks all, and especially you, Zefie, for getting me through this!!
(Now what to do the rest of the layoff?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Zefie.
Your second version works on 8.1 as well as 10. It is more stable than before but still will crash on xHE-AAC errors. Other formats work very well. Thank you for your efforts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
can't anyone put a Windows build together so all you gotta do is download an exe/zip and run the thing? I don't want to load up my machine with a VS and QT development environment just to listen to a radio station I can't even understand.
Last edit: David C Jackson 2020-06-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi! A friend of mine ran into this issue this morning, and I have just checked about the release.
It seems like it's missing some runtime components, so I grabbed my Qt 5.12.0 msvc2017 and re-ran windeployqt.exe, and it seems working now.
I didn't recompile anything, I just put some missing things back with windeployqt.
I've repacked everything in a 7z file, see the link below.
I'm not quite familiar with this project, but if you ran into this issue, test it out and see if there's any glitch or error.
Don't forget to install npcap anyway and get vc runtime 2015/17/19 [x86]. https://sanctuary-cdn.beacoworks.xyz/s/38LYicM2ge2mxzi
Last edit: Beacon Zhang 2020-09-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do not put the wpcap and packet dlls directly in the folder with my build. simply install npcap as normal, the application will find it in the system folder.
All you have to do in Dream 2.1 is choose your INPUT sound device, for some reason changing the input will crash 2.2, but you can change the output. Or if your Dream 2.1 works on normal AAC, just copy that Dream.ini into the folder with the new dream.
Also, for the record, when installing applications without an installer (such as my RAR) it is best to NOT put it in program files, because of Windows permissions. My setup goes something like:
C:\bin\SDR\ (SDR Apps)
C:\bin\SDR\analytics\ (decoder apps)
My DReaM is at C:\bin\SDR\analytics\DReaM
you dont need to use the same folder names I do, I just have a lot of SDR stuff I try to keep organized.
by extracting the rar to a custom made folder outside of Program Files you reduce the chance of extra errors stemming from when the application cannot write its own files (such as Dream.ini).
Last edit: zefie 2020-05-29
Unzipped Zefies' version of Dream 2.2 in it's own folder, uninstalled Ncap and re installed it, and now Dream seems to want to work, (now to wait for Radio Marti later to test). Note, something when installing Ncap made it try to install it twice, happened both times I installed it, let it install twice the first try and aborted the attempt on the second try, Don't know if that made a difference, but I thought I'd note it.
and THANK YOU!!!!
Last edit: Michael E McCarty 2020-05-30
Well, another update. Band conditions are good and I found a signal to play with. With SDRuno set to line out (virtual cable) and with the digital button clicked and the bandwidth set at 12k, Dream seemed to be reading the signal (it identified it for location and signal type), even though input is still default. I thought it had to come in on the virtual cable to do this, am I routing stuff wrong?
If DReaM is identifying the signal and you are sure its coming in over the virtual cable (mute SDR and make loud noise into your mic to verify its not using mic), then I would not worry about what it is displaying as the input device, its likely a cosmetic issue.
When testing with a couple test recordings Dream 2.2.1 worked well. When listening to on the air signals if the S/N ratio isnt high enough for a good audio decode Dream never crashes. It will stay up for hours. As soon as its good enough to decode audio Dream will crash and close if the signal varies or drops momentarily which of course happens all the time on HF. Darn! I had high hopes. Seems to me the problem is now related to the FDK codec. Sure wish the old DRM Radio software from years ago was still supported and upgradeable or could be reverse engineered. It worked a treat.
I believe this has to do with the error handling (or lack thereof) of the new AAC decoder. When it recieves a corrupt frame, it crashes instead of trying to recover. This is one thing I hope I'm able to address when I can actually debug it and make it crash when the debugger is running. Haven't had much time to mess with it, nor luck when I did have time.
There's clause in DRM standard in section"5.3.1.2 xHE-AAC audio frame: Audio frame content CRC" which can be used to decide if the audio frame in question is corrupt and be dealt with accordingly.
I'm not sure if the new fdk-aac decoder is actually up to DRM standards yet.
Regardless the internal implementation on FDK side, the audio frame CRC is mandatory in DRM bitstream and serves as "insanity check" on what is contained in its payload that will be further processed by FDK.
I feel like the switch from FAAD to FDK-AAC was a bit hacky and that DReaM is not up to DRM standards either. Check this source file in which the getFrame function accepts a crc but is not even checked. http://svn.code.sf.net/p/drm/code/branches/dream-rafa/src/MSC/xheaacsuperframe.cpp
Ok, a further update. Tried a cheat to overthrow the "crash on changing input" by opening up the INI file and manually inputting the choice I wanted, hit "save" and it seemed to take. Choice is now correct, Ive got a good waterfall, and it ID'd the station and parameters once, but still no audio. Signal is not great, I've got a 6.6 DB SNR and the MSC CRC is not lit. How much signal do I need to get decoding started?
Last edit: Michael E McCarty 2020-05-30
About as much as Dream 2.1, 15dB+
GOT IT!!! Found a stronger signal elsewhere and it's working! Signal not outstanding but good enough, some occasional digital stuttering but the station is staying locked, no crashing. Decode is aac, will see later how it handles other modes. If I minimize Dream and then click on the taskbar, it seems to start another instance of Dream as opposed to bringing it up.
Thanks all, and especially you, Zefie, for getting me through this!!
(Now what to do the rest of the layoff?)
Zefie.
Your second version works on 8.1 as well as 10. It is more stable than before but still will crash on xHE-AAC errors. Other formats work very well. Thank you for your efforts.
can't anyone put a Windows build together so all you gotta do is download an exe/zip and run the thing? I don't want to load up my machine with a VS and QT development environment just to listen to a radio station I can't even understand.
Last edit: David C Jackson 2020-06-26
Hi! A friend of mine ran into this issue this morning, and I have just checked about the release.
It seems like it's missing some runtime components, so I grabbed my Qt 5.12.0 msvc2017 and re-ran windeployqt.exe, and it seems working now.
I didn't recompile anything, I just put some missing things back with windeployqt.
I've repacked everything in a 7z file, see the link below.
I'm not quite familiar with this project, but if you ran into this issue, test it out and see if there's any glitch or error.
Don't forget to install npcap anyway and get vc runtime 2015/17/19 [x86].
https://sanctuary-cdn.beacoworks.xyz/s/38LYicM2ge2mxzi
Last edit: Beacon Zhang 2020-09-20