Activity for zefie
-
zefie posted a comment on discussion General Discussion
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
-
I released an update last night. It might support as low as Windows 8.1 now (even though it was built on Windows 7 it won't run on it, lol). I also added more codec support (opus, speex and libsndfile). The build may also been slightly more stable as I realized some of the library SDKs were mismatched with the first release. Check the reddit post for the update. :)
-
How much signal do I need the get decoding started? About as much as Dream 2.1, 15dB+
-
I'm not sure if the new fdk-aac decoder is actually up to DRM standards yet.
-
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 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.
-
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...
-
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...
-
After looking into the current build a bit more, you should remove wpcap.dll and Packet.dll that you copied from old dream, and install npcap (the successor to WinPCap). Do this even if you installed WinPCap (it will upgrade it). The mismatched libraries will cause it to crash even more than 2.2 normally does. It won't be super stable and will probably still crash on weak signal (I think this is the new decoder), but it should run more than 5 seconds. :)
-
After looking into the current build a bit more, you should remove wpcap.dll and Packet.dll that you copied from old dream, and install npcap (the successor to WinPCap). Do this even if you installed WinPCap (it will upgrade it). The mismatched libraries will cause it to crash even more than 2.2 normally does. It won't be super stable and will probably still crash on weak signal (I think this is the new decoder), but it should run more than 5 seconds. :)
-
The pcap dependancy was likely overlooked because both test machines had the official WinPcap installed (https://www.winpcap.org/install/default.htm) . As for the stability, well, thats 2.2 for ya. I am hoping to be able to run debugging once the environment is set up for Win7 and maybe try to address the issues myself.
-
(accidental double post)
-
What is the error message? Also be sure to have Visual C++ 2019 x86 redist installed as well.
-
What is the error message? Also be sure to have Visual C++ 2019 x86 redist installed as well.
-
I am not part of the team who developed DReaM, just a developer who is stubborn (and maybe a bit masochist) enough to fight with this stuff to make a build. I didn't modify any of the source (yet), just the dream.pro file (to add include paths and change versions of libraries). It is a pain to build and I do not have an automated way to build it, I build the libraries manually and put them where the dream makefiles expect. The current build is apparently VS2019. I am going to try to recreate it in...
-
It was tested on another machine completely unrelated to the development prior to release. There was also another redditor who executed it fine. Make sure your copy of Win10 is up to date, or at least equal to or higher than v10.0.19041.0. I am in the process of attempting to set up a Win7 development enviroment in order to attempt to build a more compatible version, but that will take some time.
-
See here: https://www.reddit.com/r/RTLSDR/comments/grp6m2/dream_v221_for_windows_with_xheaac_support/
1
